<?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 CHACHA20_POLY1305 Support? in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/chacha20-poly1305-support/m-p/213732#M62145</link>
    <description>&lt;P&gt;Anyone know or heard when we might get&amp;nbsp;CHACHA20_POLY1305 cipher support for Inbound Decryption?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I finally came across a server using it... my Enterprise Services team is setting up a Papercut on-prem server and it seems to be running multiple web services.&amp;nbsp; One service is using our standard public cert we've purchased with standard cipher suites and the other is using a self-signed Papercut cert&amp;nbsp;(seems to just be for mobility printing) and supports the afforementioned cipher.&amp;nbsp; I'm considering decryption here so we can do app visibility what would otherwise appear as&amp;nbsp; SSL over TCP 9164... alternatively I guess I could create an app for it or multiple security policy rules but decryption just seems cleaner.&amp;nbsp; We were able to get a copy of the cert and key for this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're investigating how to disable that cipher on the server but, so far, have only found instructions on cipher modification for the other service.&lt;/P&gt;</description>
    <pubDate>Wed, 09 May 2018 12:55:41 GMT</pubDate>
    <dc:creator>jsalmans</dc:creator>
    <dc:date>2018-05-09T12:55:41Z</dc:date>
    <item>
      <title>CHACHA20_POLY1305 Support?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/chacha20-poly1305-support/m-p/213732#M62145</link>
      <description>&lt;P&gt;Anyone know or heard when we might get&amp;nbsp;CHACHA20_POLY1305 cipher support for Inbound Decryption?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I finally came across a server using it... my Enterprise Services team is setting up a Papercut on-prem server and it seems to be running multiple web services.&amp;nbsp; One service is using our standard public cert we've purchased with standard cipher suites and the other is using a self-signed Papercut cert&amp;nbsp;(seems to just be for mobility printing) and supports the afforementioned cipher.&amp;nbsp; I'm considering decryption here so we can do app visibility what would otherwise appear as&amp;nbsp; SSL over TCP 9164... alternatively I guess I could create an app for it or multiple security policy rules but decryption just seems cleaner.&amp;nbsp; We were able to get a copy of the cert and key for this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We're investigating how to disable that cipher on the server but, so far, have only found instructions on cipher modification for the other service.&lt;/P&gt;</description>
      <pubDate>Wed, 09 May 2018 12:55:41 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/chacha20-poly1305-support/m-p/213732#M62145</guid>
      <dc:creator>jsalmans</dc:creator>
      <dc:date>2018-05-09T12:55:41Z</dc:date>
    </item>
    <item>
      <title>Re: CHACHA20_POLY1305 Support?</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/chacha20-poly1305-support/m-p/213810#M62168</link>
      <description>&lt;P&gt;In order to get more information on this, you need to ask your sales engineer.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Maybe there is an existing feature request that you can vote for or you could create a new one this way.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 09 May 2018 21:26:28 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/chacha20-poly1305-support/m-p/213810#M62168</guid>
      <dc:creator>Remo</dc:creator>
      <dc:date>2018-05-09T21:26:28Z</dc:date>
    </item>
  </channel>
</rss>

