<?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: HP/UX 11.11 SFTP Algorithm? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-11-11-sftp-algorithm/m-p/4610482#M733501</link>
    <description>HMAC = Hash-based Message Authentication Code.&lt;BR /&gt;&lt;BR /&gt;This is used for verifying the integrity of the transferred data, not for encryption.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; debug1: kex: server-&amp;gt;client aes128-ctr hmac-md5 none&lt;BR /&gt;&lt;BR /&gt;As far as I understand, the "aes128-ctr hmac-md5 none" is a triplet listing the chosen encryption, integrity check and data compression algorithms in the listed direction.&lt;BR /&gt;&lt;BR /&gt;In other words, the server will use aes128-ctr for encryption, hmac-md5 for integrity checking, and no compression.&lt;BR /&gt;&lt;BR /&gt;Somewhere near the lines you showed us, there should be another line listing the protocol choices in the client-&amp;gt;server direction.&lt;BR /&gt;&lt;BR /&gt;(You might ask: "Why would the choice of protocols ever be asymmetric?" For example, if the client is a mobile device with limited CPU power, it might not want to encrypt using an algorithm that requires a lot of CPU cycles to encrypt. &lt;BR /&gt;&lt;BR /&gt;But if decrypting using that algorithm with a correct key does take much less CPU power than encryption, the client might be willing to receive data using that protocol, and use something else for sending.)&lt;BR /&gt;&lt;BR /&gt;MK</description>
    <pubDate>Wed, 31 Mar 2010 14:19:34 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2010-03-31T14:19:34Z</dc:date>
    <item>
      <title>HP/UX 11.11 SFTP Algorithm?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-11-11-sftp-algorithm/m-p/4610481#M733500</link>
      <description>Morning all!&lt;BR /&gt;&lt;BR /&gt;I'm being asked what algorithm HP/UX 11.11 sftp uses. sftp -vvv localhost shows:&lt;BR /&gt;&lt;BR /&gt;debug1: kex: server-&amp;gt;client aes128-ctr hmac-md5 none&lt;BR /&gt;debug2: mac_setup: found hmac-md5&lt;BR /&gt;&lt;BR /&gt;So I was hoping it would be AES 128, but it looks like even to itself it's only using HMAC-MD5? That sould right, or am I looking in the wrong place?&lt;BR /&gt;&lt;BR /&gt;Server info:&lt;BR /&gt;&lt;BR /&gt;OpenSSH_5.2p1+sftpfilecontrol-v1.3, OpenSSL 0.9.8k 25 Mar 2009&lt;BR /&gt;HP-UX Secure Shell-A.05.20.004, HP-UX Secure Shell version&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;BR /&gt;&lt;BR /&gt;Leam</description>
      <pubDate>Wed, 31 Mar 2010 13:29:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-11-11-sftp-algorithm/m-p/4610481#M733500</guid>
      <dc:creator>Leam Hall</dc:creator>
      <dc:date>2010-03-31T13:29:53Z</dc:date>
    </item>
    <item>
      <title>Re: HP/UX 11.11 SFTP Algorithm?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-11-11-sftp-algorithm/m-p/4610482#M733501</link>
      <description>HMAC = Hash-based Message Authentication Code.&lt;BR /&gt;&lt;BR /&gt;This is used for verifying the integrity of the transferred data, not for encryption.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; debug1: kex: server-&amp;gt;client aes128-ctr hmac-md5 none&lt;BR /&gt;&lt;BR /&gt;As far as I understand, the "aes128-ctr hmac-md5 none" is a triplet listing the chosen encryption, integrity check and data compression algorithms in the listed direction.&lt;BR /&gt;&lt;BR /&gt;In other words, the server will use aes128-ctr for encryption, hmac-md5 for integrity checking, and no compression.&lt;BR /&gt;&lt;BR /&gt;Somewhere near the lines you showed us, there should be another line listing the protocol choices in the client-&amp;gt;server direction.&lt;BR /&gt;&lt;BR /&gt;(You might ask: "Why would the choice of protocols ever be asymmetric?" For example, if the client is a mobile device with limited CPU power, it might not want to encrypt using an algorithm that requires a lot of CPU cycles to encrypt. &lt;BR /&gt;&lt;BR /&gt;But if decrypting using that algorithm with a correct key does take much less CPU power than encryption, the client might be willing to receive data using that protocol, and use something else for sending.)&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Wed, 31 Mar 2010 14:19:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-11-11-sftp-algorithm/m-p/4610482#M733501</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2010-03-31T14:19:34Z</dc:date>
    </item>
  </channel>
</rss>

