The Cipher Behind QSYRUPWD: Reconstructing IBM i Password Hashes
blog.silentsignal.eu
The Cipher Behind QSYRUPWD: Reconstructing IBM i Password Hashes
1–10 of 11 posts
Re: The Cipher Behind QSYRUPWD: Reconstructing IBM i Password Hashes
#2Re: The Cipher Behind QSYRUPWD: Reconstructing IBM i Password Hashes
#3Link stolen from calvin on lobste.rs. https://lobste.rs/s/2dc0gb/cipher_behind_qsyrupwd_reconstruc... >
Re: The Cipher Behind QSYRUPWD: Reconstructing IBM i Password Hashes
#4Link stolen from calvin on lobste.rs. https://lobste.rs/s/2dc0gb/cipher_behind_qsyrupwd_reconstruc... >
That seems a bit harsh, we dont know if both posters discovered this article independently.
Re: The Cipher Behind QSYRUPWD: Reconstructing IBM i Password Hashes
#5Earlier quoted context omitted.
That seems a bit harsh, we dont know if both posters discovered this article independently.
I think we can assume the HN poster is well aware of where they first saw this submission link.
Since the other person decided to not post it on HN I dont see the harm in someone else reposting it here. Likewise if someone discovers something neat via HN they might repost it on, say, reddit (or vice versa).
Re: The Cipher Behind QSYRUPWD: Reconstructing IBM i Password Hashes
#6Earlier quoted context omitted.
I think we can assume the HN poster is well aware of where they first saw this submission link.
Even if they did (and I dont see any evidence either way), lobsters is an entirely different site (that also requires invites, excluding the majority of users from commenting). Since the other person decided to not post it on HN I dont see the harm in someone else reposting it here. Likewise if someone discovers something neat via HN they might repost it on, say, reddit (or vice versa).
Re: The Cipher Behind QSYRUPWD: Reconstructing IBM i Password Hashes
#7Earlier quoted context omitted.
Even if they did (and I dont see any evidence either way), lobsters is an entirely different site (that also requires invites, excluding the majority of users from commenting). Since the other person decided to not post it on HN I dont see the harm in someone else reposting it here. Likewise if someone discovers something neat via HN they might repost it on, say, reddit (or vice versa).
Uhhh, by any chance have you looked at the user name that submitted this and the user name that made the comment you replied to?
We can do Reddit on HN if we want -- hell I'm jonesing for it, I bristle at restrictions on my literary tone... but obsessing over who "stole" a link seems juvenile.
Links were made to be shared :-)
Re: The Cipher Behind QSYRUPWD: Reconstructing IBM i Password Hashes
#8Earlier quoted context omitted.
Uhhh, by any chance have you looked at the user name that submitted this and the user name that made the comment you replied to?
Did I wander into Reddit for a moment? We can do Reddit on HN if we want -- hell I'm jonesing for it, I bristle at restrictions on my literary tone... but obsessing over who "stole" a link seems juvenile. Links were made to be shared :-)
Re: The Cipher Behind QSYRUPWD: Reconstructing IBM i Password Hashes
#9Re: The Cipher Behind QSYRUPWD: Reconstructing IBM i Password Hashes
#10Earlier quoted context omitted.
Even if they did (and I dont see any evidence either way), lobsters is an entirely different site (that also requires invites, excluding the majority of users from commenting). Since the other person decided to not post it on HN I dont see the harm in someone else reposting it here. Likewise if someone discovers something neat via HN they might repost it on, say, reddit (or vice versa).
Uhhh, by any chance have you looked at the user name that submitted this and the user name that made the comment you replied to?