pedro84

12 ms·

91.
Sweet32: Birthday attacks on 64-bit block ciphers in TLS and OpenVPN(sweet32.info)
140 points by pedro84 10y ago|41 comments
92.
Breaking cryptographic trust in iOS and beyond(falseconnect.com)
7 points by pedro84 10y ago|6 comments
93.
What does the MS Secure Boot Issue teach us about key escrow?(emergentchaos.com)
2 points by pedro84 10y ago|0 comments
94.
LastPass: design flaw in communication to privileged components(bugs.chromium.org)
156 points by pedro84 10y ago|41 comments
95.
Make Sure DSA Signing Exponentiations Really Are Constant-Time [pdf](eprint.iacr.org)
3 points by pedro84 10y ago|0 comments
96.
Execute My Packet(blog.exodusintel.com)
2 points by pedro84 11y ago|0 comments
97.
What are reasonable radon limits? A screed against regulators(wcheswick.wordpress.com)
1 points by pedro84 11y ago|0 comments
98.
Extreme Privilege Escalation on Windows 8/UEFI Systems [pdf](mitre.org)
2 points by pedro84 12y ago|0 comments
99.
Git Frost – The Branch Not Maintained(mynameismichelle.com)
2 points by pedro84 12y ago|0 comments
100.
A vulnerability that wasn’t (An SMT solver example)(joxeankoret.com)
1 points by pedro84 12y ago|0 comments
101.
Share Your Where(whr.io)
1 points by pedro84 12y ago|0 comments
102.
Build Your Own Lisp(buildyourownlisp.com)
2 points by pedro84 13y ago|0 comments
103.
The Page-Fault Weird Machine: Lessons in Instruction-less Computation(usenix.org)
2 points by pedro84 13y ago|0 comments
104.
by pedro84 13y ago
"First, our tests showed that EMET default configuration can block the exploits seen in the wild." http://blogs.technet.com/b/srd/archive/2014/03/24/security-a...
105.
PRELOAD RELOAD: Get Off My Lawn(ellzey.github.io)
3 points by pedro84 13y ago|0 comments
106.
Playing Hide-and-Seek with BiOS Implants(mitre.org)
1 points by pedro84 13y ago|0 comments
107.
IETF Draft Wants To Formalize 'Man-In-The-Middle' Decryption Of Data(techdirt.com)
1 points by pedro84 13y ago|0 comments
108.
Guest Post: Try Radar for Your Next Project(hackaday.com)
3 points by pedro84 13y ago|0 comments
109.
by pedro84 13y ago
Ransomware crypto fail: The number has 128 digits, which could indicate a (big) mistake from the malware author, who wanted to generate a 128 bytes key. Finally, we simply deal with RSA-464 encryption, which can easily be broken
110.
Bitcrypt broken(blog.cassidiancybersecurity.com)
221 points by pedro84 13y ago|87 comments
111.
WRT120N fprintf Stack Overflow(devttys0.com)
189 points by pedro84 13y ago|42 comments
112.
A subfield-logarithm attack against ideal lattices(blog.cr.yp.to)
89 points by pedro84 13y ago|7 comments
113.
by pedro84 13y ago
I think there's more here than what can be fixed with tape. Your computer has computers in it that can be re-programmed in ways that the OS doesn't tell you about. From the pdf: The same technique that allows us to disable the
114.
ISeeYou: Disabling the MacBook Webcam Indicator LED(jscholarship.library.jhu.edu)
8 points by pedro84 13y ago|2 comments
115.
Unprivileged GPU access vulnerability - CVE-2013-5987(nvidia.custhelp.com)
2 points by pedro84 13y ago|0 comments
116.
Generating More Secure GPG Keys(spin.atomicobject.com)
1 points by pedro84 13y ago|0 comments
117.
Backpressure and Unbounded Concurrency in Node.js(engineering.voxer.com)
1 points by pedro84 13y ago|0 comments
118.
How many people are missing out on JavaScript enhancement?(digital.cabinetoffice.gov.uk)
8 points by pedro84 13y ago|3 comments
119.
by pedro84 13y ago
There's a walkthrough of some of those sysadmin-y things here: http://ponytech.net/blog/2013/09/10/django-deployement-ubuntu-upstart-nginx-gunicorn-and-virtualenvwrapper/
120.
RSA warns developers not to use RSA products(blog.cryptographyengineering.com)
132 points by pedro84 13y ago|69 comments

More ›