beefhash

9 ms·

91.
AES-based Synthetic IDs: deterministic AE for 64-bit integers(github.com)
64 points by beefhash 6y ago|29 comments
92.
by beefhash 6y ago
What even is this timeline anymore. Though I don't see this recapturing the casual reverse engineering market that Ghidra ate for lunch unless they have very compelling IDA Home pricing for the decompilers as well (the “One processor f
93.
Sspam: Symbolic Simplification with PAttern Matching (2017)(github.com)
1 points by beefhash 6y ago|0 comments
94.
by beefhash 6y ago
It's a simplified description of EdDSA (and as much is said in the article), taking out the deterministic part for a random nonce, effectively presenting key-prefixed Schnorr signatures instead.
95.
by beefhash 6y ago
> I'm not sure why TweetNaCl is even considered a serious crypto library. Probably because its authors are all big-name people and their paper says: > We have placed TweetNaCl into the public domain, and we encourage applicati
96.
by beefhash 6y ago
Maybe we should gatekeep it so much though. As long as there exist at least two people capable of implementation per programming language (one to implement, another to audit), there will only ever be one, single, canonical implementatio
97.
by beefhash 6y ago
From what I can tell, they were trying to get it adopted as RFC, but then a couple more things popped up on the CFRG, so they're planning a new version[1]. It's been adopted by the CFRG officially[2]. I haven't seen any sign
98.
by beefhash 6y ago
> efficient complete formulas for Weierstrass curves were found only after Curve25519 was well established Assuming you are talking about the Renes–Costello–Batina formulas, they're complete, but not necessarily efficient. Accordi
99.
by beefhash 7y ago
To be fair, "the web" means "what Chrome does" nowadays to a lot of people. Even if it wasn't Firefox's fault but rather some web standard that Firefox adhered to, Firefox will be blamed for not being bug-for
100.
by beefhash 7y ago
ISO tends to be aggressive about their intellectual property, and given the prices of the standards, few people bother re-writing them to avoid their copyright. They have a lot of somewhat obscure standards that are highly priced, such as I
101.
by beefhash 7y ago
And I guess it was probably cheaper for Google to just buy the TLD and not fix their internal processes?
102.
by beefhash 7y ago
I feel like I should add a bit that pledge(2) and unveil(2) take the "opposite" approach of SELinux. Instead of caging an application in hopes that the cage is correctly set up, the responsibility for pledge(2) and unveil(2) is
103.
by beefhash 7y ago
Then you'd just repeat the Perl 5/Raku split. You'd have a "new" C++ that isn't actually C++ but it's called C++ with a different version number and people will then bicker for a few years until they reali
104.
by beefhash 7y ago
From a practical standpoint, I agree (I've started abusing getentropy(2) as a more portable replacement), but it violates the use case though: getentropy(2) is only intended to seed userspace RNGs. Breaking the usage scenario means bre
105.
by beefhash 7y ago
No, it wouldn't, but they've made abundantly clear they're not interested in doing anything reasonable the BSDs propose.
106.
by beefhash 7y ago
On that note, would it kill the OpenBSD guys to get on the getrandom(2) train? I get it, they're dying on the “arc4random is better” hill (and, yes, I agree), but they're literally the last people in the way of making getrandom(2)
107.
by beefhash 7y ago
The job market has been very hard on everyone lately. And looking at current event, I don't think that's going to improve in the foreseeable future.
108.
by beefhash 7y ago
Whatever it is, I hope the answer involves “implement kevent(2) instead of creating epoll(2)”.
109.
by beefhash 7y ago
> And I don't think env's file path is even in POSIX, it's just a de facto standard. You would be correct about that. And that sucks .
110.
Approaching One Driver Overhead: Making Direct3D Games Faster in Wine (2018)(comminos.com)
2 points by beefhash 7y ago|0 comments
111.
by beefhash 7y ago
> Find me one system in current use (2020) that isn't 2's complement. Fortunately, C2x will stop with the meme assumption that two's complement hasn't taken over the world (see draft N2479). It will not, however, spec
112.
by beefhash 7y ago
> and decided to release it for the benefit of the community I don't understand. You're saying “for the benefit of the community”, but then only speak about companies as negative examples. (1) Are companies inherently incapab
113.
by beefhash 7y ago
4.4BSD-Lite2 is the earliest they could do without risking some legal issues[1]. [1] https://virtuallyfun.com/wordpress/2018/11/26/why-bsd-os-is-...
114.
Signing HTTP Messages (2019)(tools.ietf.org)
3 points by beefhash 7y ago|0 comments
115.
Emulation of Unix V6 on a PDP-11 with an emulated teletype(pavel-krivanek.github.io)
62 points by beefhash 7y ago|23 comments
116.
by beefhash 7y ago
In fact, it predates C itself. See https://github.com/DoctorWkt/pdp7-unix/blob/9947fbf42bbb3c94...
117.
On C and embedded platforms(blog.teserakt.io)
9 points by beefhash 7y ago|0 comments
118.
The Shortest Signatures Ever (2016) [pdf](eprint.iacr.org)
27 points by beefhash 7y ago|4 comments
119.
by beefhash 7y ago
This looks pretty interesting and may well be an improvement over PCG[1]. For non-simulation purposes, however, using a fast-key-erasure[2] ChaCha20 or AES-256-CTR RNG has served me well enough, and doesn't leave me worrying if maybe s
120.
by beefhash 7y ago
Long prose does not benefit from those fonts. A system font is usually used for UIs and is optimized accordingly. There's more to font selection than "use the same font as native applications".

More ›