<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Password question in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/password-question/m-p/3494553#M845446</link>
    <description>I should also add that as another UNIX irony, the crypt command (as opposed to the crypt() function) DOES do encryption; ie, it produces reversible results.</description>
    <pubDate>Mon, 28 Feb 2005 15:13:25 GMT</pubDate>
    <dc:creator>A. Clay Stephenson</dc:creator>
    <dc:date>2005-02-28T15:13:25Z</dc:date>
    <item>
      <title>Password question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/password-question/m-p/3494550#M845443</link>
      <description>Hello experts,&lt;BR /&gt;&lt;BR /&gt;I have noticed that in several threads, passwords are referred to as "encrypted" and sometimes they are referred to as "hashes". Which is correct or are these just different names for the same thing?&lt;BR /&gt;&lt;BR /&gt;TIA,&lt;BR /&gt;Ryan&lt;BR /&gt;</description>
      <pubDate>Mon, 28 Feb 2005 14:52:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/password-question/m-p/3494550#M845443</guid>
      <dc:creator>Ryan Clerk</dc:creator>
      <dc:date>2005-02-28T14:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: Password question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/password-question/m-p/3494551#M845444</link>
      <description>While these terms are often used interchangably when referring to the UNIX passwd algorithm, technically it is a hash. An encrypted password is reversible; ie, one could apply an algorithm to the encrypted password and retrieve the plaintext. In a hashing algorithm, information is intentionally lost so that the process is not reversible.</description>
      <pubDate>Mon, 28 Feb 2005 14:55:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/password-question/m-p/3494551#M845444</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-02-28T14:55:02Z</dc:date>
    </item>
    <item>
      <title>Re: Password question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/password-question/m-p/3494552#M845445</link>
      <description>I should add that one of the true ironies in UNIX is that the function that creates this hash is called crypt even though it does not do encryption. So go figure.&lt;BR /&gt;</description>
      <pubDate>Mon, 28 Feb 2005 14:57:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/password-question/m-p/3494552#M845445</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-02-28T14:57:05Z</dc:date>
    </item>
    <item>
      <title>Re: Password question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/password-question/m-p/3494553#M845446</link>
      <description>I should also add that as another UNIX irony, the crypt command (as opposed to the crypt() function) DOES do encryption; ie, it produces reversible results.</description>
      <pubDate>Mon, 28 Feb 2005 15:13:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/password-question/m-p/3494553#M845446</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-02-28T15:13:25Z</dc:date>
    </item>
  </channel>
</rss>

