TRADING BINARY OPTIONS WITH MARKET INDICATORS: AN EASY WAY

Freestanding in Prague

Freestanding in Prague

The C++ standards committee met in Prague, Czech Republic between Feb 10 and Feb 15. The standard is wording complete, and the only thing between here and getting it published is ISO process. As is typical for me at these meetings, I spent a lot of time doing freestanding things, Library Incubator (LEWGI) things, and minuting along the way (15-ish sessions/papers!).

Freestanding

I had three freestanding papers coming into this meeting:
The first two papers are pieces of my former "P0829: Freestanding Proposal" paper, and had been seen by the Feature Test study group in Belfast. During this meeting, I got to run them by the Library Incubator for some design feedback. The papers were received well, though some potential danger points still exist. Library Evolution can look at the papers as soon as they have time.
P2013 is the first smaller piece taken out of "P1105: Leaving no room for a lower-level language: A C++ Subset". Exceptions are probably the most important thing in P1105, but there's so much activity going on in this area that it is hard for me to make good recommendations. The next highest priority was new and delete, hence P2013 being born. I also felt that P2013 was a good test paper to see if the committee was willing to make any language based change for freestanding.
I had presented P2013 in a prior Low Latency / SG14 telecon, and received unanimous approval (no neutral, no against votes). I was able to present it in the Evolution Incubator, and received no against votes. Then, in a surprisingly quick turnaround, I was able to present to Evolution, and again received no against votes. So now I just need to come up with wording that accomplishes my goals, without breaking constant evaluated new.

Errors and ABI

On Monday, we held a join session between Evolution and Library Evolution to talk about one of the C++ boogeymen, ABI. P1836 and P2028 have good background reading if you are not familiar with the topic. The usual arguments were raised, including that we are losing out on performance by preserving ABI, and that breaking ABI would mean abandoning some software that cannot be rebuilt today. We took some polls, and I fear that each person will interpret the polls differently. The way I interpreted the polls is that we won't do a "big" ABI break anytime soon, but we will be more willing to consider compiler heroics in order to do ABI breaks in the library.
One ABI area that is frequently overlooked is the situation that I am in. I can rebuild all of my source code, but even despite that I still care about ABI because I don't ship all of it together. I build a library with a plugin architecture, and breaking ABI would mean updating all the plugins on customer systems simultaneously... which is no easy task. I also ship binaries on Linux systems. We would prefer to be able to use new C++ features, despite targeting the various "LTS" distributions. ABI stability is a big part of that. I am hoping to make another post to cpp with my thoughts in the next few months, tentatively titled "ABI Breaks: Not just about rebuilding".
On Tuesday, LEWG discussed "P1656: 'Throws: Nothing' should be noexcept". This is a substantial change to the policy laid out in N3279, authored by Alisdair Meredith. That's why it is informally called the "Lakos" rule. We discussed the trade-offs involved, including how adding noexcept can constrain future changes, how noexcept can make precondition tests more difficult, and how this will change little in practice, because implementers already mark most "Throws: Nothing" calls as noexcept. Arguments about performance, code bloat, and standards guaranteed portability won out though. This paper was "only" a policy change, so a follow-on paper will need to be authored by someone in order to actually do the noexcept marking.
Wednesday night we had a social event celebrating the impending C++20 release. The event was held in the Prague Crossroads, built in 927 A.D.. The large tables let us have conversations with people we may not have really bumped into during the rest of the meeting. I started talking exceptions with a few of the other people at the table, and one of the had some particularly in depth knowledge about the topic. As it turns out, I was sitting at the same table as James Renwick of Low-cost Deterministic C++ Exceptions for Embedded Systems fame. I ended up talking his ear off over the course of the night.
Thursday in LEWG, we talked about Niall Douglas's "P1028: SG14 status_code and standard error object". This is the class that may one day be thrown by P0709 "Static" exceptions. Coincidentally, the most contentious parts were issues involving ABI. In several of the virtual interfaces in the standard, we've wanted to add things later, but haven't been able to do so.
Friday, James Renwick was able to present his paper, and the room was very receptive of it. One of my concerns going in to the presentation was that the committee would be unwilling to change anything in the standard related to today's exceptions. After the presentation and discussion, I'm less concerned about that. There was definitely a willingness to make some changes... but one of the big challenges is a question of whether we change default behavior in some cases, or change language ABI, even for C.

Other papers

P1385: "High level" Linear Algebra

This one is the "high level" linear algebra paper. There's a different, "lower level" linear algebra paper (P1673) that covers BLAS use cases. P1385 is intended to be something that can sit on top of P1673, if I understand correctly.
For being a math paper, there was surprisingly little math discussion in Library Incubator. We were generally discussing general interface issues like object ownership, concept requirements, and how to spell various operations, particularly inner product and outer product.

P1935: Physical Units

We are still in the philosophy and goals stage of this paper. We got to discuss the finer points of the distinctions between "kilogram" and "1 kilogram"; the difference between a unit, a dimension, and a quantity; and the difference between systems and models.
This paper is challenging in that there is significant prior art, as well as strong opinions about "the right way" to do things. This gets to one of the trickier parts of standards meetings... driving consensus. The interested parties have been requested to (preferably) work together outside of the three meetings a year, or failing that, to write a paper that gives some outline of what a solution should look like.
This paper also has an absurdly awesome / terrifying metaprogramming trick in it. A base class uses a friend declaration to declare (but not define) a function with an auto return type and no trailing return value. The derived class then declares and defines the function (again via friend) and lets the definition of the function determine the auto return type. This lets the base class use decltype to pull type information out of the derived class without explicitly passing that information down in a template argument (sorcery!). The main caveat with this trick is that it only works with exactly one derived class, as otherwise you end up with multiple conflicting definitions of the same function.

Concurrent Queues, P0260 and P1958

It's amazing what a minor paper reorg will do for productivity. This pair of papers used to be a single paper in the San Diego time frame, and we had a difficult time understanding how the pieces worked together. With the paper split as it is now, we have a small, concrete piece to review, which we were then able to see how it fit in to the interfaces and concepts of the larger paper. We got to dig in to some corner case traps with exception safety, move semantics, and race conditions. There were implementers in the room that could say what their implementation did, and I feel that the room was able to give good feedback to the authors.

