"MuPDF versions before 1.28.5 use an implementation of the drand48 family" yeah, ok, so they're basically not doing real encryption. The number of bits in the key space isn't the real story; the keys simply aren't cryptographically random.
What is wrong with software engineers that we keep making really stupid basic mistakes like this? Sometimes I think programming should require licensing and regular testing.
btw, the idea that the system rng isnt good enough, or "runs out" or whatever, is no longer true on pretty much every modern, widely used os.
btw... im sure there's some legacy rng in windows or some shit that isnt good. read the docs but if it's the blessed system rng, you're probably fine!
although... i suppose if this is news to you (the person reading this), then you probably shouldn't be implementing whatever you are that really requires prng. ask a friend for help. im not trying to be a jerk, i just want to make sure you dont hurt yourself!
PDFs are usually untrusted input and C provides no assurance there isn't a bug in the code that allows corrupted input to turn into arbitrary remote code execution.
I think the claim is hyperbolic, since most people memory-unsafe PDF implementations, but PDF is a monster format, a metaformat that brings in virtually every conceivable display format, and their renderer implementations with them, often poorly-maintained, never-touched reference implementations from the before times. PDF is pretty scary.
"MuPDF versions before 1.28.5 use an implementation of the drand48 family" yeah, ok, so they're basically not doing real encryption. The number of bits in the key space isn't the real story; the keys simply aren't cryptographically random.
What is wrong with software engineers that we keep making really stupid basic mistakes like this? Sometimes I think programming should require licensing and regular testing.
This is partly why I'm not too worried about AI slopcode.
The human bar is not that high.
I would much rather have rigorous testing than a filter based on the origin of the code.
I think it's safe to assume anything associated with PDFs is radioactive.
Those are not the "software engineers" but coders, those who like to say that the university degree doesn't add anything in programming.
one and the same
Rule #1 of rolling your own RNG: don’t.
Rule #2? Please don’t.
That's why we use the system RNG !
Be careful to use the cryptographic one, not rand(3)
And if you're a sysadmin, be extremely careful when generating keys in VMs or embedded devices.
btw, the idea that the system rng isnt good enough, or "runs out" or whatever, is no longer true on pretty much every modern, widely used os.
btw... im sure there's some legacy rng in windows or some shit that isnt good. read the docs but if it's the blessed system rng, you're probably fine!
although... i suppose if this is news to you (the person reading this), then you probably shouldn't be implementing whatever you are that really requires prng. ask a friend for help. im not trying to be a jerk, i just want to make sure you dont hurt yourself!
I assume this is the fruit of AI-driven decompilation? Nice work.
Obligatory xkcd https://m.xkcd.com/221/
Wonderful.
it's like the weak hardware wallet entropy bug
You'd have to be completely off your rocker to use a PDF tool written in C anyway.
very VERY few people judge tools like this by the language used to develop them.
How many people judge their tools based on the AES key entropy?
A lot actually.
You're confusing just assuming by default its enough for purpose rather than not caring at all.
just down vote it.
You can downvote anything not interesting.
If he have list some alternative or give example, it might be interesting.
What are the alternatives?
PDF.js, for example. It's what Firefox uses, and most websites with integrated on-page PDF viewing functionality.
Genuine question, since I'm not very knowledgeable about this: why is using C for a PDF tool such a bad idea?
PDFs are usually untrusted input and C provides no assurance there isn't a bug in the code that allows corrupted input to turn into arbitrary remote code execution.
I think the claim is hyperbolic, since most people memory-unsafe PDF implementations, but PDF is a monster format, a metaformat that brings in virtually every conceivable display format, and their renderer implementations with them, often poorly-maintained, never-touched reference implementations from the before times. PDF is pretty scary.
buffer overflow vulnerability in code dealing with user generated data and a complex file format.