.@lavados, @lunkw1ll, and I gave a talk with the title "Rowhammer in the Wild - Large-Scale Insights from FlippyRAM" at the 39th Chaos Communication Congress (#39c3). In our #FlippyRAM study, we investigated the prevalence of the #Rowhammer effect. If you are interested, the video is already online: https://media.ccc.de/v/39c3-rowhammer-in-the-wild-large-scale-insights-from-flippyr-am
Rowhammer in the Wild: Large-Scale Insights from FlippyR.AM

media.ccc.de

Oh, my toots have been part of 39c3's #FlippyRAM talk "Rowhammer in the Wild: Large-Scale Insights from FlippyR.AM" (https://media.ccc.de/v/39c3-rowhammer-in-the-wild-large-scale-insights-from-flippyr-am). As there were only two batches, I must have done it wrong or I had a bad USB thumb drive. 🤡

https://chaos.social/@maehw/113743443034869984

If you are interested in the results of our #flippyram #rowhammer study, which we presented last year at #38c3, we (@lavados, @lunkw1ll and me) will be presenting our findings in Room One at 23:00 at #39c3.

I recently tried https://flippyr.am/. This is a #Linux live system for a USB flash drive. It tests bit flips in RAM (#Rowhammer).

Which is only in the disclaimer of the live system:

1. The computer can be damaged when running it.

2. The test takes at least 3 hours, 8 hours would be better.

Unfortunately, there was no clear result file after 3 hours. There was nothing in the log files either. A bit frustrating.

#FlippyRAM #vulnerability #infosec

FLIPPYR.AM

Was halt so in der Gürteltasche rumliegt. #38C3 #FlippyRAM

just stuck in a random usb stick i got from a security conference, and it didn't boot. i guess lack of support from UEFI saved my ass again?

#FlippyRAM

My #FlippyRAM USB pen drive which was handed out during the Rowhammer talk at #38C3 has Vendor ID 0x346d=13421d and Product ID 0x5678. If https://usb.org/sites/default/files/vendor_ids051920_0.pdf is the most recent account then this doesn't look like an officially registered VID. My Linux displays a "USB Disk 2.0". It actually enumerates as "Mass Storage" device. PID of 0x5678 also really reads like a dummy value though 0x38c3 would have been even nicer. Probably really just some cheap-o pen drives from $somewhere?
USB Sticks auf einer Securitykonferenz austeilen. Because why not? #38C3 #FlippyRAM (ISO gibts auch auf flippyr.am)