Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
beefhash
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
by
beefhash
6y ago
> "Just Libsodium" doesn't work on anything smaller than a Raspberry-Pi, or pretty much any embedded system out there. There are alternatives out there And the same author provides a solution for those systems as well wi
62.
▲
by
beefhash
6y ago
How long until the patents expire?
63.
▲
by
beefhash
6y ago
If you want a to get this stuff into your head reasonably fast, go implement a curve. Then do it again, but in Rust (or C) and in constant-time. Then do it again, but actually computationally efficiently (i.e. optimize the hell out of a Rus
64.
▲
by
beefhash
6y ago
> I didn't know about possible patents, that sucks. (I live in the EU, though, so I can still give them the finger if I need to.) Hamburg made this IP risk pretty clear in the paper, for a bit more context on it, see [1]. Because
65.
▲
by
beefhash
6y ago
> we now have better ways of dealing with short Weierstraß curves We do? The complete Renes/Costello/Batina formulas for point addition are significantly slower at a factor of 1.4.[1] The complete formulas presented by Hambur
66.
▲
LadderLeak: Breaking Ecdsa with Less Than One Bit of Nonce Leakage
(eprint.iacr.org)
7 points
by
beefhash
6y ago
|
0 comments
67.
▲
Solitaire-y Confinement: Why we can’t stop playing a computerized card game (200
(slate.com)
2 points
by
beefhash
6y ago
|
0 comments
68.
▲
by
beefhash
6y ago
Kind of hard when the operating system does it for you... https://groups.google.com/d/msg/comp.unix.aix/0dv4N0qmgVQ/ty...
69.
▲
by
beefhash
6y ago
> The standard digest is 64-bits, but you can modify it to take 128-bits if you want a cryptographically secure hash. There's not even an attempt at a preliminary cryptanalysis anywhere as far as I can tell. I'd advise stayin
70.
▲
by
beefhash
6y ago
Can't really argue with the makers of proprietary microcontrollers about what tooling they provide though.
71.
▲
by
beefhash
6y ago
Tink addresses things libsodium doesn't really do. Native support for AWS Key Management System and its equivalent on other cloud platforms is a huge win; we should all be using more of these. But libsodium would have to start mandatin
72.
▲
by
beefhash
6y ago
Everybody hates ads until it comes to their own bottom line, I guess. Exceptions apply, of course.
73.
▲
Shogihax – Remote Code Execution on Nintendo 64 Through Morita Shogi 64
(cturt.github.io)
3 points
by
beefhash
6y ago
|
0 comments
74.
▲
by
beefhash
6y ago
(2017)
75.
▲
Cryptographic Right Answers (2018)
(latacora.singles)
2 points
by
beefhash
6y ago
|
0 comments
76.
▲
Lavender: A console font inspired by Sun Gallant Demi and the XNU console font
(github.com)
2 points
by
beefhash
6y ago
|
0 comments
77.
▲
Dedicated Security Chips in the Age of Secure Enclaves
(eprint.iacr.org)
1 points
by
beefhash
6y ago
|
0 comments
78.
▲
by
beefhash
6y ago
Note that the spec[1] requires that this tops at an implementation-defined size of integers, so you're likely not getting out of writing bignum code yourself (and even fifimplemented, the bignum operations may likely be variable-time a
79.
▲
by
beefhash
6y ago
Windows doesn't ship it, so now your build system got even more complicated on Windows.
80.
▲
by
beefhash
6y ago
That's partially on the community for making so much free (as in beer, often also as in freedom) software. The expectation is now there. Though how to reverse it remains an unsolved problem.
81.
▲
by
beefhash
6y ago
C has a proposal for #embed. http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2499.pdf
82.
▲
Surrounded by Elligators: Implementing Crypto with Nothing to Compare To
(loup-vaillant.fr)
3 points
by
beefhash
6y ago
|
0 comments
83.
▲
Regex2fat: Turn your favorite regex into FAT32
(github.com)
397 points
by
beefhash
6y ago
|
82 comments
84.
▲
by
beefhash
6y ago
wchar_t can be (a) not Unicode in any way, or (b) 16-bit, insufficient to represent a rune.
85.
▲
by
beefhash
6y ago
And every BSD out there. And whatever it is that macOS does. Microsoft looks to be the outlier to me.
86.
▲
by
beefhash
6y ago
Wait, doesn't this mean that the BSD sockets API is inherently dependent on UB, casing different socket types to each other and sometimes only using the first few members, or am I misunderstanding you?
87.
▲
by
beefhash
6y ago
C has been making strides towards complete Unicode support. I've been having trouble following along though: Am I correct in assuming that there's no actual multi-byte UTF-8 to UTF-32 Rune function and the best approximation dep
88.
▲
by
beefhash
6y ago
(Not one of the OPs:) Wasn't C11 Annex K, the notoriously failed bounds-checking interfaces, a example of not having an existing implementation?
89.
▲
by
beefhash
6y ago
Now that C2x plans to make two's complement the only sign representation, is there any reason why signed overflow has to continue being undefined behavior? On a slightly more personal note: What are some undefined behaviors that you wo
90.
▲
Ed25519 Quirks
(slowli.github.io)
1 points
by
beefhash
6y ago
|
0 comments
More ›