My setup!submitted by Shirt_Shanks to hackintosh [link] [comments]
Introduction:I realise build guides are a dime a dozen, but it’s always reassuring to see one by someone who’s used a combination of components as similar to yours as possible, and even more so when that someone happens to be a newbie. So here I am, with the steps I followed to get macOS Catalina up and running on the tower I’d built.
I’ll take this step by step, and will make an effort to avoid confusing language. Of course, if you have any questions, feel free to ask, after you’ve read the whole thing! Just bear in mind that I, too, am a novice.
Moreover, I have next to no experience with Ryzen builds, or prebuilt machines like laptops, so again, this guide is specific to modern Intel builds and chipsets. If you need help selecting components, look no further than this brilliant, concise primer by Mykola. My guide is by and large limited to the processes I followed, though I’ll try to include alternative steps for anyone that may need them.
Lastly, this guide may be extra handy for Indian Hackintosh enthusiasts — all my components were purchased in in India itself. So if you’re a fellow Indian interested in building one of these for yourself, there’s a good chance these components are readily available for you without having to import anything. But first, some vanity shots:
My old faithful 1080p ASUS monitor, I hope to replace it with a better 1440p 100% sRGB one soon!
Pretty low-end as far as cases go, but very practical! NZXT cases are quite expensive in my country...
The innards! It's actually a lot better cable-managed than it looks here.
The innards! It's actually a lot better cable-managed than it looks here.
Before You Get Started:
You HAVE to be a computer enthusiast, and have basic knowledge of how computers work. It’s crucial that you understand that there are no shortcuts to this.
Morgonaut’s videos on YouTube are an example of what not to do — if you blindly follow what someone spoonfeeds you without truly understanding why something works the way it works, you’re setting yourself up for failure, and we won’t be able to help you because you wouldn’t be able to tell us what you’ve done.
This also applies to tonymacx86 tools like Unibeast; they take user-intervention and transparency out of a process that absolutely depends on both of those to work reliably.
Hackintoshing is a precise process to begin with, and what works for someone else may not necessarily work for you. Take the time and effort to read through every line of the more specific guides I’ll be linking further ahead, and toggle exactly what is specific to your hardware. What you don’t get, Hackintosh and its Discord channel will be happy to lend you a hand with.
Don’t be anxious! It’s an intimidating prospect when you’re doing it for the first time, but once you’ve got everything up and running, you’ll realise that the process is actually pretty straightforward.
The Hardware:The first thing you’ll need to do is, of course, build a computer, so build a computer, I did. Here are my components:
The parts that will affect your Hackintosh setup:
The Z390 motherboards don’t have native NVRAM, but there’s a workaround to emulate it. If you’re starting from scratch, this becomes an unnecessary step, so stick with the Z370 series. However if you, like me, weren’t aware of this at the time of buying your components, no stress! The workaround to emulate NVRAM support is a rather easy one.
Besides this, the other oddity you’ll notice is the Fenvi HB-1200. Here’s the deal: MacOS normally plays well only with very specific Broadcom cards for perfect WiFi and Bluetooth connectivity. So if you want AirDrop and Handoff to function properly on your Hackintosh build, you’ll need one of these things. Installing them is very easy, though, and if you’re unable to find one locally, AliExpress sells these in great abundance. It’ll take about 2-3 weeks to reach you, though. Until then, your only option for internet connectivity is via Ethernet. A more high-end alternative of the same is the Fenvi T919.
Finally, macOS has no built-in framework for controlling the RGB lighting in your system. If you want to control the lighting via your motherboard’s RGB header, you’ll have to do it via BIOS. If even this option isn’t available, a hardware remote is your best bet*, I’m using this one.
*You can mess with your RGB settings via Windows and have your settings persist when you reboot into macOS, but for this, Windows will have to be installed on a partition in the same disk as macOS. This often causes a number of complications and is generally not recommended.
We now move on to the nitty and the gritty, the part of this process that puts the “Hack” in Hackintosh:
Setting up macOS Catalina:Prerequisites:
The recommended method for getting started with a Hackintosh build — the vanilla method — involves having an actual Mac device around. It gives you the simplest, most reliable, and trustworthy way to download a fresh copy of macOS Catalina, straight from Apple’s own App Store. The download itself is free and won’t cost you anything. If you don’t own a Mac, borrow a friends’ — this way, you can also natively format your Catalina USB drive to a Mac-compatible format using macOS’ built-in tools, rather than having to rely on third-party methods.
With this in mind, the guide I’d followed is the OpenCore Vanilla Desktop Guide, once again by the brilliant Mykola. I’ll be referring to this multiple times, and will straight up link directly to it where I don’t have anything specific to my experience to add. Remember, my guide is sort of like an addon to Mykola’s Vanilla guide, and is NOT meant to act as a replacement.
A proven alternative method for those don’t have access to a Mac is Midi Jari’s Internet Install method. I have no experience with this, though, so I can’t really comment on what this entails. But it’s also a trusted method and has produced successful results for many folks here, so don’t stress out unduly! It’s just not something that I personally have used, given I simply borrowed my girfriend’s MacBook for this purpose.
The only other hardware you’ll need is a 16GB USB drive. Until macOS Mojave — the previous version — 8GB USB drives were enough to hold macOS, but unfortunately, Catalina is slightly larger than 8GB, so 16GB drives are the new minimum.
A Brief Prologue:
Here’s a grossly oversimplified primer on how macOS (or any OS, really) boots on a Hackintosh system:
BIOS —> Bootloader —> macOS
Similarly, let’s take this step by step.
BIOS:First, your motherboard’s BIOS fires up. This is normally where the “Gigabyte” or “Asus” or whichever else company’s logo pops up, depending on your motherboard’s make. Here, repeatedly tapping on a button — which can vary from manufacturer to manufacturer — should take you to your BIOS’s settings. This is where your setup process begins.
MacOS requires a specific set of BIOS settings to be toggled, which can be a little daunting for first timers. Luckily, Mykola’s got your standard BIOS settings covered in his guide, so simply reset your BIOS to its optimised defaults, and make the necessary changes he’s highlighted here.
Once this is done, we move on to the big one:
The Bootloader, OpenCore:The bootloader is the key to achieving a successful Hackintosh build, and this is where most of your efforts will be directed.
Ordinarily, on most Windows computers and actual Macs, the bootloader is invisible; you wouldn’t even know it exists beyond the existence of the loading screen. Given we’re off the beaten path, we will need to use a custom bootloader put together by several smart people in the community. This custom bootloader is what will let us boot macOS on non-Apple hardware.
Until very recently, Clover had been the standard bootloader for all Hackintosh builds. It’s well-documented, has a GUI that you’re used to operating, and comes with thousands upon thousands of guides and years of documented online support. It is also, however, nearing the end of its life. A lot of its code is deprecated, unmaintained, and can break anytime.
This brings us to OpenCore — a spanking new bootloader that many believe is the future of Hackintoshing. It’s designed to be a whole lot more flexible than Clover, and uses more modern protocols to offer a far stronger degree of futureproofiness — and dramatically faster boot times, to boot. There’s certainly a lot about it I don’t fully understand, but it’s been painstakingly documented over here in acidenthera’s GitHub page, so do pop over and give it a read if you’re interested.
It’s in the final stages of beta testing — v0.5.3 at the time of writing this — and aims to be released as a stable, public v1.0 build in the coming weeks. Given it’s so close to release, as long as you’re not running a laptop or a prebuilt, OpenCore will run just fine for you once properly setup. Seriously — if you’re not scared of a more transparent process where you have far more control over what your bootloader will end up doing, OpenCore is the way to go.
At this juncture, I’ll simply redirect you to Mykola’s guide, full on. It summarises the process of setting up OpenCore as simply as possible without skimping on important details.
I do, however, have three points to add:
My OpenCore EFI folder structure:Here, you can also have a look at my drivers and kexts. You’ll also notice a file called SSDT-UIAC.aml which isn’t explicitly present in Mykola’s writeup, but is something every Hackintosh user needs to build for themselves. This particular file is called a custom SSDT, and I’ll get into it in just a moment.
EFI ├── APPLE │ ├── EXTENSIONS │ │ └── Firmware.scap │ └── UPDATERS │ └── MULTIUPDATER │ ├── Mac-BE088AF8C5EB4FA2.epm │ ├── Mac-BE088AF8C5EB4FA2.smc │ ├── MultiUpdater.efi │ ├── SmcFlasher.efi │ ├── flasher_base.smc │ └── flasher_update.smc ├── BOOT │ └── BOOTx64.efi └── OC ├── ACPI │ ├── SSDT-AWAC.aml │ ├── SSDT-EC-USBX.aml │ └── SSDT-UIAC.aml ├── Drivers │ ├── ApfsDriverLoader.efi │ ├── FwRuntimeServices.efi │ └── HFSPlus.efi ├── Kexts │ ├── AppleALC.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── AppleALC │ ├── IntelMausi.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── IntelMausi │ ├── Lilu.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── Lilu │ ├── SMCProcessor.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── SMCProcessor │ ├── SMCSuperIO.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── SMCSuperIO │ ├── USBInjectAll.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── USBInjectAll │ ├── VirtualSMC.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── VirtualSMC │ ├── WhateverGreen.kext │ │ └── Contents │ │ ├── Info.plist │ │ └── MacOS │ │ └── WhateverGreen │ └── XHCI-unsupported.kext │ └── Contents │ └── Info.plist ├── OpenCore.efi ├── Tools │ └── Shell.efi └── config.plistYou can find my config.plist over here, but once again, be warned — no good ever came off copy-pasting without at least some superficial understanding of the flags I’ve toggled in my .plist.
Once you’ve got all of this sorted, your OpenCore folder is now ready!
Follow the instructions here to make yourself a USB drive to install macOS Catalina from (assuming you’ve already downloaded it from the App Store and quit the installer). Once the process is complete — it should take about 20 minutes — use this super handy Python script from Corp Newt to mount the EFI folder in your USB drive. Then simply copy the contents of your OpenCore folder to the EFI folder.
The final structure should be similar to the folder tree I’d shared above.
Installing macOS:This is very straightforward. Boot from your USB drive, and when you arrive at the OpenCore selection menu, pick the partition in which your macOS installer is sitting.
It is at this point that many first timers may see an error, indicating that you’ve overlooked something while setting up your OpenCore configuration. Don’t stress! Take a picture of the error you’re seeing, keep your hardware configuration and your EFI folder’s contents handy, and approach the subreddit or the Discord channel for help. It’s more often than not just a couple flags that need to be sorted out, after which you’ll be good to go.
Once you arrive at your macOS installer, before you do anything, find Disk Utility in it (it’s in one of the menus up top) and format your storage drive to Mac OS Extended (Journaled). Once that’s done, go right ahead and install the OS onto your disk!
There’s only a few things left to do after. One of them, Mykola’s already outlined — set up your NVRAM emulation if your motherboard doesn’t have native NVRAM. The other is setting up your custom SSDT. Let me explain why this is necessary.
Setting up your Custom SSDT:MacOS, unlike Windows, has an interesting limitation: you’re limited to a maximum of 15 USB ports, including the internal ones sitting on your motherboard for Bluetooth connectivity, etc. To make matters worse, if you have a USB 3.0/3.1 port that’s backwards compatible with USB 2.0 connectors, to the OS, that one physical port counts as two ports — one for 3.0/3.1, one for 2.0. So even if your motherboard has exactly 15 physical USB ports, if even one of them is USB 3.0, you’re likely above the limit.
A second problem is, when you install macOS on a motherboard whose firmware isn’t specifically written for supporting macOS, it gets the placement of your USB ports wrong. So your super high-speed USB 3.0 port may not even recognise a USB 3.0 device plugged into it. This may also cause issues with your Hackintosh facing weird sleep/wake issues, among others.
This is where the USBInjectAll kext* comes in. If you’ve got it enabled, it’ll force macOS to “see” all the USB ports it possibly can, including ones that don’t physically exist on your motherboard. This isn’t a solution to get all your ports working, though — this shoots you well beyond the 15 port limit (you’ll likely see around 30 ports, instead), and will more often than not cause more problems than it fixes. This brings us to the custom SSDT — this file is what “talks” to UsbInjectAll, telling it which ports to inject and which ones to not bother injecting. Once you setup your SSDT file properly, you’ll have eliminated all the ports that don’t actually exist, or that you don’t intend to use, to bring the total number of ports down to 15, or lower. After this, macOS will communicate with your motherboard’s USB ports perfectly, the way you’d want it to.
*Some motherboards, such as mine, will require UsbInjectAll.kext to be accompanied by the XHCI-unsupported.kext for it to work properly.
Here’s another super handy Corp Newt Python script to very quickly map your USB ports. If you want a clearer understanding of what USB mapping is all about, I recommend this guide for newbies, and this one for people who want an even deeper dive into the subject.
Corp Newt’s script actually provides you with an alternative — once you’ve mapped your USB ports, you can either generate your custom SSDT file and place it in your ACPI folder the way I have, or you can generate an all-new kext called USBMap that will replace both the USBInjectAll kext and your SSDT file (you’ll still need XHCI-unsupported, though). USBMap is the more recommended method, as USBInjectAll isn’t maintained all that frequently, and could stop working properly after a macOS update.
Once you set up USBMap.kext (or your custom SSDT), you’ll never need to do it again for your motherboard, so be patient, set it up, and then forget about it.
And that’s it!You should have yourself a Hackintosh that just works. If you don’t, there’s a detailed post-install section in Mykola’s guide that should see you through common problems that occur once everything is up and running. If it doesn’t, you’re always welcome to share your troubles with us at the Discord channel, or in the subreddit. Just make sure that what you’re facing is a Hackintosh-related issue, rather than a macOS bug that’s all Apple’s fault. Enjoy!
Credits:I really can’t thank enough all the people who patiently sat down and helped me through my various rookie mistakes and anxieties. There are certainly more names — forgive my terrible retention — but among others, u/dracoflar, u/CorpNewt, and u/fewtarius have been invaluable in teaching me how to approach the entire process and in answering all the questions I had about the same. Thanks a billion, y’all.
March 07, 2017submitted by CuteBananaMuffin to conspiracy [link] [comments]
from Wikileaks Website
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,
...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,
...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.
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.
AnalysisCIA 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
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
"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.
ExamplesThe 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 exfiltrationAnother 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".
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,
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,
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.
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.
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.
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.
"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.
pip3 install -r requirements.txt python3 bip39\_gui.py
Geschrieben von admin am 23. November 2016 Gold hat traditionell als ein sicherer Hafen für Investoren gedient, wann immer die Wirtschaft ze... NOTE: If you have any questions or problems, read our Troubleshooting topic & Frequently Asked Questions topic. If you still haven't found a solution, post your issue down below and we'll do our best to help! If the hack does work for you, post your feedback below and help out other fellow members that are encountering issues. Credits: - @DanYal Geschrieben von admin am 23. November 2016 Gold hat traditionell als ein sicherer Hafen für Investoren gedient, wann immer die Wirtschaft z... The Simpsons Tapped Out Hack tool Unlimited Coins Money Cash, XP, Donuts, Tickets http: If you want to get a lot of donus, XP, coins and other resources in this game, use the Simpsons Tapped Out Cheats for it! You can also do that if you pay with your own real money, but it is not worth it to pay for just … a game! In addition, we spoof the ... Ex-binary options salesman: Here’s how we fleece the clients After a few weeks in the industry, Joshua told his wife: ‘Even if it means we’re going to starve, I can’t do this job anymore’ The Simpsons Tapped Out Hack Apk Cheats Get Unlimited Donuts and Cash - Justgameshack. Posted by Hackers University. Enable free shopping and use the donuts to rebuild the Springfield City. No jailbreak or root required on your device for your Simpsons: In this game, fans can recreate and customize the Springfield town and play along with many of the beloved characters from the show. The ... May 24, 2019 - Explore macramirez16's board "hack deutsch" on Pinterest. See more ideas about Tool hacks, Game cheats, Gaming tips. This had a version of the debug WIN386 but Windows tapped out saying it couldn’t load VMM and VMD when I tried it. A quick look at the dates made it clear that this WIN386.EXE was for Windows 3 ... The Simpsons™: Tapped Out v4.46.0 +3 Cheats Zahir posted a topic in Free Jailbroken Cydia Cheats , October 3, 2018 Modded/Hacked App: The Simpsons™: Tapped Out By Electronic Arts The following are some features/characteristics one should look out for in a Binary Options trading platform: • Luckily, Most trading platforms these day, do not need to install extra software on your computer, which is good. Flexibility is important, and trading on mobile devices,mini browsers are becoming more and more popular these days.Further more; security is also important, we must ...
[index]          
Have you ever been tempted to join binary options? Ever had a bad experience with binary options Recovery? Have you ever been scammed? How do you recover fro... The Simpsons Tapped Out Hack Unlimited Donuts/Cash [No Root/No Jailbreak] [WORKING] Download #1 - http://viid.me/qfQZos Thanks for downloading my app! Plea... Make 10 usd Every 50 Seconds Trading Binary Options 100% WINS - Profitable 2018 Trading strategies - Duration: 5:58. Proudly Tech Money General Tips And Tricks 55,253 views 5:58 Find out why Close. Watch Me Make $688 Live With Binary Options Hack KingHuman. Loading... Unsubscribe from KingHuman? Cancel Unsubscribe. Working... Subscribe Subscribed Unsubscribe 133K. Loading ... Binary Options Robot and Binary Hedge Fund lead the auto trading revolution that is sweeping the binary options world. Both enable 100% freedom with their auto trading process that runs from the ... Hello friends today i will show our secret software thats one software which you earn money from iq option binary trading its 100% profitable if you want or ... Find out why Close. #Binary #Option # ... binary option hack binary option haram binary option hindi binary option hedging binary option halal binary option hedging strategy binary option how to ... Best Binary Options Brokers for this Strategy: 1. 💲💹IQ Option FREE DEMO: http://www.cryptobinarylivingway.com/IQOption1 2. 💲💹Pocket Option FREE DEMO: http Find out why Close. How To Hack Binary Options and make $647 a Day KingHuman. Loading... Unsubscribe from KingHuman? Cancel Unsubscribe. Working... Subscribe Subscribed Unsubscribe 133K. Loading ... Binary options trading binary options strategy consists of considerable danger. Certainly, how to trade binary options you are doing need to register if you want to open a binary options account ...