ircCloud because my self hosted push notifications were failing and it worked right away.
Irssi before I started depending on push notifications though.
ircCloud because my self hosted push notifications were failing and it worked right away.
Irssi before I started depending on push notifications though.
What makes it more of a minefield than email?
I agree. Premium modern plastic or resin beats metal or glass any day.
Better grip. Better duribiliy. Transparent to radio. Easier to repair or replace. It’s just better.
Do you also prefer to drink water out of the toilet? I know taste is subjective but…
CMD.EXE is eye cancer. Whatever launched when I searched for powershell was a slightly better blue version. What are you using that you actually like?
Self-hosted Bitwarden. I just pay $10 for their pro hosted version because they’ve not given me any reason to doubt them yet but I hear self-hosted is easy.
I like it. A note that says, “I thought I could squeeze in but there wasn’t enough room. Sorry about the damage.” Might make them reconsider doing this again.
Semantics aside it sounds like we are in agreement. Have another upvote. :)
Why does upvoting feel better without a karma system? shrug
I’m a bit behind on password specific hashing techniques. Thanks for the education.
My background more in general purpose one way hashing functions where we want to be able to calculate hashes quickly, without collisions, and using a consistent amount of resources.
If the goal is to be resource intensive why don’t modern hashing functions designed to use more resources? What’s the technical problem keeping Argon2 from being designed to eat even more cycles?
True. I was all kinds of incorrect in my hasty typing. I’ll update it to be less wrong.
I was incorrect about the goal being minimal resources. I should have written that that goal was to have controlled resource usage. The salt does not increase the expense of the the hash function. Key stretching techniques like adding rounds increase the expense to reach the final hash output but does not increase the expense of the hash function. High password length allowances of several thousand characters should not lead to a denial of service attack but they don’t materially increase security after a certain length either.
I was incorrect but I still disagree with you. The hashing function is not designed to be resource intensive but to have a controlled cost. Key stretching by adding rounds repeats the controlled cost to make computing the final hash more expensive but the message length passed to the function isn’t really an issue. After the first round it doesn’t matter if the message length was 10, 128, or 1024 bytes because each round after is only getting exactly the number of bytes the one way hash outputs.
Totally true. I stand corrected. Thank you.
Edited to remove untrue information. Thanks for the corrections everyone.
Now do the A spec.