/explore
|
You are here 
|
l-o-o-s-e-d.net | ||
| | | | |
tinypilotkvm.com
|
|
| | | | | Updates about my life and what I learn about creating software | |
| | | | |
irq5.io
|
|
| | | | | In case you haven't heard, the Raspberry Pi Zero is the smallest, most low-cost device in the Raspberry Pi family, but it's also the hardest to find. It has two Micro-B USB ports, one for power and another functions as a dual-role USB OTG port. One of the more interesting uses for the Raspberry Pi... | |
| | | | |
koscis.wordpress.com
|
|
| | | | | Today we will make our RPi a slave device connected to PC via USB. And this RPi will be detected as the keyboard. We need Raspberry Pi Zero or Zero W with the micro USB connector. Configuration First, we have to enable ConfigFS for USB gadgets: echo "dtoverlay=dwc2" | sudo tee -a /boot/config.txt echo "dwc2"... | |
| | | | |
nv1t.github.io
|
|
| | | Close to a year ago, I stumbled upon the Kekz Headphones, which seemed like an interesting approach on the whole digital audio device space. They claimed to work without any internet connection and all of the content already on the headphones itself. They are On-Ear Headphones, which work by placing a small chip (I call them "Kekz" or "Cookie") into a little nook on the side and it plays an audio story. I was intrigued, because there were some speculations going around, how they operate with those "Kekz"-Chips. I invite you to join me on a journey into the inner workings of those headphones. We will talk about accessing the encrypted files on the device, breaking the crypto and discovering disclosure of data from customers. | ||
