<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: CyberLily</title><link>https://news.ycombinator.com/user?id=CyberLily</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 15 Jun 2026 14:23:53 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=CyberLily" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by CyberLily in "Twin brothers wipe 96 government databases minutes after being fired"]]></title><description><![CDATA[
<p>Hashing passwords client-side is generally a bad idea, since it means that the hash effectively becomes the password. For example, if I have a database row that has the hash of the password and a bad-guy gets access to the database, they will get the hash. The benefit of a hash is that it is a one-way operation, I can't figure out the plaintext from the hash, so my account is safe. If the password is hashed on the client, and sent to the server the attacker doesn't need to reverse the hash, they can just send the hash in the request. Instead, you should send the password to the server (using TLS encryption) and do the hash and compare on the server.</p>
]]></description><pubDate>Wed, 13 May 2026 20:21:27 +0000</pubDate><link>https://news.ycombinator.com/item?id=48126972</link><dc:creator>CyberLily</dc:creator><comments>https://news.ycombinator.com/item?id=48126972</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48126972</guid></item></channel></rss>