zx2c4

8 ms·

31.
by zx2c4 2y ago
From the article: "It remains possible to put arbitrary bytes AFTER the parts of the shell script that get parsed & executed (like some Solaris patch files do). "
32.
Provable Security of Linux-DRBG in the Seedless Robustness Model [pdf](eprint.iacr.org)
43 points by zx2c4 2y ago|3 comments
33.
by zx2c4 2y ago
Why fork/copy&paste wireguard-go source code instead of using wireguard-go's existing netstack package? Couldn't you help improve instead?
34.
Area – group chat for creatives rather than employees(area.cx)
3 points by zx2c4 3y ago|0 comments
35.
by zx2c4 3y ago
I would be interested to learn from somebody with experience using both Bun and Deno: which one is actually the more compelling Node successor? Bun's website makes some impressive performance claims over Deno. Are these true in practic
36.
by zx2c4 3y ago
Maybe OP is thinking of https://paste.sh/Uwyu3Clb#MSWkjF81G0RvLYtrU6wic6LZ ?
37.
by zx2c4 3y ago
Sounds like you have a handy script to paste here... :)
38.
by zx2c4 3y ago
I love the initiative, of course. How could I not? The idea of folks casually taking a dip in this city is really nice. I spend a lot of time beside the Seine - writing code on my laptop, even! - and being able to dangle my legs in sounds n
39.
by zx2c4 4y ago
I love this project. Super simple to interface with, accomplishes the task very well, reliable, good documentation. It's hard to think of better design and execution for this type of utility. I use it to get notifications of the CI run
40.
by zx2c4 4y ago
Yes! Very excited by this. We developed this together out-of-tree, and it's been available in ports (FreeBSD's package system) for a while now. This here is about moving it into the FreeBSD base system, so that it'll now be d
41.
by zx2c4 4y ago
The relevant commit is here: https://github.com/cschoenebeck/qemu/commit/8ab70b8958a8f9cb...
42.
by zx2c4 4y ago
I too really loved Fireworks (and Dreamweaver) back in the Macromedia days. As a kid then, it was really very intuitive to do all sorts of odd creative projects easily. Riding on nostalgia fumes, I went searching for screenshots and in the
43.
Bootloader RNG seeding support on Linux 6.0(twitter.com)
2 points by zx2c4 4y ago|0 comments
44.
by zx2c4 4y ago
> This is what the patch does. It does not handle the case of VM resume yet. Actually, it does. Look at the use of v->generation.
45.
by zx2c4 4y ago
> If a memory corruption occurs, or my process’s memory contents can be disclosed somehow (easier to do against a userspace process than against the kernel!), I don’t have truly random numbers anymore. Yea, that's definitely a downs
46.
by zx2c4 4y ago
It's kind of wild, yea. I'd rather not do it. But if it's between unsafe userspace implementations and this thing, this thing is better. Maybe people will decide they don't care about hyperspeed card shuffling or whateve
47.
Linux RNG RFC Patch: implement getrandom() in vDSO(lore.kernel.org)
102 points by zx2c4 4y ago|67 comments
48.
by zx2c4 4y ago
If you're into the open ISA idea but find the big guys a bit intimidating, you might have fun with OpenRISC. At least lately I've had a blast hacking on it. The kernel and QEMU implementations are very simple, and Stafford Horne i
49.
by zx2c4 4y ago
I'll spare ya the trouble. - Unrolled tweets: https://threadreaderapp.com/thread/1528494394604761094.html - The merge commit: https://git.kernel.org/pub/scm/linux/kernel/git&#x2
50.
Linux kernel RNG enhancements for 5.19(twitter.com)
121 points by zx2c4 4y ago|25 comments
51.
Improved Dual Lattice Attack(groups.google.com)
2 points by zx2c4 5y ago|0 comments
52.
by zx2c4 5y ago
CONFIG_RANDOM_TRUST_CPU=y CONFIG_RANDOM_TRUST_BOOTLOADER=y CONFIG_HW_RANDOM=y CONFIG_HW_RANDOM_TPM=y and so forth all exist.
53.
by zx2c4 5y ago
That's what this demo code project is about: https://git.zx2c4.com/seedrng/tree/seedrng.c https://git.zx2c4.com/seedrng/about/ https://twitter.com/EdgeSecurity/
54.
by zx2c4 5y ago
> (3) as mostly a non-problem (like, you do the best you can to get compromise recovery from a CSPRNG, you don't do nothing, but you don't hold up progress on it). Mitigating that attack is the main selling point of Fortuna, wh
55.
by zx2c4 5y ago
There are a few intertwined closely related pitfalls that are each subtly different: 1) "premature first" wrt non-local attacker: this is the problem you identified - the RNG initializes when there's actually only 1 bit of en
56.
by zx2c4 5y ago
> I'm surprised to be reading justifications that amount to "it's been deployed for several years now, so we think it's OK", I'm not making any claims or justifications about it being good or not. Just a sim
57.
Random number generator enhancements for Linux 5.17 and 5.18(zx2c4.com)
17 points by zx2c4 5y ago|1 comments
58.
by zx2c4 5y ago
Here's the document for that change: http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2841.htm > In this proposal, a function declarator without a parameter list declares a prototype for a f
59.
by zx2c4 5y ago
Right, it unifies /dev/urandom, /dev/random, and getrandom(flags=0) to all do exactly the same thing. Most modern userspaces already use getrandom(flags=0). Nothing changes for them. They already count on the rng being s
60.
by zx2c4 5y ago
Yes. This happens via random.c's add_hwgenerator_randomness() hook, which the hwrng framework calls from a kthread.

More ›