P1944: constexpr and

Antony Polukhin is secretly my accidental nemesis (well, not so secret anymore). Over the course of C++20, he sprinkled constexpr on many of the things. As it turns out, there is a large (but not 100%) overlap of constexpr and freestanding. Each thing that went constexpr turned into a merge conflict that I got to resolve in my papers.
And he's still at it!
In this case, 100% of the things that were constexpr'd were also things that I have previously identified as being potentially freestanding. So that's a positive. There were concerns about implementability though, as sometimes, the C library and the C++ library come from different vendors, and having forwarding wrappers is far from trivial.

A minute about minuting

For the wg21 readers out there, if you think you are bad at taking minutes, that just means you need more practice :) . If you find yourself in a room that is about to review a paper that you are not heavily invested in, volunteer to take minutes. That way you can make a valuable contribution, even for an area where you don't have domain expertise.
As a bonus, you get to follow the minuter's code (something I just made up) about spelling other people's names. As the person taking minutes, you have license to change up to three letters in someone's name, so long as it isn't used maliciously. You can freely take any double letter in a name and convert it to a single letter (e.g. Connor -> Conor), turn a single letter to a double letter (David -> Davvid), or completely rearrange any consecutive series of vowels. And people will thank you for it! You are also given free license to interrupt people in order to ask them who they are. Give it a try!

Closing

I've got a bunch of papers to write for the next mailing, and I won't even be in Varna. So if you're interested in championing some freestanding papers, let me know, and I can coach you on the topics.
submitted by ben_craig to cpp [link] [comments]

Vault 7 - CIA Hacking Tools Revealed

Vault 7 - CIA Hacking Tools Revealed
March 07, 2017
from Wikileaks Website


https://preview.redd.it/9ufj63xnfdb41.jpg?width=500&format=pjpg&auto=webp&s=46bbc937f4f060bad1eaac3e0dce732e3d8346ee

Press Release
Today, Tuesday 7 March 2017, WikiLeaks begins its new series of leaks on the U.S. Central Intelligence Agency.
Code-named "Vault 7" by WikiLeaks, it is the largest ever publication of confidential documents on the agency.
The first full part of the series, "Year Zero", comprises 8,761 documents and files from an isolated, high-security network situated inside the CIA's Center for Cyber Intelligence (below image) in Langley, Virgina.
It follows an introductory disclosure last month of CIA targeting French political parties and candidates in the lead up to the 2012 presidential election.
Recently, the CIA lost control of the majority of its hacking arsenal including,
  1. malware
  2. viruses
  3. trojans
  4. weaponized "zero day" exploits
  5. malware remote control systems

...and associated documentation.
This extraordinary collection, which amounts to more than several hundred million lines of code, gives its possessor the entire hacking capacity of the CIA.
The archive appears to have been circulated among former U.S. government hackers and contractors in an unauthorized manner, one of whom has provided WikiLeaks with portions of the archive.
"Year Zero" introduces the scope and direction of the CIA's global covert hacking program, its malware arsenal and dozens of "zero day" weaponized exploits against a wide range of U.S. and European company products, include,

  1. Apple's iPhone
  2. Google's Android
  3. Microsoft's Windows
  4. Samsung TVs,

...which are turned into covert microphones.
Since 2001 the CIA has gained political and budgetary preeminence over the U.S. National Security Agency (NSA).
The CIA found itself building not just its now infamous drone fleet, but a very different type of covert, globe-spanning force - its own substantial fleet of hackers.
The agency's hacking division freed it from having to disclose its often controversial operations to the NSA (its primary bureaucratic rival) in order to draw on the NSA's hacking capacities.
By the end of 2016, the CIA's hacking division, which formally falls under the agency's Center for Cyber Intelligence (CCI - below image), had over 5000 registered users and had produced more than a thousand,
hacking systems trojans viruses,
...and other "weaponized" malware.


https://preview.redd.it/3jsojkqxfdb41.jpg?width=366&format=pjpg&auto=webp&s=e92eafbb113ab3e972045cc242dde0f0dd511e96

Such is the scale of the CIA's undertaking that by 2016, its hackers had utilized more codes than those used to run Facebook.
The CIA had created, in effect, its "own NSA" with even less accountability and without publicly answering the question as to whether such a massive budgetary spend on duplicating the capacities of a rival agency could be justified.
In a statement to WikiLeaks the source details policy questions that they say urgently need to be debated in public, including whether the CIA's hacking capabilities exceed its mandated powers and the problem of public oversight of the agency.
The source wishes to initiate a public debate about the security, creation, use, proliferation and democratic control of cyberweapons.
Once a single cyber 'weapon' is 'loose' it can spread around the world in seconds, to be used by rival states, cyber mafia and teenage hackers alike.

Julian Assange, WikiLeaks editor stated that,
"There is an extreme proliferation risk in the development of cyber 'weapons'.
Comparisons can be drawn between the uncontrolled proliferation of such 'weapons', which results from the inability to contain them combined with their high market value, and the global arms trade.
But the significance of 'Year Zero' goes well beyond the choice between cyberwar and cyberpeace. The disclosure is also exceptional from a political, legal and forensic perspective."

Wikileaks has carefully reviewed the "Year Zero" disclosure and published substantive CIA documentation while avoiding the distribution of 'armed' cyberweapons until a consensus emerges on the technical and political nature of the CIA's program and how such 'weapons' should analyzed, disarmed and published.

Wikileaks has also decided to Redact (see far below) and Anonymize some identifying information in "Year Zero" for in depth analysis. These redactions include ten of thousands of CIA targets and attack machines throughout,
Latin America Europe the United States

While we are aware of the imperfect results of any approach chosen, we remain committed to our publishing model and note that the quantity of published pages in "Vault 7" part one ("Year Zero") already eclipses the total number of pages published over the first three years of the Edward Snowden NSA leaks.

Analysis

