@AviD weight ... the heavier the better, and the light ones that promise more than the heavy ones are pure BS, or they use batteries that will only be good for a few years... well, my 2 cents at least, but this might have changed somewhat in the last years that I didn't follow it, tho doubt it
well that's 0.168 kWh capacity so you can calculate yourself how long it'd last if you have power meter that you could plug between the wall socket and any equipment you'd like it to power up
@TerryChia Also, can you, with a clear conscious, say that your "answer" answers the question? All day, everyday, we flag answers for not meeting our quality criteria, and then we break that ourselves? For what? 50 rep?
@TerryChia and please understand that the issue isn't that I don't like upvoting you, no no no. I've serial-upvoted you many times (because I like most of your answers, and usually under the threshold). It's just that recently I've been getting sick with this rep-whoring. Not the one where we self-plug our answers, no no, where we post shitty "answers".
@Adnan Yes. 1) I opened an issue with the developers asking for an explanation. 2) No response from the developers. No explanation available elsewhere. A "we will probably never know" answer is still an answer. 3) I provide a way to comply with the RFC. Yes, it's trivial. So what? It's still a solution.
Yes, I'm doing it for the bounty (and the hat, don't really care about the rep) but I don't see a problem with that.
Like I said, this isn't the first time we have disagreed on a matter like this. I won't convince you, you won't convince me so I don't see the point in trying.
@Adnan The answer is right there. "However, there has been no official replies from the developers on it." ; "While there is probably no good explanation for why Google opted for 80 bits instead of the recommended 160 bits as per the RFC"
@Adnan UPS is surge protection, and I don't know of any batteries that couldn't handle occasional spikes, they're just charge rate rated so they don't overheat mostly, or ruin electrolyte
This will no longer work, the adviza server is no longer running
Found this in the code:
// Yes, dear person reading this, there's a secret trigger. But you'll have to
// work a little bit to find out what it is.
Challenge accepted
So, here's a surefire trigger, that ought to work for a fe...
@TerryChia Fantastic. If you're the service provider (the server with access to all of the seeds), can you deduce the seed used to generate a certain OTP?
@Adnan Bruteforce is probably the easiest method. Just test generate the OTP for each and every seed until you find one that matches for that time period. The operation is very fast after all.
I'm not aware of any weaknesses on the algorithm itself, then again I just implement it according to the RFC. Not a cryptographer after all.
@TerryChia I haven't used Fedora in a while, but no, I usually never had problems. Those that I did have were almost always display driver related. As in the Nvidia drivers didn't work, or I had to completely rebuild my xorg config, and I was using multimonitor so I couldn't rely on nouveau.
@TerryChia From what I understand it's better now that they have tools to do it.
@AviD So, he is now in the leaderboard of the suggested edits because he edited his own question even though he has 1 rep? This still makes no damn sense.
Short answer: To prevent brute forcing the CSRF token.
Let's take a trivial example: let's say your token is a single digit, accepting values from 0 to 9.
Now sure, an attacker cannot read this value from the cookie or header, but she does not have to - she can just send 10 CSRF requests, one...
This will no longer work, the adviza server is no longer running
Found this in the code:
// Yes, dear person reading this, there's a secret trigger. But you'll have to
// work a little bit to find out what it is.
Challenge accepted
So, here's a surefire trigger, that ought to work for a fe...
