IAmLiterallyAB
Joined 8 years ago
Karma
567
Submissions
218
Member since
Mar 22
Recent submissions
Comment · 1 month ago
Use the -u flag instead of -a. Doesn't add new files, just existing ones.
Comment · 4 months ago
Oops, you're right. I was thinking of those as nearly interchangeable but they're actually pretty different.
I might give it a try when I have a chance, I'll let you know if anything comes of it.
Comment · 4 months ago
I wonder if an adversarial user could bypass the checks and achieve memory corruption / code execution. Maybe not a practical attack in most situations but a fun exercise.
> This includes things like asm volatile("" : : : "memory"), which is an old-school way of saying atomic_signal_fence(memory_order_seq_cst).
Not quite. AIUI, the first is just a barrier for the compiler, while the second is also a CPU memory barrier. Godbolt seems to confirm that.
Comment · 5 months ago
Yes but at best their "solution" is equally secure, not any better.
Comment · 6 months ago
That's a privacy violation, not relevant.
Comment · 7 months ago
For the old version support. Why not do some compile time #ifdef SUPPORT_ES3? That way library writers can support it and if the user doesn't need it they can disable it at compile time and all the legacy code will be removed
Comment · 7 months ago
It doesn't bypass it exactly, it's still accessing it via virtual memory and the page tables. It's just that the kernel maintains one big linear memory map of RAM that's writable.
Comment · 8 months ago
Citation needed. We don't even know if indistinguishability obfuscation is possible.
Comment · 8 months ago
And everyone uses Ghidra exclusively where I work. I'd say we're a serious operation
Comment · 8 months ago
Amusing because gmail doesn't even follow spec. I had to workaround gmail quirks when I worked at an email company.
Better than outlook though. What a nightmare.
Comment · 8 months ago
Half the time when people say they're using telnet (including in this thread) they're really just using the client as a TCP client, not doing anything with the Telnet protocol.
No one is stopping you from using the telnet client. And really you should just use netcat
Comment · 9 months ago
That doesn't work on any* NAND flash device, be it a flash drive, NVME, SATA, whatever.
The block device you see is an abstraction provided by the SSD controller. In reality, the flash capacity is larger. Pages are swapped out for wear leveling. If a block goes bad, it'll be taken out of commission, and your data may hide in there.
All of this happens on the SSD controller. The kernel doesn't know. You have no way to directly erase or modify specific blocks.
*Okay, there are raw NAND flash chips without controllers, but that is not you're working with when you have a SSD or flash drive. If you do have a raw flash chip, you can more directly control flash contents.
Comment · 9 months ago
To maximize device performance when wiping a drive to use for something else, I use nvme format with --ses=1.
Which in theory should free all of the blocks on the flash.
Really hard to find good documentation on this stuff. Doesn't help that 95% of internet articles just say "overwrite with zeroes" which is useless advice
Comment · 9 months ago
As far as I know, there is NO way to securely erase a USB flash drive (barring some undocumented vendor specific commands that may exist).
Comment · 9 months ago
They explicitly check if the referrer is hackernews and do that.