CIA malware targets iPhone, Android, smart TVs
CIA malware and hacking tools are built by EDG (Engineering Development Group), a software development group within CCI (Center for Cyber Intelligence), a department belonging to the CIA's DDI (Directorate for Digital Innovation).
The DDI is one of the five major directorates of the CIA (see above image of the CIA for more details).
The EDG is responsible for the development, testing and operational support of all backdoors, exploits, malicious payloads, trojans, viruses and any other kind of malware used by the CIA in its covert operations world-wide.
The increasing sophistication of surveillance techniques has drawn comparisons with George Orwell's 1984, but "Weeping Angel", developed by the CIA's Embedded Devices Branch (EDB), which infests smart TVs, transforming them into covert microphones, is surely its most emblematic realization.
The attack against Samsung smart TVs was developed in cooperation with the United Kingdom's MI5/BTSS.
After infestation, Weeping Angel places the target TV in a 'Fake-Off' mode, so that the owner falsely believes the TV is off when it is on. In 'Fake-Off' mode the TV operates as a bug, recording conversations in the room and sending them over the Internet to a covert CIA server.
As of October 2014 the CIA was also looking at infecting the vehicle control systems used by modern cars and trucks. The purpose of such control is not specified, but it would permit the CIA to engage in nearly undetectable assassinations.
The CIA's Mobile Devices Branch (MDB) developed numerous attacks to remotely hack and control popular smart phones. Infected phones can be instructed to send the CIA the user's geolocation, audio and text communications as well as covertly activate the phone's camera and microphone.
Despite iPhone's minority share (14.5%) of the global smart phone market in 2016, a specialized unit in the CIA's Mobile Development Branch produces malware to infest, control and exfiltrate data from iPhones and other Apple products running iOS, such as iPads.
CIA's arsenal includes numerous local and remote "zero days" developed by CIA or obtained from GCHQ, NSA, FBI or purchased from cyber arms contractors such as Baitshop.
The disproportionate focus on iOS may be explained by the popularity of the iPhone among social, political, diplomatic and business elites.
A similar unit targets Google's Android which is used to run the majority of the world's smart phones (~85%) including Samsung, HTC and Sony. 1.15 billion Android powered phones were sold last year.
"Year Zero" shows that as of 2016 the CIA had 24 "weaponized" Android "zero days" which it has developed itself and obtained from GCHQ, NSA and cyber arms contractors.
These techniques permit the CIA to bypass the encryption of, WhatsApp
  1. Signal
  2. Telegram
  3. Wiebo
  4. Confide
  5. Cloackman
