This is the same "logic" SJW's use to trash IT and broke working software with all their "cancelling" of "master/slave", "whitelist/blacklist" and other settled long ago terminology. "nonce" is old cryptographic term that have nothing common with blockchain. It is blockchain uses crypto algorithms with nonces that existed long before all that blockchain hype.
It is even not a word. It is a name of variable. Most programmers don't like to type long variable names and shorten them with some kind of keepeng meaning (except Java programmers, I think, but they are weird people :) ). Instead of writing something like number_to_be_used_only_once = random();, somebody once wrote n_once = random(); or just nonce = random();. This name was short and even had some decent meaning. That variable name become a term. And that's all.
False. It's not old. It's used very much today. It's a critical part of cryptography.
IDK, but it seems that 30 years is rather old for IT.
I first meet it in mid-90s. It was used in code and comments to name random sequence in MD5 hashed password exchange.
I think that it is older, since that algorithm of protected password exchange (with simplier hash) was known since 1970s
When user tried to log in to some server, server sends a nonce - random number. Client added that sequence of digits to password, calculated MD5 hash and send that hash to server. Since server knows nonce and password, it also calculated a MD5 hash from combination of nonce and password and compared this hash with hash from client. If hashes was equal, user was allowed to log in. That algorithm make the password exchange encrypted, clear password never was send over the net. Nonce was necessary to modify hash for every new login, so even if third-party sniffed hash sent to server, it will be useless, since on next login it would be different because of new nonce.
Or spew smears like 'you sound like a leftist whining about master/slave'
But it is the same thing. I used different obscene and slur words in my programs, and still sometime use them. I really don't care if anyone will try to somehow attach some shit to that usage, just will be disappointed about the IQ of that person.
I'm trying to figure out WHY this word was used; because nonce as a slur predated nonce as a cryptographic tool
There are a lot of slur in code. You will even find few "fuck"s in linux kernel sources. A lot of tools named with obscene words. If somebody wanted to mention pedo in code for some reason, he could easily and openly use something like "fucking_pedofile" or "pedo" as variable/function name without any problems. It was completely OK at the time. There was no any need to use some barely known slur for whatever reason.
And all in all, nonce is not something specific for cryptocurrency/blockchain. So the title at least incorrect. Like "Critical part of login process is "Nonce" ... Login requires pedofiles ... ", Even just viewing conspiracies.win require use of nonces. Does conspiracies.win requires pedofiles?
This is the same "logic" SJW's use to trash IT and broke working software with all their "cancelling" of "master/slave", "whitelist/blacklist" and other settled long ago terminology. "nonce" is old cryptographic term that have nothing common with blockchain. It is blockchain uses crypto algorithms with nonces that existed long before all that blockchain hype.
It is even not a word. It is a name of variable. Most programmers don't like to type long variable names and shorten them with some kind of keepeng meaning (except Java programmers, I think, but they are weird people :) ). Instead of writing something like number_to_be_used_only_once = random();, somebody once wrote n_once = random(); or just nonce = random();. This name was short and even had some decent meaning. That variable name become a term. And that's all.
IDK, but it seems that 30 years is rather old for IT.
I first meet it in mid-90s. It was used in code and comments to name random sequence in MD5 hashed password exchange. I think that it is older, since that algorithm of protected password exchange (with simplier hash) was known since 1970s
When user tried to log in to some server, server sends a nonce - random number. Client added that sequence of digits to password, calculated MD5 hash and send that hash to server. Since server knows nonce and password, it also calculated a MD5 hash from combination of nonce and password and compared this hash with hash from client. If hashes was equal, user was allowed to log in. That algorithm make the password exchange encrypted, clear password never was send over the net. Nonce was necessary to modify hash for every new login, so even if third-party sniffed hash sent to server, it will be useless, since on next login it would be different because of new nonce.
So what should I see there?
But it is the same thing. I used different obscene and slur words in my programs, and still sometime use them. I really don't care if anyone will try to somehow attach some shit to that usage, just will be disappointed about the IQ of that person.
There are a lot of slur in code. You will even find few "fuck"s in linux kernel sources. A lot of tools named with obscene words. If somebody wanted to mention pedo in code for some reason, he could easily and openly use something like "fucking_pedofile" or "pedo" as variable/function name without any problems. It was completely OK at the time. There was no any need to use some barely known slur for whatever reason.
And all in all, nonce is not something specific for cryptocurrency/blockchain. So the title at least incorrect. Like "Critical part of login process is "Nonce" ... Login requires pedofiles ... ", Even just viewing conspiracies.win require use of nonces. Does conspiracies.win requires pedofiles?