Slashdot Mirror

Most things can be explained very simply

"For every complex problem there is a simple solution that is wrong."

If you can handle the technical side:

• The original whitepaper that started it
• Mastering Bitcoin
• Bitcoin Source Code

That's all you need.



To address your other points:

Sidechains are divorced from the block so require other layers of trust and are therefore not blockchain.

You're absolutely right. Blockchain was only one of the inventions in the whitepaper. The system doesn't work with it alone. And if you can replace the buzzword "blockchain" with "database" in an application, it's not interesting and adds little to no value.

51% attack is completely possible, in 2 cases especially. ...

Right again. Bitcoin may not be what fintech applications are written on in ten years. But it will be a cryptocurrency that is trust-less, fungible, censorship resistant, immutable, peer to peer, and open. Bitcoin introduced decentralized security through computation that can operate in highly hostile environments. It is currently the most "anti-fragile" cryptocurrency because of size, but another may take its place.

Only 3 of the top 4 pools need to conspire to further their own self interest

This attack has been tried and will be tried again. It's a long story, but the current result is a fork called "Bitcoin Cash". So far it hasn't gained the same traction as the original "Bitcoin".

even if they are able to disrupt the network for their own purposes with 30% of the hash rate

Has most likely been tried very recently. Many suspect that spam transactions that drove transaction rates up for many weeks were exactly this. Transaction rates are lower again. These attacks are very expensive to continue. They require an immense amount of electricity.

Maybe there is a simply a spam attack possible that delays all transactions for many hours or days.

same as above

Maybe there is a trust attack where proof appears from multiple sources.

You mean a Sybil attack. Currently highly unlikely based on how the code works. Read through the source code.

When does a classic man in the middle attack become 'worth it', impersonate the work originator.

If you're talking about the network, it doesn't. With the amount of electrical power required, it's always much more profitable to simply mine bitcoin.

If you're talking about individuals, many are doing this right now and draining people's wallets. It's one user at a time. It does not affect the whole network. Crypto allows the user to be their own bank. This carries significant risks at the moment. I wouldn't recommend it to the masses yet.

if its not regulated out of use by governments in short order anyways

Some governments can make it go underground (like in Venezuela). But it's impossible to stop (like in Venezuela). Unless you destroy every computer on the planet that runs a full bitcoin wallet.


I encourage you to be skeptical. Be highly skeptical. If you dig into it, you'll see that your ideas on compromising this system are not new. You'll find a multitude of other attacks that have been accounted for as well. Bitcoin has been under attack since day 1.

Andreas also put his Mastering Bitcoin book on GitHub for free.

Jesus, how did I manage to fuck up the links so badly. Link, link, link. And some bonus stuff.

Jesus, how did I manage to fuck up the links so badly. Link, link, link. And some bonus stuff.

Jesus, how did I manage to fuck up the links so badly. Link, link, link. And some bonus stuff.

Jesus, how did I manage to fuck up the links so badly. Link, link, link. And some bonus stuff.

There seems to be no requirement to open the console, or even solder, and the picture shows what seems to be a board with an FTDI chip, and 2 wires going to the console. Is it just a UART, and are they getting into the bootloader that way ?

Well, the joy con controllers have two ways to communicate to the switch console, wirelessly using a modified form of bluetooth, or wired by sliding them onto the sides of the console, where they use a high speed serial link via UART.

It's quite hard to see the connector on the things, but along the rail at the very bottom, where on the plastic it has some downward pointing arrows. Directly behind those arrows is the connector.

The switch starts out handshaking with a 1mbit/sec serial link using that. This lets the joycon identify itself and kick up the baud rate to 3.2mbit/sec to start blasting input date to the console.

This is a 10 pin connector, but the serial part uses the same number of wires as expected for bi-directional hardware flow control.
There is also a single "sense pin" that the console tells the joycon to not use wireless with.
The rest are power/ground.

As the sense line appears to just be a low/high signal, I'd guess they are just using the RX serial pin (receive from the POV of the console that is)

People have been working on reverse engineering the joy con protocol and enough of the handshaking to get to that point. This info should be easy to google for.