...by hacking the "smart" phones that they run on and collecting audio and message traffic before encryption is applied.
CIA malware targets Windows, OSx, Linux, routers
The CIA also runs a very substantial effort to infect and control Microsoft Windows users with its malware.
This includes multiple local and remote weaponized "zero days", air gap jumping viruses such as "Hammer Drill" which infects software distributed on CD/DVDs, infectors for removable media such as USBs, systems to hide data in images or in covert disk areas ("Brutal Kangaroo") and to keep its malware infestations going.
Many of these infection efforts are pulled together by the CIA's Automated Implant Branch (AIB), which has developed several attack systems for automated infestation and control of CIA malware, such as "Assassin" and "Medusa".
Attacks against Internet infrastructure and webservers are developed by the CIA's Network Devices Branch (NDB).
The CIA has developed automated multi-platform malware attack and control systems covering Windows, Mac OS X, Solaris, Linux and more, such as EDB's "HIVE" and the related "Cutthroat" and "Swindle" tools, which are described in the examples section far below.
CIA 'hoarded' vulnerabilities ("zero days")
In the wake of Edward Snowden's leaks about the NSA, the U.S. technology industry secured a commitment from the Obama administration that the executive would disclose on an ongoing basis - rather than hoard - serious vulnerabilities, exploits, bugs or "zero days" to Apple, Google, Microsoft, and other US-based manufacturers.
Serious vulnerabilities not disclosed to the manufacturers places huge swathes of the population and critical infrastructure at risk to foreign intelligence or cyber criminals who independently discover or hear rumors of the vulnerability.
If the CIA can discover such vulnerabilities so can others.
The U.S. government's commitment to the Vulnerabilities Equities Process came after significant lobbying by US technology companies, who risk losing their share of the global market over real and perceived hidden vulnerabilities.
The government stated that it would disclose all pervasive vulnerabilities discovered after 2010 on an ongoing basis.
"Year Zero" documents show that the CIA breached the Obama administration's commitments. Many of the vulnerabilities used in the CIA's cyber arsenal are pervasive and some may already have been found by rival intelligence agencies or cyber criminals.
As an example, specific CIA malware revealed in "Year Zero" is able to penetrate, infest and control both the Android phone and iPhone software that runs or has run presidential Twitter accounts.
The CIA attacks this software by using undisclosed security vulnerabilities ("zero days") possessed by the CIA but if the CIA can hack these phones then so can everyone else who has obtained or discovered the vulnerability.
As long as the CIA keeps these vulnerabilities concealed from Apple and Google (who make the phones) they will not be fixed, and the phones will remain hackable.
The same vulnerabilities exist for the population at large, including the U.S. Cabinet, Congress, top CEOs, system administrators, security officers and engineers.
By hiding these security flaws from manufacturers like Apple and Google the CIA ensures that it can hack everyone at the expense of leaving everyone hackable.
'Cyberwar' programs are a serious proliferation risk
Cyber 'weapons' are not possible to keep under effective control.
While nuclear proliferation has been restrained by the enormous costs and visible infrastructure involved in assembling enough fissile material to produce a critical nuclear mass, cyber 'weapons', once developed, are very hard to retain.
Cyber 'weapons' are in fact just computer programs which can be pirated like any other. Since they are entirely comprised of information they can be copied quickly with no marginal cost.
Securing such 'weapons' is particularly difficult since the same people who develop and use them have the skills to exfiltrate copies without leaving traces - sometimes by using the very same 'weapons' against the organizations that contain them.
There are substantial price incentives for government hackers and consultants to obtain copies since there is a global "vulnerability market" that will pay hundreds of thousands to millions of dollars for copies of such 'weapons'.
Similarly, contractors and companies who obtain such 'weapons' sometimes use them for their own purposes, obtaining advantage over their competitors in selling 'hacking' services.
Over the last three years the United States intelligence sector, which consists of government agencies such as the CIA and NSA and their contractors, such as Booz Allan Hamilton, has been subject to unprecedented series of data exfiltrations by its own workers.
A number of intelligence community members not yet publicly named have been arrested or subject to federal criminal investigations in separate incidents.
Most visibly, on February 8, 2017 a U.S. federal grand jury indicted Harold T. Martin III with 20 counts of mishandling classified information.
The Department of Justice alleged that it seized some 50,000 gigabytes of information from Harold T. Martin III that he had obtained from classified programs at NSA and CIA, including the source code for numerous hacking tools.
Once a single cyber 'weapon' is 'loose' it can spread around the world in seconds, to be used by peer states, cyber mafia and teenage hackers alike.
U.S. Consulate in Frankfurt is a covert CIA hacker base
In addition to its operations in Langley, Virginia the CIA also uses the U.S. consulate in Frankfurt as a covert base for its hackers covering Europe, the Middle East and Africa.
CIA hackers operating out of the Frankfurt consulate ("Center for Cyber Intelligence Europe" or CCIE) are given diplomatic ("black") passports and State Department cover.
The instructions for incoming CIA hackers make Germany's counter-intelligence efforts appear inconsequential: "Breeze through German Customs because you have your cover-for-action story down pat, and all they did was stamp your passport" Your Cover Story (for this trip) Q: Why are you here? A: Supporting technical consultations at the Consulate. Two earlier WikiLeaks publications give further detail on CIA approaches to customs and secondary screening procedures.
Once in Frankfurt CIA hackers can travel without further border checks to the 25 European countries that are part of the Shengen open border area - including France, Italy and Switzerland.
A number of the CIA's electronic attack methods are designed for physical proximity.
These attack methods are able to penetrate high security networks that are disconnected from the internet, such as police record database. In these cases, a CIA officer, agent or allied intelligence officer acting under instructions, physically infiltrates the targeted workplace.
The attacker is provided with a USB containing malware developed for the CIA for this purpose, which is inserted into the targeted computer. The attacker then infects and exfiltrates data to removable media.
For example, the CIA attack system Fine Dining, provides 24 decoy applications for CIA spies to use.
To witnesses, the spy appears to be running a program showing videos (e.g VLC), presenting slides (Prezi), playing a computer game (Breakout2, 2048) or even running a fake virus scanner (Kaspersky, McAfee, Sophos).
But while the decoy application is on the screen, the underlying system is automatically infected and ransacked.
How the CIA dramatically increased proliferation risks
In what is surely one of the most astounding intelligence own goals in living memory, the CIA structured its classification regime such that for the most market valuable part of "Vault 7", the CIA's, weaponized malware (implants + zero days) Listening Posts (LP) Command and Control (C2) systems, ...the agency has little legal recourse.
The CIA made these systems unclassified.
Why the CIA chose to make its cyber-arsenal unclassified reveals how concepts developed for military use do not easily crossover to the 'battlefield' of cyber 'war'.
To attack its targets, the CIA usually requires that its implants communicate with their control programs over the internet.
If CIA implants, Command & Control and Listening Post software were classified, then CIA officers could be prosecuted or dismissed for violating rules that prohibit placing classified information onto the Internet.
Consequently the CIA has secretly made most of its cyber spying/war code unclassified. The U.S. government is not able to assert copyright either, due to restrictions in the U.S. Constitution.
This means that cyber 'arms' manufactures and computer hackers can freely "pirate" these 'weapons' if they are obtained. The CIA has primarily had to rely on obfuscation to protect its malware secrets.
Conventional weapons such as missiles may be fired at the enemy (i.e. into an unsecured area). Proximity to or impact with the target detonates the ordnance including its classified parts. Hence military personnel do not violate classification rules by firing ordnance with classified parts.
Ordnance will likely explode. If it does not, that is not the operator's intent.
Over the last decade U.S. hacking operations have been increasingly dressed up in military jargon to tap into Department of Defense funding streams.
For instance, attempted "malware injections" (commercial jargon) or "implant drops" (NSA jargon) are being called "fires" as if a weapon was being fired.
However the analogy is questionable.
Unlike bullets, bombs or missiles, most CIA malware is designed to live for days or even years after it has reached its 'target'. CIA malware does not "explode on impact" but rather permanently infests its target. In order to infect target's device, copies of the malware must be placed on the target's devices, giving physical possession of the malware to the target.
To exfiltrate data back to the CIA or to await further instructions the malware must communicate with CIA Command & Control (C2) systems placed on internet connected servers.
But such servers are typically not approved to hold classified information, so CIA command and control systems are also made unclassified.
A successful 'attack' on a target's computer system is more like a series of complex stock maneuvers in a hostile take-over bid or the careful planting of rumors in order to gain control over an organization's leadership rather than the firing of a weapons system.
If there is a military analogy to be made, the infestation of a target is perhaps akin to the execution of a whole series of military maneuvers against the target's territory including observation, infiltration, occupation and exploitation.
Evading forensics and anti-virus
A series of standards lay out CIA malware infestation patterns which are likely to assist forensic crime scene investigators as well as, Apple
  1. Microsoft
  2. Google
  3. Samsung
  4. Nokia
  5. Blackberry
  6. Siemens
  7. anti-virus companies,
...attribute and defend against attacks.
"Tradecraft DO's and DON'Ts" contains CIA rules on how its malware should be written to avoid fingerprints implicating the "CIA, US government, or its witting partner companies" in "forensic review".
Similar secret standards cover the, use of encryption to hide CIA hacker and malware communication (pdf) describing targets & exfiltrated data (pdf) executing payloads (pdf) persisting (pdf), ...in the target's machines over time.
CIA hackers developed successful attacks against most well known anti-virus programs.
These are documented in, AV defeats Personal Security Products Detecting and defeating PSPs PSP/DebuggeRE Avoidance For example, Comodo was defeated by CIA malware placing itself in the Window's "Recycle Bin". While Comodo 6.x has a "Gaping Hole of DOOM".
CIA hackers discussed what the NSA's "Equation Group" hackers did wrong and how the CIA's malware makers could avoid similar exposure.

Examples

