CodesInChaos

98 ms·

1321.
by CodesInChaos 9y ago
For CPUs/GPUs it probably wouldn't help that much, since you have to get rid of the heat produced by switching a transistor. And for storage the main issue isn't how big it is, but how cheap it is to manufacture.
1322.
by CodesInChaos 9y ago
How was that feature supposed to work concerning copyright? "Scrape random images off the internet without the site's or the user's consent and upload them to a website for commercial purposes" doesn't exactly sound
1323.
by CodesInChaos 9y ago
Passing GPUs to VMs is tricky, especially with nvidia consumer GPUs. It's certainly not "just spin up a VM".
1324.
by CodesInChaos 9y ago
My biggest issue with automatic language detection is that many websites use location to detect language, instead of the http accept headers.
1325.
by CodesInChaos 9y ago
I'd guess it's because bcrypt only supports 72-byte inputs (though there are workarounds, like pre-hashing)
1326.
by CodesInChaos 9y ago
Every dependency can run code on every computer your project runs on. That means you have to trust its author to: 1. not be malicious 2. not write a vulnerability by accident 3. not get their computer infected, their email account hijacked,
1327.
by CodesInChaos 9y ago
In my experience avoiding unlimited recursion/stackoverflows is one of the most annoying parts of writing a parser, so I find it surprising that the paper doesn't even mention that topic.
1328.
by CodesInChaos 9y ago
Probably tightly-coupled memory http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc....
1329.
by CodesInChaos 9y ago
One thing that worries me about RISC-V is how much encoding space for (major) opcodes they already used up. There are 7 bits to encode the opcodes. Of those 128 possible values, 3/4 are used for 16-bit compressed/thumb instruction
1330.
by CodesInChaos 9y ago
At a glance shadowsocks doesn't look like a secure protocol to me, so even if you use shadowsocks to obfuscate the protocol, you still need to tunnel a secure encrypted protocol inside of shadowsocks. I don't expect most VPN users
1331.
by CodesInChaos 10y ago
120 bits for the birth date is much too big. It's closer to 14 bits (taking your 42 year figure it's log2(42*365)=13.9).
1332.
by CodesInChaos 10y ago
> The default hash table has better security against malicious input by using a slower hashing algorithm. I think an adaptive hash that switches from fast to secure when collisions are detected would make a better default choice (at the
1333.
by CodesInChaos 11y ago
It's difficult to implement efficiently: * If you use the underlying hash as a black-box, each HMAC invocation compresses 4 blocks. An optimized implementation will only require 2. Many implementations (e.g. the .NET one) don't in
1334.
by CodesInChaos 14y ago
DMCA'd CipherCloud discussion on stackexchange online again (minus images). The Copyright part of the notice only covered the images and stackexchange apparently didn't consider the text part of the posts a ToS violation. I expanded my anal
1335.
by CodesInChaos 14y ago
Now stackexchange forwarded the DMCA notice to the involved users. http://meta.crypto.stackexchange.com/q/250/180 CipherCloud claim copyright infringement on the three images used to evidence the posts. They also claim that certain statem
1336.
by CodesInChaos 14y ago
EFF has a collection of DMCA abuses: https://www.eff.org/takedowns
1337.
by CodesInChaos 14y ago
Why do you disable the newest protocol version (TLS 1.0 is essentially SSL 3.1) but keep the older versions? I'd enable SSL 3.0 and TLS 1.x, but disable SSL 2.0 since it's old and broken.
1338.
by CodesInChaos 14y ago
Is `rand` a secure random number in ruby? In many programming languages/implementations the default PRNG is only seeded with the current time, which leads to quite low entropy.