Going by the image on NintendoLife, if you'll note those various small flex cables barely in view, comparing this to teardown images of the joycons, I am guessing the bulk of the thing snapped on the side of their switch is a real joy con rail and board.

https://github.com/dekuNukem/Nintendo_Switch_Reverse_Engineering
If you scroll down to the header text "Joy-Con to Console Communication" you'll see two pictures.
A joycon case and rail with the PCB removed, and below just the rail itself.

The NintendoLife image seems to be one of those rails, with the flex ribbon cable wrapped downwards and I assume out of frame or possibly under the console.
They are likely taping into the solder points that connect the flex cable to the connector.

As to what the switch is doing using those ports in the boot rom, and what they ended up having to do over that serial link to exploit it, I have no idea beyond "what kind of sorcery is this?!"

At least some good news is those solder pads are still of a size that can be soldered to by hand.
The tiny pitch of the connector pins would be a bitch to work with. I think the tip of my standard soldering iron is about the width of two or maybe three of those pins!

I wonder how much of the code is different from https://github.com/PureDarwin/

How many of Slashdot's editors are women?

Although information about the editors here is limited, from what I can tell the number is probably close to zero, if it isn't actually zero.

It reminds me of the Rust programming language's community. That community is predominantly made up of effeminate white males in their 20s, yet they still feel the need to brag about how "diverse" their extremely homogeneous community supposedly is, and they lecture everybody else about how important "tolerance" and "inclusion" are.

I really don't care one way or the other about the gossipy minutia and the personal lives of the Rust community. I care about whether Rust is a useful and cost-effective solution to a progamming problem.

Do you really care about this sort of trivia? If so, you are extremely small-minded, making you the apparent target audience. Do you read tabloids to learn about celebrity divorces, too? Effeminate males are used for PR points because they're non-threatening and are unlikely to rock the boat. But that would be ... ... PR. It has no place in an objective evaluation of a logic-based system such as a programming language. If it's a good programming language that neatly meets my needs, I really don't care if the other users are a third gender who have purple skin with green polka-dots. If it does not meet my needs, it's time to move on to something that might.

How many of Slashdot's editors are women?

Although information about the editors here is limited, from what I can tell the number is probably close to zero, if it isn't actually zero.

It reminds me of the Rust programming language's community. That community is predominantly made up of effeminate white males in their 20s, yet they still feel the need to brag about how "diverse" their extremely homogeneous community supposedly is, and they lecture everybody else about how important "tolerance" and "inclusion" are.

https://github.com/rust-lang/rust/pull/25640

https://github.com/rust-lang-deprecated/rust-buildbot/issues/2

https://github.com/rust-lang/rust/pull/25640

https://github.com/rust-lang-deprecated/rust-buildbot/issues/2

Spectre is harder to exploit you're correct. Meltdown however is way more dangerous and not hard at all to implement. Heres some PoC links for you to look through.
https://github.com/paboldin/me...
https://github.com/gkaindl/mel...
https://github.com/IAIK/meltdo...
https://github.com/RealJTG/Mel...

That was from a 5 second google search. I have only tested the top one myself but I know it works.

Spectre is harder to exploit you're correct. Meltdown however is way more dangerous and not hard at all to implement. Heres some PoC links for you to look through.
https://github.com/paboldin/me...
https://github.com/gkaindl/mel...
https://github.com/IAIK/meltdo...
https://github.com/RealJTG/Mel...

That was from a 5 second google search. I have only tested the top one myself but I know it works.

Spectre is harder to exploit you're correct. Meltdown however is way more dangerous and not hard at all to implement. Heres some PoC links for you to look through.
https://github.com/paboldin/me...
https://github.com/gkaindl/mel...
https://github.com/IAIK/meltdo...
https://github.com/RealJTG/Mel...

That was from a 5 second google search. I have only tested the top one myself but I know it works.

Spectre is harder to exploit you're correct. Meltdown however is way more dangerous and not hard at all to implement. Heres some PoC links for you to look through.
https://github.com/paboldin/me...
https://github.com/gkaindl/mel...
https://github.com/IAIK/meltdo...
https://github.com/RealJTG/Mel...