The CIA's Engineering Development Group (EDG) management system contains around 500 different projects (only some of which are documented by "Year Zero") each with their own sub-projects, malware and hacker tools.
The majority of these projects relate to tools that are used for,
penetration infestation ("implanting") control exfiltration
Another branch of development focuses on the development and operation of Listening Posts (LP) and Command and Control (C2) systems used to communicate with and control CIA implants.
Special projects are used to target specific hardware from routers to smart TVs.
Some example projects are described below, but see the table of contents for the full list of projects described by WikiLeaks' "Year Zero".
UMBRAGE
The CIA's hand crafted hacking techniques pose a problem for the agency.
Each technique it has created forms a "fingerprint" that can be used by forensic investigators to attribute multiple different attacks to the same entity.
This is analogous to finding the same distinctive knife wound on multiple separate murder victims. The unique wounding style creates suspicion that a single murderer is responsible.
As soon one murder in the set is solved then the other murders also find likely attribution.
The CIA's Remote Devices Branch's UMBRAGE group collects and maintains a substantial library of attack techniques 'stolen' from malware produced in other states including the Russian Federation.
With UMBRAGE and related projects the CIA cannot only increase its total number of attack types but also misdirect attribution by leaving behind the "fingerprints" of the groups that the attack techniques were stolen from.
UMBRAGE components cover,
keyloggers
  1. password collection
  2. webcam capture
  3. data destruction
  4. persistence
  5. privilege escalation
  6. stealth
  7. anti-virus (PSP) avoidance
  8. survey techniques

Fine Dining
Fine Dining comes with a standardized questionnaire i.e menu that CIA case officers fill out.
The questionnaire is used by the agency's OSB (Operational Support Branch) to transform the requests of case officers into technical requirements for hacking attacks (typically "exfiltrating" information from computer systems) for specific operations.
The questionnaire allows the OSB to identify how to adapt existing tools for the operation, and communicate this to CIA malware configuration staff.
The OSB functions as the interface between CIA operational staff and the relevant technical support staff.
Among the list of possible targets of the collection are,
  • 'Asset'
  • 'Liason Asset'
  • 'System Administrator'
  • 'Foreign Information Operations'
  • 'Foreign Intelligence Agencies'
  • 'Foreign Government Entities'
Notably absent is any reference to extremists or transnational criminals. The 'Case Officer' is also asked to specify the environment of the target like the type of computer, operating system used, Internet connectivity and installed anti-virus utilities (PSPs) as well as a list of file types to be exfiltrated like Office documents, audio, video, images or custom file types.
The 'menu' also asks for information if recurring access to the target is possible and how long unobserved access to the computer can be maintained.
This information is used by the CIA's 'JQJIMPROVISE' software (see below) to configure a set of CIA malware suited to the specific needs of an operation.
Improvise (JQJIMPROVISE)
  1. 'Improvise' is a toolset for configuration, post-processing, payload setup and execution vector
  2. selection for survey/exfiltration tools supporting all major operating systems like,
  3. Windows (Bartender)
  4. MacOS (JukeBox)
  5. Linux (DanceFloor)
  6. Its configuration utilities like Margarita allows the NOC (Network Operation Center) to customize tools
based on requirements from 'Fine Dining' questionnaires.
HIVE
HIVE is a multi-platform CIA malware suite and its associated control software.
The project provides customizable implants for Windows, Solaris, MikroTik (used in internet routers) and Linux platforms and a Listening Post (LP)/Command and Control (C2) infrastructure to communicate with these implants.
The implants are configured to communicate via HTTPS with the webserver of a cover domain; each operation utilizing these implants has a separate cover domain and the infrastructure can handle any number of cover domains.
Each cover domain resolves to an IP address that is located at a commercial VPS (Virtual Private Server) provider.
The public-facing server forwards all incoming traffic via a VPN to a 'Blot' server that handles actual connection requests from clients.
It is setup for optional SSL client authentication: if a client sends a valid client certificate (only implants can do that), the connection is forwarded to the 'Honeycomb' toolserver that communicates with the implant.
If a valid certificate is missing (which is the case if someone tries to open the cover domain website by accident), the traffic is forwarded to a cover server that delivers an unsuspicious looking website.
The Honeycomb toolserver receives exfiltrated information from the implant; an operator can also task the implant to execute jobs on the target computer, so the toolserver acts as a C2 (command and control) server for the implant.
Similar functionality (though limited to Windows) is provided by the RickBobby project.
See the classified user and developer guides for HIVE.

Frequently Asked Questions

Why now?
WikiLeaks published as soon as its verification and analysis were ready. In February the Trump administration has issued an Executive Order calling for a "Cyberwar" review to be prepared within 30 days.
While the review increases the timeliness and relevance of the publication it did not play a role in setting the publication date.
Redactions
Names, email addresses and external IP addresses have been redacted in the released pages (70,875 redactions in total) until further analysis is complete. Over-redaction: Some items may have been redacted that are not employees, contractors, targets or otherwise related to the agency, but are, for example, authors of documentation for otherwise public projects that are used by the agency.
Identity vs. person: the redacted names are replaced by user IDs (numbers) to allow readers to assign multiple pages to a single author. Given the redaction process used a single person may be represented by more than one assigned identifier but no identifier refers to more than one real person.
Archive attachments (zip, tar.gz, ...), are replaced with a PDF listing all the file names in the archive. As the archive content is assessed it may be made available; until then the archive is redacted.
Attachments with other binary content, are replaced by a hex dump of the content to prevent accidental invocation of binaries that may have been infected with weaponized CIA malware. As the content is assessed it may be made available; until then the content is redacted.
Tens of thousands of routable IP addresses references, (including more than 22 thousand within the United States) that correspond to possible targets, CIA covert listening post servers, intermediary and test systems, are redacted for further exclusive investigation.
Binary files of non-public origin, are only available as dumps to prevent accidental invocation of CIA malware infected binaries.
Organizational Chart
The organizational chart (far above image) corresponds to the material published by WikiLeaks so far.
Since the organizational structure of the CIA below the level of Directorates is not public, the placement of the EDG and its branches within the org chart of the agency is reconstructed from information contained in the documents released so far.
It is intended to be used as a rough outline of the internal organization; please be aware that the reconstructed org chart is incomplete and that internal reorganizations occur frequently.
Wiki pages
"Year Zero" contains 7818 web pages with 943 attachments from the internal development groupware. The software used for this purpose is called Confluence, a proprietary software from Atlassian.
Webpages in this system (like in Wikipedia) have a version history that can provide interesting insights on how a document evolved over time; the 7818 documents include these page histories for 1136 latest versions.
The order of named pages within each level is determined by date (oldest first). Page content is not present if it was originally dynamically created by the Confluence software (as indicated on the re-constructed page).
What time period is covered?
The years 2013 to 2016. The sort order of the pages within each level is determined by date (oldest first).
WikiLeaks has obtained the CIA's creation/last modification date for each page but these do not yet appear for technical reasons. Usually the date can be discerned or approximated from the content and the page order.
If it is critical to know the exact time/date contact WikiLeaks.
What is "Vault 7"
"Vault 7" is a substantial collection of material about CIA activities obtained by WikiLeaks.
When was each part of "Vault 7" obtained?
Part one was obtained recently and covers through 2016. Details on the other parts will be available at the time of publication.
Is each part of "Vault 7" from a different source?
Details on the other parts will be available at the time of publication.
What is the total size of "Vault 7"?
The series is the largest intelligence publication in history.
How did WikiLeaks obtain each part of "Vault 7"?
Sources trust WikiLeaks to not reveal information that might help identify them.
Isn't WikiLeaks worried that the CIA will act against its staff to stop the series?
No. That would be certainly counter-productive.
Has WikiLeaks already 'mined' all the best stories?
No. WikiLeaks has intentionally not written up hundreds of impactful stories to encourage others to find them and so create expertise in the area for subsequent parts in the series. They're there.
Look. Those who demonstrate journalistic excellence may be considered for early access to future parts.
Won't other journalists find all the best stories before me?
Unlikely. There are very considerably more stories than there are journalists or academics who are in a position to write them.
submitted by CuteBananaMuffin to conspiracy [link] [comments]

