<?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 Modifying PSK doesn't alter the policy in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Modifying-PSK-doesn-t-alter-the-policy/m-p/59246#M11957</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have a strange behavior with one of our IPSec tunnels (I get an error about 'possibly a mismatch in pre-shared keys').&lt;/P&gt;&lt;P&gt;When I change the PSK and push the policy with the revision enabled, I receive a notification that no policy was modified hence no revision is possible. The policy installation is successful but I have an impression that the pre-shared key has not been modified since the tunnel is down with the same error.&lt;/P&gt;&lt;P&gt;We're under R77.30 (Take 216) on a open server.&lt;/P&gt;&lt;P&gt;Perhaps it's worth to mention that the affected VPN Community Name was reused. There was an old and unused VPN Community Name, which I renamed and reused for this one. The Shared Secret has been reset since then, and the Peer Name is correct.&lt;/P&gt;&lt;P&gt;Could that be the cause?&lt;/P&gt;&lt;P&gt;I also tried to remove the shared secret, save the policy, set the shared secret and install the policy - still get the same message about no revision.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Tue, 30 Jul 2019 14:53:15 GMT</pubDate>
    <dc:creator>Teddy_Brewski</dc:creator>
    <dc:date>2019-07-30T14:53:15Z</dc:date>
    <item>
      <title>Modifying PSK doesn't alter the policy</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Modifying-PSK-doesn-t-alter-the-policy/m-p/59246#M11957</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I have a strange behavior with one of our IPSec tunnels (I get an error about 'possibly a mismatch in pre-shared keys').&lt;/P&gt;&lt;P&gt;When I change the PSK and push the policy with the revision enabled, I receive a notification that no policy was modified hence no revision is possible. The policy installation is successful but I have an impression that the pre-shared key has not been modified since the tunnel is down with the same error.&lt;/P&gt;&lt;P&gt;We're under R77.30 (Take 216) on a open server.&lt;/P&gt;&lt;P&gt;Perhaps it's worth to mention that the affected VPN Community Name was reused. There was an old and unused VPN Community Name, which I renamed and reused for this one. The Shared Secret has been reset since then, and the Peer Name is correct.&lt;/P&gt;&lt;P&gt;Could that be the cause?&lt;/P&gt;&lt;P&gt;I also tried to remove the shared secret, save the policy, set the shared secret and install the policy - still get the same message about no revision.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2019 14:53:15 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Modifying-PSK-doesn-t-alter-the-policy/m-p/59246#M11957</guid>
      <dc:creator>Teddy_Brewski</dc:creator>
      <dc:date>2019-07-30T14:53:15Z</dc:date>
    </item>
    <item>
      <title>Re: Modifying PSK doesn't alter the policy</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Modifying-PSK-doesn-t-alter-the-policy/m-p/59285#M11965</link>
      <description>That sounds like some sort of corruption and it's a good idea to involve the TAC.</description>
      <pubDate>Tue, 30 Jul 2019 21:28:41 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Modifying-PSK-doesn-t-alter-the-policy/m-p/59285#M11965</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2019-07-30T21:28:41Z</dc:date>
    </item>
  </channel>
</rss>