That was from a 5 second google search. I have only tested the top one myself but I know it works.

There is. It's called RON.

He is terrified of other language because, being a Social Justice Warrior, his group finds the terms "master" and "slave" to be "problematic."

No, I'm not kidding, though I wish I were.

When a language is gleefully throwing away well understood, well used terms because of someone's misguided feelings, then quite frankly I wonder what other decisions - truly important ones - have been impacted by the same toxic SJW attitude.

We're working on decentralizing the internet too. We're a startup that was founded in Norway who have gotten an international team of highly experienced Tech personalities who also agree that this is the future. This is also partly what's behind the Blockchain movement. We've made an open source operating system that we're inserting into the internet. Autonomous infrastructure that allows for building desktop and mobile apps on decentralized technology. Check out the Friend Unifying Platform. https://friendup.cloud/ [friendup.cloud] - https://github.com/FriendUPClo... [github.com]

Not to forget our highly nerdy team of programmers that will help give JavaScript an even bigger push by allowing JS deveopers to built whole apps within a desktop just using JavaScript, including file management, window management, user management.. all you need, open sourced, install on your own hardware or run somewhere else. Client side encryption and DOS drivers to allow integration of arbitrary datasources included. disclaimer: I am part of that team :)

I think you just defeated your own argument.

Try Linux Deploy (or if you don't trust Google, go to the github.) You do have the problem of having to connect to it via VNC still AFAIK, since last I looked all the Android X servers were garbage. But if you know one that works, I'm interested.

We're working on decentralizing the internet too. We're a startup that was founded in Norway who have gotten an international team of highly experienced Tech personalities who also agree that this is the future. This is also partly what's behind the Blockchain movement. We've made an open source operating system that we're inserting into the internet. Autonomous infrastructure that allows for building desktop and mobile apps on decentralized technology. Check out the Friend Unifying Platform. https://friendup.cloud/ - https://github.com/FriendUPClo...

All of .NET is open source.

Numerous languages are open. Even the compiler is open source.

You also have vscode, the Edge JavaScript runtime and so many other things I'm just going to put this link here.

In short, you are living under a rock.

All of .NET is open source.

Numerous languages are open. Even the compiler is open source.

You also have vscode, the Edge JavaScript runtime and so many other things I'm just going to put this link here.

In short, you are living under a rock.

All of .NET is open source.

Numerous languages are open. Even the compiler is open source.

You also have vscode, the Edge JavaScript runtime and so many other things I'm just going to put this link here.

In short, you are living under a rock.

All of .NET is open source.

Numerous languages are open. Even the compiler is open source.

You also have vscode, the Edge JavaScript runtime and so many other things I'm just going to put this link here.

In short, you are living under a rock.

All of .NET is open source.

Numerous languages are open. Even the compiler is open source.

You also have vscode, the Edge JavaScript runtime and so many other things I'm just going to put this link here.

In short, you are living under a rock.

All of .NET is open source.

Numerous languages are open. Even the compiler is open source.

You also have vscode, the Edge JavaScript runtime and so many other things I'm just going to put this link here.

In short, you are living under a rock.

All of .NET is open source.

Numerous languages are open. Even the compiler is open source.

You also have vscode, the Edge JavaScript runtime and so many other things I'm just going to put this link here.

In short, you are living under a rock.

minimap2 works better for long reads, and can be used in the Canu assembler as the overlapper component for doing read correction.

Why not? The necessary hooks seem to be all there. Untrusted X Clients are isolated against trusted X Clients. This seems to work.

Who told you this nonsense? X.org doesn't have any real distinction between clients. They are all similarly "trusted".

There's a thin veneer of SECURITY and XAce extensions which are not used by anybody. They are not even build-enabled in Debian and CentOS. They are also utterly inadequate, for example, SECURITY extension puts all "untrusted" clients together as there's no per-client isolation and doesn't prevent all sniffing.

Yes, that could easily be changed by also separating untrusted clients from each other. I once had a proof of concept patch doing exactly that and it was very simple... It wasn't too useful as untrusted clients also can't use render and other important extensions. This also seems easily changed.

A wayland shell would also be shared by its clients, or? With the security hooks already there, why is there are need for re-architecting?

Wayland clients don't have access to each other without shell explicitly granting capabilities to do it. They _might_ have access to the shell but it's easy to isolate. For example, a browser application can be limited only to submitting requests for direct rendering manager and to reading its input stream.

Ok, so it starts from the other direction. So what? It isn't clear to me why - once all desired features and extensions have been added - the end result would be any better than what could be achieved by using isolated untrusted clients on X.

I don't mind splitting up X or re-architecting parts of it (although I do not quite see why you think it is needed - we also have a monolithic kernel). The main problem I have with Wayland is that it breaks compatibility with the wire-protocol without a good reason.

Run XWayland for perfect backwards compat. Problem solved.

So we now have to maintain both X and Wayland. Wow, Genius!

Well, if they can interact, then isolation is difficult and somehow I doubt they have solved this completely, and if they can not really interact, they are useless....

Solved: https://github.com/snapcore/sn...

"Since many of the underlying technologies in these environments were not designed with strong application isolation in mind, users should only install applications using these interfaces from trusted sources." Solved?

NetBoot is on the deprecation list. Apple suggest NetSUS or BSDPy.

NetBoot is on the deprecation list. Apple suggest NetSUS or BSDPy.

https://github.com/M66B/XPriva...

Should be standard

Yup, I've been experimenting with streaming vpx/opus and it's quite simple and should just work with any modern browser. You can do surprising bit of stuff with the video with Javascript, as well. That alone is going to be pretty compelling for any business that wants to do anything with video, even before you factor in not getting sued for trying to use the format for anything without a license.

uBlock Origin silently poll data in background from raw.githubusercontents.com. Some people asked the dev to fix "phoning home" but was rejected. Use AdblockPlus [mozilla.org] instead. ABP connect to only filter servers(easylist.to).

I use Ublock Origin and this bothered me so I did some searching. Apparently this is the other side of the story, at this link where Ublock is hosted. I think he makes some good points here. Ublock is open source and has no home server to "phone home" to. He claimst he periodic connections are to update filter lists, which is quite plausible.

Do you have any evidence that Ublock's background connections are anything else? Do you have logs or packet captures showing malice? As it stands now I want to believe it's a good extension (it's good at blocking ads anyway). I'm honestly more inclined to believe the authors of an open-source project over a random AC but if you have evidence I'm willing to listen.

I'd recommend Kodi with the PsuedoTV Live plugin, which lets you set up channels from your library with various rule sets to determine what is shown and when.

Exactly what I thought of as reading. PsuedoTVLive is pretty much exactly what he is describing.

I'll just recommend an OpenELEC box (I prefer on ODROID C2) for the KODI platform.

I'd recommend Kodi with the PsuedoTV Live plugin, which lets you set up channels from your library with various rule sets to determine what is shown and when.

You've linked to two separate projects. Here's a better link.

Why not? The necessary hooks seem to be all there. Untrusted X Clients are isolated against trusted X Clients. This seems to work.

Who told you this nonsense? X.org doesn't have any real distinction between clients. They are all similarly "trusted".

There's a thin veneer of SECURITY and XAce extensions which are not used by anybody. They are not even build-enabled in Debian and CentOS. They are also utterly inadequate, for example, SECURITY extension puts all "untrusted" clients together as there's no per-client isolation and doesn't prevent all sniffing.

A wayland shell would also be shared by its clients, or? With the security hooks already there, why is there are need for re-architecting?

Wayland clients don't have access to each other without shell explicitly granting capabilities to do it. They _might_ have access to the shell but it's easy to isolate. For example, a browser application can be limited only to submitting requests for direct rendering manager and to reading its input stream.

I don't mind splitting up X or re-architecting parts of it (although I do not quite see why you think it is needed - we also have a monolithic kernel). The main problem I have with Wayland is that it breaks compatibility with the wire-protocol without a good reason.

Run XWayland for perfect backwards compat. Problem solved.

Well, if they can interact, then isolation is difficult and somehow I doubt they have solved this completely, and if they can not really interact, they are useless....

Solved: https://github.com/snapcore/sn...

An arstechnica commenter mentioned NoCoin which is a standalone extension.
https://arstechnica.com/inform...

https://github.com/keraf/NoCoi...

You can also take the URL they curate and then import it into your adblocker of choice.

https://raw.githubusercontent....

Even the CLI of linux isn't all that great IMO.

I can already tell this is going to be a great list of well-reasoned complaints and not just a description of default behaviors that work well for most people but can be changed if desired.

You don't get rolodex autocomplete (where you can cycle through the suggestions by pressing tab)

This is determined by your shell. Personally, I hate this kind of autocomplete. If that's your thing, you might want to look into zsh (and might I suggest Oh My Zsh as well).

autocomplete doesn't automatically fill in quotes for you for filenames with spaces

That's because it doesn't need to. At least in bash, which I assume is the shell you're using, it escapes characters that need to be escaped, so if a filename contains spaces they will be filled in preceded by a backslash.

"clear" just prints some blank lines instead of actually clearing the screen, apparently thinking it is outputting to an old terminal without scroll features

clear does actually clear your screen, unless you're using an old terminal without scroll features. From man clear:

clear clears your screen if this is possible, including its scrollback
buffer (if the extended "E3" capability is defined). clear looks in
the environment for the terminal type and then in the terminfo database
to determine how to clear the screen.

In my terminal, clear clears my screen and resets my cursor to the top line, just like a newly-opened window would look.

And then there is lack of support for line-drawing characters everywhere.

[citation needed]. I haven't run into support issues with line-drawing characters in years.

Change log:
2018/01/01 - Added 14 Useful Links. Disable Intel ME 11 via undocumented NSA "High Assurance Platform" mode with me_cleaner, Blackhat Dec 2017 Intel ME presentation, Intel ME CVEs (CVSS Scored 7.2-10.0)

Intel CPU Backdoor Report
The goal of this report is to make the existence of Intel CPU backdoors a common knowledge and provide information on backdoor removal.

What we know about Intel CPU backdoors so far:

TL;DR version

Your Intel CPU and Chipset is running a backdoor as we speak.

The backdoor hardware is inside the CPU/Bridge and the backdoor firmware (Intel Management Engine) is in the chipset flash memory.

30C3 Intel ME live hack:
[Video] 30C3: Persistent, Stealthy, Remote-controlled Dedicated Hardware Malware
@21:43, keystrokes leaked from Intel ME above the OS, wireshark failed to detect packets.

[Quotes] Vortrag:
"the ME provides a perfect environment for undetectable sensitive data leakage on behalf of the attacker".

"We can permanently monitor the keyboard buffer on both operating system targets."

Decoding Intel backdoors:
The situation is out of control and the Libreboot/Coreboot community is looking for BIOS/Firmware experts to help with the Intel ME decoding effort.

If you are skilled in these areas, download Intel ME firmwares from this collection and have a go at them, beware Intel is using a lot of counter measures to prevent their backdoors from being decoded (explained below).

Backdoor removal:
The backdoor firmware can be removed by following this guide using the me_cleaner script.
Removal requires a Raspberry Pi (with GPIO pins) and a SOIC clip.

2017 Dec Update:
Intel ME on recent CPUs may be disabled by enabling the undocumented NSA HAP mode, use me_cleaner with -S option to set the HAP bit, see me_cleaner: HAP AltMeDisable bit.

Useful links (Added 2018 Jan 1):
Disabling Intel ME 11 via undocumented HAP mode (NSA High Assurance Platform mode)
me_cleaner: Set HAP AltMeDisable bit with -S option
Blackhat 2017: How To Hack A Turned Off Computer Or Running Unsigned Code In Intel Management Engine
EFF: Intel's Management Engine is a security hazard, and users need a way to disable it
Sakaki's EFI Install Guide/Disabling the Intel Management Engine
Intel ME bug storm: Hardware vendors race to identify and provide updates for dangerous Intel flaws.
CVE-2017-5689: An unprivileged network attacker could ga

Change log:
2018/01/01 - Added 14 Useful Links. Disable Intel ME 11 via undocumented NSA "High Assurance Platform" mode with me_cleaner, Blackhat Dec 2017 Intel ME presentation, Intel ME CVEs (CVSS Scored 7.2-10.0)

Intel CPU Backdoor Report
The goal of this report is to make the existence of Intel CPU backdoors a common knowledge and provide information on backdoor removal.

What we know about Intel CPU backdoors so far:

TL;DR version

Your Intel CPU and Chipset is running a backdoor as we speak.

The backdoor hardware is inside the CPU/Bridge and the backdoor firmware (Intel Management Engine) is in the chipset flash memory.

30C3 Intel ME live hack:
[Video] 30C3: Persistent, Stealthy, Remote-controlled Dedicated Hardware Malware
@21:43, keystrokes leaked from Intel ME above the OS, wireshark failed to detect packets.

[Quotes] Vortrag:
"the ME provides a perfect environment for undetectable sensitive data leakage on behalf of the attacker".

"We can permanently monitor the keyboard buffer on both operating system targets."

Decoding Intel backdoors:
The situation is out of control and the Libreboot/Coreboot community is looking for BIOS/Firmware experts to help with the Intel ME decoding effort.

If you are skilled in these areas, download Intel ME firmwares from this collection and have a go at them, beware Intel is using a lot of counter measures to prevent their backdoors from being decoded (explained below).

Backdoor removal:
The backdoor firmware can be removed by following this guide using the me_cleaner script.
Removal requires a Raspberry Pi (with GPIO pins) and a SOIC clip.

2017 Dec Update:
Intel ME on recent CPUs may be disabled by enabling the undocumented NSA HAP mode, use me_cleaner with -S option to set the HAP bit, see me_cleaner: HAP AltMeDisable bit.

Useful links (Added 2018 Jan 1):
Disabling Intel ME 11 via undocumented HAP mode (NSA High Assurance Platform mode)
me_cleaner: Set HAP AltMeDisable bit with -S option
Blackhat 2017: How To Hack A Turned Off Computer Or Running Unsigned Code In Intel Management Engine
EFF: Intel's Management Engine is a security hazard, and users need a way to disable it
Sakaki's EFI Install Guide/Disabling the Intel Management Engine
Intel ME bug storm: Hardware vendors race to identify and provide updates for dangerous Intel flaws.
CVE-2017-5689: An unprivileged network attacker could ga

Change log:
2018/01/01 - Added 14 Useful Links. Disable Intel ME 11 via undocumented NSA "High Assurance Platform" mode with me_cleaner, Blackhat Dec 2017 Intel ME presentation, Intel ME CVEs (CVSS Scored 7.2-10.0)

Intel CPU Backdoor Report
The goal of this report is to make the existence of Intel CPU backdoors a common knowledge and provide information on backdoor removal.

What we know about Intel CPU backdoors so far:

TL;DR version

Your Intel CPU and Chipset is running a backdoor as we speak.

The backdoor hardware is inside the CPU/Bridge and the backdoor firmware (Intel Management Engine) is in the chipset flash memory.

30C3 Intel ME live hack:
[Video] 30C3: Persistent, Stealthy, Remote-controlled Dedicated Hardware Malware
@21:43, keystrokes leaked from Intel ME above the OS, wireshark failed to detect packets.

[Quotes] Vortrag:
"the ME provides a perfect environment for undetectable sensitive data leakage on behalf of the attacker".

"We can permanently monitor the keyboard buffer on both operating system targets."

Decoding Intel backdoors:
The situation is out of control and the Libreboot/Coreboot community is looking for BIOS/Firmware experts to help with the Intel ME decoding effort.

If you are skilled in these areas, download Intel ME firmwares from this collection and have a go at them, beware Intel is using a lot of counter measures to prevent their backdoors from being decoded (explained below).

Backdoor removal:
The backdoor firmware can be removed by following this guide using the me_cleaner script.
Removal requires a Raspberry Pi (with GPIO pins) and a SOIC clip.

2017 Dec Update:
Intel ME on recent CPUs may be disabled by enabling the undocumented NSA HAP mode, use me_cleaner with -S option to set the HAP bit, see me_cleaner: HAP AltMeDisable bit.

Useful links (Added 2018 Jan 1):
Disabling Intel ME 11 via undocumented HAP mode (NSA High Assurance Platform mode)
me_cleaner: Set HAP AltMeDisable bit with -S option
Blackhat 2017: How To Hack A Turned Off Computer Or Running Unsigned Code In Intel Management Engine
EFF: Intel's Management Engine is a security hazard, and users need a way to disable it
Sakaki's EFI Install Guide/Disabling the Intel Management Engine
Intel ME bug storm: Hardware vendors race to identify and provide updates for dangerous Intel flaws.
CVE-2017-5689: An unprivileged network attacker could ga

Change log:
2018/01/01 - Added 14 Useful Links. Disable Intel ME 11 via undocumented NSA "High Assurance Platform" mode with me_cleaner, Blackhat Dec 2017 Intel ME presentation, Intel ME CVEs (CVSS Scored 7.2-10.0)

Intel CPU Backdoor Report
The goal of this report is to make the existence of Intel CPU backdoors a common knowledge and provide information on backdoor removal.

What we know about Intel CPU backdoors so far:

TL;DR version

Your Intel CPU and Chipset is running a backdoor as we speak.

The backdoor hardware is inside the CPU/Bridge and the backdoor firmware (Intel Management Engine) is in the chipset flash memory.

30C3 Intel ME live hack:
[Video] 30C3: Persistent, Stealthy, Remote-controlled Dedicated Hardware Malware
@21:43, keystrokes leaked from Intel ME above the OS, wireshark failed to detect packets.

[Quotes] Vortrag:
"the ME provides a perfect environment for undetectable sensitive data leakage on behalf of the attacker".

"We can permanently monitor the keyboard buffer on both operating system targets."

Decoding Intel backdoors:
The situation is out of control and the Libreboot/Coreboot community is looking for BIOS/Firmware experts to help with the Intel ME decoding effort.

If you are skilled in these areas, download Intel ME firmwares from this collection and have a go at them, beware Intel is using a lot of counter measures to prevent their backdoors from being decoded (explained below).

Backdoor removal:
The backdoor firmware can be removed by following this guide using the me_cleaner script.
Removal requires a Raspberry Pi (with GPIO pins) and a SOIC clip.

2017 Dec Update:
Intel ME on recent CPUs may be disabled by enabling the undocumented NSA HAP mode, use me_cleaner with -S option to set the HAP bit, see me_cleaner: HAP AltMeDisable bit.

Useful links (Added 2018 Jan 1):
Disabling Intel ME 11 via undocumented HAP mode (NSA High Assurance Platform mode)
me_cleaner: Set HAP AltMeDisable bit with -S option
Blackhat 2017: How To Hack A Turned Off Computer Or Running Unsigned Code In Intel Management Engine
EFF: Intel's Management Engine is a security hazard, and users need a way to disable it
Sakaki's EFI Install Guide/Disabling the Intel Management Engine
Intel ME bug storm: Hardware vendors race to identify and provide updates for dangerous Intel flaws.
CVE-2017-5689: An unprivileged network attacker could ga

Going full circle https://github.com/christophwi...

module.exports = function (data, force) {
;;var opts = {
;;;;preset: 'default',
;;;;indent: {
;;;;;;value: ';;',
;;;;;;ObjectExpression: force ? 1 : 0
;;;;}
;;}
;;return esformatter.format(data + '\n', opts)
}

The TSA demanded (and received) back-door master keys to your luggage for exactly the same reasons, for fighting them terrorists. Guess what? They leaked.

Also, Apple's signing keys are far less valuable, since you need a lot more than that to install software on their phones - and the signing mechanism has long been defeated by jailbreaking anyway. They have no master decryption keys. And there's zero actual evidence that Apple has given back-door access to user devices to China or anyone else, despite vaguely-worded reports about "security checks"; Apple continue to insist that not even Apple can do that.

Two extensions that I have used have not been ported. One was not ported because it depends on legacy APIs known to lack a counterpart in WebExtensions.

https://github.com/10se1ucgo/D...

https://github.com/10se1ucgo/D...