Waltonchain All-In-One Thread

This All-In-One Thread is still undergoing correction. Feel free to post below and let me know if something needs to be corrected.
What is Waltonchain?
Waltonchain is the only truly decentralized platform combining blockchain with the Internet of Things (IoT) via RFID technology. Their blockchain is implemented in the foundational layer, through their unique, patented RFID chips, which are able to read and write directly to the blockchain, creating a genuine, trustworthy, and traceable business ecosystem, with complete data sharing and absolute information transparency.
Click here for the News, PR & Awards Thread.
Official Sources
WTC Wallet
Noteworthy Posts
Progress Reports
Unofficial
The Team-->>> Waltonchain Organizational Chart <<<<----
Child Chains
Partnerships
Infographic
Hardware
Videos
List of AMAs
Exchanges
Frequently Asked Questions
Q: When will Token Swap Happen? Did Mainnet Release?
Waltonchain has launched mainnet, token swap has not happened yet in progress. Token swap from Ethereum to Watlon's own chain is trending to occur complete in Q2 2019 Q4 2019-?. To prepare for swap you can hold your tokens on any of the listed exchanges. For additional information as it becomes available one should follow Walton on twitter.
Q:What's the Total Supply of Waltoncoin (WTC)?
The Total Supply is 100 million coins with no further issuance in any case. The Max Supply is currently 70 million coins, with the remaining 30 million left to be mined over the course of many years. Currently, the Circulating Supply is around 25 million.
Q:I hear Walton is moving to its own blockchain?
Main net has just been launched. Stay tuned for details about the token swap and transition to the new chain!
Q:How do I convert my ERC20 WTC tokens to the real thing?
You can either leave your coins on the exchange, and they will take care of the switch for you, or you can leave them in your MEW wallet, and the team will provide details on how the tokens will be swapped over. Just sit tight! Details are coming.
Q: How do I move my WTC to MEW (or the new Walton Wallet)?
For MEW:
I. Send your WTC to your wallet address.
II. Add a custom token using the information below:
Address: 0xb7cb1c96db6b22b0d3d9536e0108d062bd488f74
Name: WTC
Decimals: 18
For Walton Wallet:
Do not send ANY coins to this wallet yet. Wait for instructions from the team. Once everything is safe, you will be able to just create a wallet on the Walton Wallet and send your coins to the public address generated.
Q:What if I want to keep them on my Ledger Nano?
You can do that, and the team will still snapshot your wallet and copy it along with your coins; however, the the Ledger may not support WTC currently. Don't fret. Your coins are 100% safe. What that means is, if there is no Ledger support, the only way to transfer your coins out of the wallet will be to expose your Ledger's private key. I don't recommend doing this, as it will make the ledger no more secure than a paper wallet (still very secure, but a waste of money now).
So basically, your coins are safe. You can still mine to the address. You just won't be able to move them until Ledger support comes. But if you really need access to the coins, you can break out the Ledger's private key on MEW and log into your wallet.
Ledger support will come, we just don't know exactly when. Walton is also making their own Walton hardware wallets. I'll update this with more information as it comes.
Q:My GMN is on MEW. Will I ever be able to secure GMN in a hardware wallet?
As you know, moving your GMN will void your Guardian status because it is attached to the wallet containing at least 5000 WTC; however, the team has stated that they are working on a solution for this and have reassured us that our coins will be safe. We will have to wait for more information regarding whether the transferring of a GMN to a new address will be possible in the future.
Q:What is the utility of WTC? What gives the coin value?
In the WaltonChain Ecosystem WTC will have multiple functions:
More in depth coverage of each point here
Q: Is Waltonchain a platform?
Yes. Waltonchain is a smart contract platform that will have ICOs and dApps.
Q: But I thought Walton just tracked clothing in the supply chain. What else can it do?
Walton is capable of implementation in smart cities, smart waste management systems, and things of that nature. That's certainly beyond supply chain. Walton isn't so much a "supply chain" coin as it is a Big Data coin. The RFIDs are used to gather data, which is very useful in supply chain management. But it can also be used to combine with smart devices and make an Internet of things network.
Q: Why does this need a blockchain?
"It is difficult for the Internet of things under the current central structure to accomplish real autonomous cooperation and effective transactions, because the relevant parties of such cooperation and transactions often belong to different stakeholders with complex and uncertain trust relationships. Therefore, the collaboration and transactions of the current Internet of Things devices can only be carried out under the same trust domain. That is to say, the devices to collaborate and trade must be provided or verified by the same Internet of Things service provider, which significantly reduces the true commercial value of the Internet of Things applications." (Page 2 of the Whitepaper)
To expand, counterfeiting is an obvious answer to this question. There needs to be a way to truly authenticate an item. Blockchain is that answer.
Walton's blockchain also removes data silos. Companies won't have to manage any database anymore. Everything is handled by Walton. Walton uses child chains which are separate from the parent chain. Companies can keep proprietary information secret and private on their child chain, and only broadcast necessary information to the parent chain for public viewing. Blockchains make the sharing of info between companies easy and fast, too. And then obviously, blockchains have perfect transparency and are immutable.
Smart contracts are also extremely useful. In the supply chain industry, after perfectly counting and storing inventory, things can be auto-ordered and paid for simultaneously with wtc, just as an example. Your mind can come up with a whole host of other ideas related to automation.
Furthermore, decentralized, transparent, and immutable data for things like smart waste management systems, which Walton has designed, and air-pollution monitoring systems in smart cities would benefit greatly from the blockchain, for reasons explained in the first point from the whitepaper.
You could also imagine on the customer end that wanting to know where all their goods come from is important. This is in line with counterfeiting, but also with things more benign. Imagine wanting to return an item to a store, but can't remember which grocery store it was from. Lots of simple improvements like that are all use cases for blockchain.
Q: I heard Waltonchain has patented technology. What are the patents?
The Walton team has filed filed for 13 patents, 7 of which have been approved so far. The patents cover many inventions in chip design, but the main one of interest is the Transaction ID-reading RFID chip with memory storage. This allows the blockchain to be implemented in the Foundational layer through the RFIDs themselves. The chips can generate their own random ID hash within a secure Key Generation Center within the chip, and the hash along with the data are uploaded simultaneously to the blockchain via their RFID reader. This makes WaltonChain fully decentralized and secure.
Q:What are the advantages of the RFID IC tag chip designed in this project?
Existing RFID chip industry cannot meet the development of Internet of Things applications, especially applications for the Value Internet of Things:
The project’s IC design has the following significant advantages:
Q:How much do the chips cost?
Waltonchain in a nutshell with COO Monitor Chan:"We develop and produce hardware such as chips ourselves. This really differentiates us from other companies at the moment. Basically, Silitec, our technical support company, was founded in 2015 and is specialized in manufacturing chips. They already have a R&D team of around 20+ people, so in that way we are not 'increasing' cost. Next important detail is that Waltonchain’s blockchain technology is written into our chips. This means that unlike traditional RFID chips that have their own specific ID and cost around $0.15 to $0.20, the chips we develop will be below 5 cents. With the volume of sales increasing, the overall cost will spread over many units, and the system's cost and ID’s cost will go down consequently, or simply put, economics of scale will do the work."
Q:I need help with mining. What resources are out there?
WaltonchainMining is for this purpose. Community members here have done testing with many different configurations and have provided ample information for anything you need with setting up your cpu/gpu rig.
Q:How many GMNs are left?
The Waltonchain Explorer now tracks these addresses.
Q:Who are the Knights?
Credit for the original making of this post goes to u/thelatemercutio
submitted by WTCmen to WaltonchainUncensored [link] [comments]

