What are some cool things to do with a Raspberry Pi / single board computer / lightweight Linux machine?
I compiled and installed a hardware accelerated version of MPV which I can use to watch and stream video. It's really good, runs incredibly smoothly and CPU usage is very low (I guess because it's using the GPU probably...).
- Use it as a cheap baremetal server for tor hidden services.
- install it in some kind of protected network, punch a hole into the firewall by making ssh accessible via hidden service, hack the network, extract informations, leak them. Something like this would be a nice thing to be done in a police station, or a news media concern.
- use it for all kinds of robotics, or as a programming device for chips.
- use it as a surveillance device to protect your home
- lots of other stuff.
is a great site with homebuilt retrocomputers, but it seems to be "sleeping" at the moment, whatever that means. You can probably find it on archive.org through the Wayback Machine if you use js, but I don't, so I can't look it up for you.
>>7823 >>7874 >ARM TrustZone
ARM TrustZone is not botnet, you are just retarded and do not understand how it works. It's like complaining that having different rings is botnet. Just because the different rings exist, it does not mean you can not just run everything in ring 0.
>>7877 >using software developed by literal Israeli jews from tel aviv isn't botnet, goy
>just (((trust))) us goy!
jew niggers need to all be gassed. every last one.
I use mine as a chip programmer. I bought an official xilinx programmer for a cpld chip, but I couldn't get it to work. The raspberry pi worked like a dream.
>>7886 >xilinx
i bought a xiling fpga dev kit and from my experience i can say they are the most kikey company, even worse than kiketel. the way that they use to get the verilog into the fpga was proprietary and you had to (((pay money))) for proprietary kike software to do it for you. and guess what, that software only ran on windows 8 or higher.
fuck xilinx. it's botnet af.
not that raspberry pi is any better. arm processors have (((trustzone))) backdoors, and the rpi foundation itself is full of sjw's and trannys.
>>7887 Unfortunately, pretty much all FPGA manufactures have their own proprietary IDE. Thankfully, symbiflow is providing a free software toolchain.
Again, TrustZone is not a backdoor. TrustZone is not a separate microprocessor like Intel's ME. With TrustZone when the chip starts you start in trusted mode. If you are just using a raspberry pi normally you world always remain in the trusted mode. TrustZone would pretty much be an unused feature to you.
>>7888 >you start in trusted mode
You mean the kikes over at tel aviv can trust that the chip is beaming all data directly to israeli HQ? Nice try kike.
Maybe try telling me how to get out of (((trusted mode))) first.
>>7877 >>7888 >ARM TrustZone is not botnet, you are just retarded and do not understand how it works. It's like complaining that having different rings is botnet.
ARM TrustZone is not for you, goy. you, user, don't have any control over it.
trustzone is for jews, so they can put DRM, backdoors, malware, spyware there and your normal software and OS cannot see, control, kill it
Why are you using an RPI you fucking Raspberry?
RPIs ARE FUCKING BOTNET!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
WE ARE FUCKING BETTER THAN THIS JESUS FUCKING CHRIST
USE REAL HARDWARE THAT ISN'T FUCKING BOTNET FOR FUCK FUCKING FUCKER SNAKES!!!!!!!!!!!!!!!!!!!!!!!!!!
Like someone mentioned, the Beagleboner ( ͡° ͜ʖ ͡°) achieves this.
Aktually, it sort of is. The TrustZone is used to prevent userspace programs from accessing certain CPU functionality if they're not using the special "burned in" key. This would allow only authorized programs to perform certain actions, like updating the firmware. It's more analogous to TPM, than IME. Although the architectural enclaves are similar to how IME keeps hackers from seeing what it's doing. This would be advantageous for implementing DRM because the client hardware can be remotely attested.
It would be one thing if you, as the user, could add the keys into the TEE, trusted execution environment, but here the key is burned in by the manufacturer, using on-chip fuses.
<Though deprivation of ownership is not an inherent property of TEEs (it is possible to design the system in a way that allows only the user who has obtained ownership of the device first to control the system), in practice all such systems in consumer electronics are intentionally designed so as to allow chip manufacturers to control access to attestation and its algorithms. It allows manufacturers to grant access to TEEs only to software developers who have a (usually commercial) business agreement with the manufacturer, and to enable such use cases as tivoization and DRM.
>>9995 Can you backup your claims on what TrustZone is doing. From my understanding TrustZone does nothing of the sort. TrustZone simply creates a trusted and untrusted world. What you are referring to would be built by a developer of a product and not by the manufacturer of the CPU itself.
>>9995 >Aktually, it sort of is.
The post you're responding to links to open source code you, the user/owner of the device, can run in the "secure" world of trustzone on raspberry pi 3.
>The TrustZone is used to prevent userspace programs from accessing certain CPU functionality if they're not using the special "burned in" key.
This is also wrong, trustzone is orthogonal to userspace vs kernel space.
Frankly I don't know how you could write this post if you actually read the post you're responding to.
>> 10008
> trustzone is orthogonal
Except it's not. Read datasheet specs, not some retard's wiki article.
Trustzone switches cpu execution states from 'guest' mode to 'privileged' mode. Yes, it allows some specific ops to be executed (like cool floating point ops or rsa-like ops), it allows to read protected memory regions, it allows to write in protected memory and basically low-level access peripherals. Every time you cpu sends tcp/ip packet most likely it does so in privileged mode. And final yes: this hard-coded key which can not be ever changed (since it is burn in non-writable memory) is always the same. Source: my experience working with ARM devices.
>>10034 When the processor starts, you already are in the trusted world. If you don't use TrustZone's features, then you will not even notice it's there.
>>10045 That blog post is talking about trusted execution environments built on top of TrustZone. To bring this back on topic, the Raspberry Pi boots up in the secure world, there is no TEE.
>>10047 >That blog post is talking about trusted execution environments built on top of TrustZone. To bring this back on topic, the Raspberry Pi boots up in the secure world, there is no TEE.
The assertion was that users can only run code in the normal world and the secure world is a mossad backdoor or some shit. >>9968
>>10034 Reading the "datasheet specs" didn't do you much good if you think TrustZone prevents "userspace programs from accessing certain CPU functionality". Stop larping, kid.
>flashing custom BIOS
coreboot and libreboot
>pi2scart
because adding a computer to an olt CRT-TV is fun
>hosting something a raspberry pi can handle
a IRC server for example
I just use mine as an alternative to x86, since I refuse to spend money on x86 ever again. So far I have two boards (A20 and A64 SoC) that run the regular Linux and BSD stuff. They do everything I need.
>>10058 Don't think that person was saying that. Was likely pointing to the must go through the privileged area of secure world to access certain hardware features as shown in the graphic.
Unsecure world, userspace applications can communicate with the secure world, TEE, but only if it has the correct key/signature.
IF I'm reading it right, that person probably means guest="normal world" and privileged="secure world"
I compiled and installed a hardware accelerated version of MPV which I can use to watch and stream video. It's really good, runs incredibly smoothly and CPU usage is very low (I guess because it's using the GPU probably...).
What else can you do with something like this?