rdpintqogeogsaa

10 ms·

61.
by rdpintqogeogsaa 4y ago
Yet there are also large networks like QuakeNet or UnderNet with no TLS anywhere.
62.
by rdpintqogeogsaa 4y ago
Key part here is "are finalizing". It's still possible for at least some of the deals to fall through. I guess NTRU is the backup plan just in case and/or a method to apply pressure by saying the public is now aware ther
63.
Picking Parameters(imperialviolet.org)
3 points by rdpintqogeogsaa 4y ago|0 comments
64.
Constant-Time Source Yields Variable-Time Binary: Exploiting Curve25519-Donna(infoscience.epfl.ch)
2 points by rdpintqogeogsaa 4y ago|0 comments
65.
Capability Hardware Enhanced RISC Instructions (CHERI)(cl.cam.ac.uk)
1 points by rdpintqogeogsaa 4y ago|0 comments
66.
Webauthn in Linux with a TPM via the HID Gadget (2019)(blog.hansenpartnership.com)
1 points by rdpintqogeogsaa 4y ago|0 comments
67.
Timing Attacks(timing.attacks.cr.yp.to)
191 points by rdpintqogeogsaa 4y ago|34 comments
68.
Himitsu: A Secret Storage Manager(himitsustore.org)
2 points by rdpintqogeogsaa 4y ago|0 comments
69.
List of unsafe ed25519 signature libs(github.com)
4 points by rdpintqogeogsaa 4y ago|1 comments
70.
Password policies of most top websites fail to follow best practices(passwordpolicies.cs.princeton.edu)
34 points by rdpintqogeogsaa 4y ago|19 comments
71.
fiat-crypto: Cryptographic Primitive Code Generation by Fiat(github.com)
1 points by rdpintqogeogsaa 4y ago|0 comments
72.
by rdpintqogeogsaa 4y ago
What's the impact on AES-NI specifically? If hardware AES is impacted and no microcode updates are coming, this would be bad news. Assuming ChaPoly needs expensive masking mitigations and AES-NI is safe, ChaPoly just became a lot less
73.
Stuxnet is embarrassing, not amazing (2011)(rdist.root.org)
117 points by rdpintqogeogsaa 4y ago|91 comments
74.
BearSSL(bearssl.org)
2 points by rdpintqogeogsaa 4y ago|1 comments
75.
OpenSMTPD(opensmtpd.org)
98 points by rdpintqogeogsaa 4y ago|35 comments
76.
“Legacy” Cryptography in Fedora 36 and Red Hat Enterprise Linux 9(redhat.com)
1 points by rdpintqogeogsaa 4y ago|0 comments
77.
Responses to NIST's Proposal (1992)(cacm.acm.org)
1 points by rdpintqogeogsaa 4y ago|0 comments
78.
by rdpintqogeogsaa 4y ago
They are not. You still have strings attached: the requirement of attribution and the disclaimer. With 3-clause and 4-clause BSD, there are even more strings attached. You can't just take MIT-licensed code. You have to take the code a
79.
Building Protocols with HTTP(rfc-editor.org)
2 points by rdpintqogeogsaa 4y ago|0 comments
80.
by rdpintqogeogsaa 4y ago
From what I can tell, at least it's historically inherited. 4.4BSD had a list of airports in the same location. Its inclusion in 4.4BSD seems a mystery though. No other files on the 4.4BSD distribution seem to reference it. The atc(6)
81.
Haiku Activity and Contract May 2022(haiku-os.org)
4 points by rdpintqogeogsaa 4y ago|0 comments
82.
TLS Certificate Transparency logs don't always talk to you(utcc.utoronto.ca)
9 points by rdpintqogeogsaa 4y ago|5 comments
83.
Exploiting the Wii U's USB Descriptor parsing(garyodernichts.blogspot.com)
1 points by rdpintqogeogsaa 4y ago|0 comments
84.
One-end encryption, stronger than end-to-end(github.com)
20 points by rdpintqogeogsaa 4y ago|5 comments
85.
Child of the Internet(keeb.dev)
2 points by rdpintqogeogsaa 4y ago|0 comments
86.
Guidance on Implementing Cryptography as a Developer(github.com)
3 points by rdpintqogeogsaa 4y ago|0 comments
87.
Boot drive encryption security on Windows(threedots.ovh)
3 points by rdpintqogeogsaa 4y ago|0 comments
88.
Dangerous Gift(tbray.org)
326 points by rdpintqogeogsaa 4y ago|137 comments
89.
The Law of Strict Licenses(gavinhoward.com)
2 points by rdpintqogeogsaa 4y ago|0 comments
90.
Electrifying Ext4(pencil.toast.cafe)
2 points by rdpintqogeogsaa 4y ago|0 comments

More ›