MAME 0.207

MAME 0.207

It’s almost the end of February, and more importantly it’s time for MAME 0.207 to be released! We’ve added two Nintendo Game & Watch titles this month: Fire (wide screen) and Snoopy Tennis. If you’re at all interested in plug-and-play TV games, this is going to be a huge update, with all the newly-supported JAKKS Pacific titles, including Disney Princess, Dragon Ball Z, Nicktoons, Spider-Man, and Wheel of Fortune, as well as a number of matching Game-Keys. The other big batch of additions this month comes in the form of a whole lot of e-kara cartridge dumps from Japan. For younger players, we’re steadily filling out the V.Smile software list, with eighteen newly supported titles. The VGM software list has been updated with the latest video game music rips, and we’ve added some more original floppy dumps and clean cracks to the Apple II software lists.
With the latest improvements to the MIPS R4000 CPU, WD33C93 SCSI and SGI Newport graphics emulation, it’s possible to install and run IRIX in MAME. This is a milestone achievement, and wouldn’t have been possible without some amazing dedication and collaboration on the part of the contributors and team members involved. With the addition of graphics and mouse support, Windows 1.0 runs on MAME’s Tandy 2000 emulation. MAME continues to add additional variants of supported systems, including the HP 9825T and the Esselte Modulab educational system.
Newly supported arcade games include an earlier prototype of Rise of the Robots, bootlegs of Ghost Chaser Densei and The Glob, and additional versions of Raiden Fighters 2, Guardian Storm, Pasha Pasha Champ, Lethal Enforcers, and X-Men. General usability improvements include friendlier Apple II disassembly, the restoration of key map support in SDL builds (Linux/macOS), and better initial window positioning on Windows.
You can get the source and Windows binary packages from the download page.

MAMETesters Bugs Fixed

New working machines

New working clones

Machines promoted to working

Clones promoted to working

New machines marked as NOT_WORKING

New clones marked as NOT_WORKING

New working software list additions

Software list items promoted to working

New NOT_WORKING software list additions

Translations added or modified

Source Changes

submitted by cuavas to emulation [link] [comments]

MAME 0.207

MAME 0.207

