News for hackers. Stuff that matters.

fcvarela

Re:Secondhand EVs Are Starting to Look Like a Bargain on Thursday February 08, 2024 @02:41PM (#39306597)
ID.5 listed as least depreciating. Mine was 55k new less than a year ago and it’s worth 30k. Definitely not the 10% mentioned in the article.
This is like saying 'yes' exists in all languages because there's an equivalent in every language... It's... a bit clikbaity
Nice article, may I ask what tools you used to produce the illustrations?
FWIW i've just verified this on a DS1019+ running the latest DSM. My certificate disappeared after rebooting and the default synology one (which I had deleted) reappeared.
Re:Apple’s Latest Macs Have a Serious Audio Glitching Bug on Tuesday February 19, 2019 @01:59AM (#19197175)
As frustrated with Apple as the next person, but I have never experienced this using a bunch of interfaces and devices with their own clock source...
Re:JSON Web Tokens should be avoided on Tuesday March 14, 2017 @10:00AM (#13867504)
The spec doesn't govern what applications can and cannot accept, it governs what contents are valid in tokens. 'None' is valid, that means my parser library will accept it, it doesn't mean my application must accept the token as valid.

Example: The fact that my service has an http stack which must parse a cookie header doesn't mean my app must accept its contents as valid. There's a lot of confusion on this thread about which components should/must do what things.

Re:JSON Web Tokens should be avoided on Tuesday March 14, 2017 @05:25AM (#13866132)
I don't think the spec meant to read that you must allow the client to be able to forge tokens by accepting tokens issued by it without an algo or signature.

If you issue tokens with none, then you will have to accept them when clients send them back. This is obviously a very bad idea, but that's all th spec says. If the issuer chooses to be insecure, that is a valid choice.

If you issue tokens with a specific algo, and clients send them back with a different or none header, you know they have been forged.

The spec allows issuers to decide whether to use none, it doesn't say you must trust none tokens if you know you didn't issue them.

Re:JSON Web Tokens should be avoided on Tuesday March 14, 2017 @04:48AM (#13865991)
"Send a header that specifies the "none" algorithm be used"

Why would an issuer ever let a client decide what algo to use?

"Send a header that specifies the "HS256" algorithm when the application normally signs messages with an RSA public key."

Again, under what circumstances would a header be used by the client to ask for a specific implementation?

What about encrypted client side cookies - would you let the client "send a header" to specify which key to use???

The only problems you highlighted are serious input validation issues and a naive, broken trust model.