That's really neat! Seems potentially adaptable to paper currency--a verifiable QR code digital signature of the bill's serial number creates a cryptographically hard obstacle to counterfeiting!
when you unblind a blind signature all the signer knows is that it's a signature they signed at some point, they know nothing (true zero knowledge) about when or where they signed it among all the other signatures.
Yes, and then you have a signed piece of data that others can verify. How does that help you with preventing duplication of signatures?
E-cash depends on the secrecy of the signed data, and immediate redemption with the issuer once it's been spent/accepted. This is a terrible model for physical cash.
> immediate redemption with the issuer once it's been spent/accepted. This is a terrible model for physical cash
not when everything is now online.
also the obvious way such cash would work is that "redemption" is just the new minting of coin. the central authority will mint a new coin by blindly signing your secret after you "destroy" the spent coin by giving them the unblinded signature.
This thread is about printing QR codes on physical cash. GGP explicitly said:
> That's really neat! Seems potentially adaptable to paper currency--a verifiable QR code digital signature of the bill's serial number creates a cryptographically hard obstacle to counterfeiting!
I don't see how any e-cash solutions can help here.
it would depend on the government and the situation. I suspect most don't realize this is possible. a small government can generate immediate demand for their currency doing this.
The original e-cash paper is from 1983. Governments absolutely know this is possible.
It's just much "too private" to get any political traction. At the very least, I suspect an acceptable modern alternative would either have caps on what can be sent/received completely anonymously (e.g. per recipient and timespan) or want non-anonymous recipients (to allow for VAT/sales tax accounting etc.)
I don't have a basis for how long this might take. As the author mentions "All bugs become shallow once they can be reproduced.", but only after spending probably the largest amount of time waiting for new incident reports to come in, and then analyzing the reports (e.g. to determine most incidents occurred on the last day of the month), and hours staring at application and kernel code. It's very impressive, but certainly the largest amount of time in the 10 month duration was not actually debugging. The "moment of extraordinary clarity" probably sprung out of years of experience.
Ah, I guess my thinking is that they didn't really focus on it. It was annoying but not high priority ... until they started to get an inkling of what was actually going on.
Agreed, about 99% of admins I know would not be able to identify this error, and most likely most Hacker News reads. The last sentence on your post is very true.
I’ve worked with (and been) a dev for several decades, and I can count on one hand the number of folks who would have a chance of figuring this out, and 2 fingers the number of folks who WOULD.
Of course, most never try to optimize or go so deep like this that they would ever need to, so there is that!
Reading the last paragraph, I did not come away with the same impression you did: "Regina is now a photography technician at Barnet and Southgate College."
And the fact that it was "discovered" which makes it sound like it was found in a dead person's lab or something. The article really gives the impression that she's dead, which is odd if that's not what is intended.
I think your statement is more true of CentOS than Ubuntu. Many Ubuntu server installations choose it because it is free and reputedly easy, and pass up CentOS because it doesn't have a lot of selling points that appeal directly to non-Linux users, nor RHEL because it costs money.
Also your comment reminds me of an argument against stealing music on the Internet, lol.
I wanted to voice my concurrence with the sentiment ensconced in the rudeness you are probably being downvoted for: I am in my twenties, generally operate from the perspective of one who thinks he "has shit to do" (in fact I use that very phrase frequently to characterize my obligations and commitments), and don't see myself having time to learn a new tool, method, or technique every time I have a need to express myself, whether professionally or personally. I don't believe this attitude is uncommon and is probably worth taking into consideration by those who would persuade people like your brother and me to use new things. Such as node.js.
Node.js is just JS running on server. I would rather invest in learning some strong functional language. The more different high-level _paradigms_ you learn in your twenties - the better.
reply