It’s almost the end of February, and more importantly it’s time for MAME 0.207 to be released! We’ve added two Nintendo Game & Watch titles this month: Fire (wide screen) and Snoopy Tennis. If you’re at all interested in plug-and-play TV games, this is going to be a huge update, with all the newly-supported JAKKS Pacific titles, including Disney Princess, Dragon Ball Z, Nicktoons, Spider-Man, and Wheel of Fortune, as well as a number of matching Game-Keys. The other big batch of additions this month comes in the form of a whole lot of e-kara cartridge dumps from Japan. For younger players, we’re steadily filling out the V.Smile software list, with eighteen newly supported titles. The VGM software list has been updated with the latest video game music rips, and we’ve added some more original floppy dumps and clean cracks to the Apple II software lists.
With the latest improvements to the MIPS R4000 CPU, WD33C93 SCSI and SGI Newport graphics emulation, it’s possible to install and run IRIX in MAME. This is a milestone achievement, and wouldn’t have been possible without some amazing dedication and collaboration on the part of the contributors and team members involved. With the addition of graphics and mouse support, Windows 1.0 runs on MAME’s Tandy 2000 emulation. MAME continues to add additional variants of supported systems, including the HP 9825T and the Esselte Modulab educational system.
Newly supported arcade games include an earlier prototype of Rise of the Robots, bootlegs of Ghost Chaser Densei and The Glob, and additional versions of Raiden Fighters 2, Guardian Storm, Pasha Pasha Champ, Lethal Enforcers, and X-Men. General usability improvements include friendlier Apple II disassembly, the restoration of key map support in SDL builds (Linux/macOS), and better initial window positioning on Windows.
You can get the source and Windows binary packages from the download page.

MAMETesters Bugs Fixed

New working machines

New working clones

Machines promoted to working

Clones promoted to working

New machines marked as NOT_WORKING

New clones marked as NOT_WORKING

New working software list additions

Software list items promoted to working

New NOT_WORKING software list additions

Translations added or modified

Source Changes

submitted by cuavas to MAME [link] [comments]

MAME 0.207

MAME 0.207

It’s almost the end of February, and more importantly it’s time for MAME 0.207 to be released! We’ve added two Nintendo Game & Watch titles this month: Fire (wide screen) and Snoopy Tennis. If you’re at all interested in plug-and-play TV games, this is going to be a huge update, with all the newly-supported JAKKS Pacific titles, including Disney Princess, Dragon Ball Z, Nicktoons, Spider-Man, and Wheel of Fortune, as well as a number of matching Game-Keys. The other big batch of additions this month comes in the form of a whole lot of e-kara cartridge dumps from Japan. For younger players, we’re steadily filling out the V.Smile software list, with eighteen newly supported titles. The VGM software list has been updated with the latest video game music rips, and we’ve added some more original floppy dumps and clean cracks to the Apple II software lists.
With the latest improvements to the MIPS R4000 CPU, WD33C93 SCSI and SGI Newport graphics emulation, it’s possible to install and run IRIX in MAME. This is a milestone achievement, and wouldn’t have been possible without some amazing dedication and collaboration on the part of the contributors and team members involved. With the addition of graphics and mouse support, Windows 1.0 runs on MAME’s Tandy 2000 emulation. MAME continues to add additional variants of supported systems, including the HP 9825T and the Esselte Modulab educational system.
Newly supported arcade games include an earlier prototype of Rise of the Robots, bootlegs of Ghost Chaser Densei and The Glob, and additional versions of Raiden Fighters 2, Guardian Storm, Pasha Pasha Champ, Lethal Enforcers, and X-Men. General usability improvements include friendlier Apple II disassembly, the restoration of key map support in SDL builds (Linux/macOS), and better initial window positioning on Windows.
You can get the source and Windows binary packages from the download page.

MAMETesters Bugs Fixed

New working machines

New working clones

Machines promoted to working

Clones promoted to working

New machines marked as NOT_WORKING

New clones marked as NOT_WORKING

New working software list additions

Software list items promoted to working

New NOT_WORKING software list additions

Translations added or modified

Source Changes

submitted by cuavas to cade [link] [comments]

The best indicator of momentum reader - super trick 2019 - iq option strategy 2020 THE TRUTH ABOUT BINARY OPTIONS Best Options Trading Books #Binary Options For Dummies Pdf learn binary option &binary option 2020 MAKE MONEY Binary Option Strategy  Volatility 100 Index 3 Odd Pairs Digit Strategy  FREE 2020

The Single Most Critical Factor to Binary Options Trading Success May I suggest that prior to reading this book you make yourself familiar with the look and feel of a real life Binary Options trading platform, this will help you to better understand the guidelines and concepts described here. You can simply register to an Pdf Books About Binary Options Pdf books about binary options Pagar imposto opções binárias. Index 3 Top Reasons to Trade Binary Options 4 Binary Options: A History 5 How to Execute a Classic Trade with Binary Options 7 Advanced Binary Trading Tools 7 RollOver Tool 8 Double Up Tool 9 An Overview of One-Touch Trading 12 Option Builder: The Basics 13 Open Platform: The Basics 14 Asset Types From reader reviews: Agustin Thornsberry: Nowadays reading books become more than want or need but also be a life style. This reading routine give WAY TO TRADE by Barry Norman ebook PDF download. TRADING BINARY OPTIONS WITH MARKET INDICATORS: AN EASY WAY TO TRADE by Barry Norman Doc. TRADING BINARY OPTIONS WITH MARKET INDICATORS: AN EASY Binary Options are easy to trade but hard to trade profitably. That's the danger. If you start to trade without learning the correct way to do so then you will loose your money. Don't let this put you off. This eBook will show you how to set about learning what you must know and must do before you start to trade. Trading binary options requires a easy to use trading strategy with at least 55% win rate to make money with binary trading! (You also need to keep your emotions under control and avoid over trading!) keep on reading to learn how to get your hands on my binary trading strategy PDF at absolutely no cost!

[index] [26426] [9454] [19532] [2321] [2274] [19017] [3062] [3688] [6871] [20798]

The best indicator of momentum reader - super trick 2019 - iq option strategy 2020

Fx master code is a good binary options strategy for beginners and experienced traders.This might be the best and most profitable one minute trading strategy new traders can use to start winning ... binary options trading with the intention of profitably to achieve successfully, and know the binary trading options scam aware, that occurred in various countries in between binary options ... learn binary options trading course pdf, learn binary option trading. Comments are turned off. Learn more. Autoplay When autoplay is enabled, a suggested video will automatically play next. Best Binary Options Strategy 2020 - 2 Minute Strategy LIVE TRAINING! - Duration: 43:42. ... When and When's Not To Use Martingale in Binary Options Trading - Duration: 20:25. The Binary Lab 21,861 ... 💲🤤Binary Tick Reader ... to meet the requirements before contacting me because the idea is to help all those who want to make money with binary options. as we help the community more ...

Flag Counter