<div dir="ltr">I think I could have written a piece of that better....<div><br></div><div>"...which is at a random/unpredictable time, where it will not for port 80 traffic to port 443 for a very specific GET Request to a very specific URL."</div><div><br></div><div>I think that's better. Anyway, I read it in the documentation, so if what I wrote is confusing, just read the docs. 1:00am email replies. sheesh!</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 23, 2020 at 1:13 AM Anthony Holloway <<a href="mailto:avholloway%2Bcisco-voip@gmail.com">avholloway+cisco-voip@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">First and foremost, the document describes how port 80 is used pretty well. It goes on to say that its no less secure than port 443, because the same underlying program/process answers to both, thus is susceptible to the same attacks.<div><br></div><div>People think it's less secure because it's clear text communication, but that's not pertinent to how people attack a host. It is however, how you intercept communications, and then use that information to your advantage.</div><div><br></div><div>However, the document also describes how port 80 is auto redirecting all traffic to 443 by default, until the renewal process starts, which is at a random/unpredictable time, and is only changed to redirect port 80 traffic to 443 for a very specific GET Request to a very specific URL. In which case, the port 80 traffic is then redirected to another separate web server instance which is spun up just in this moment to handle the comms with let's encrypt, and as soon as it's done, the web server instance is turned off, and all port 80 traffic is again redirected to 443.</div><div><br></div><div>So, the security of the system is actually pretty tight. Is it 100%? probably not. But then again, what truly is 100% secure?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 22, 2020 at 3:42 PM Riley, Sean <<a href="mailto:SRiley@robinsonbradshaw.com" target="_blank">SRiley@robinsonbradshaw.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:rgb(31,73,125)">Thanks for the reply and cliffs notes about the setup. My security team has concerns with having port 80 open to facility the Let’s Encrypt process. Documentation
states something about allowing the built in protections without giving much info on what those protections are.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:rgb(31,73,125)">I would love to be able to set it and forget it.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11pt;font-family:Calibri,sans-serif">From:</span></b><span style="font-size:11pt;font-family:Calibri,sans-serif"> Anthony Holloway <<a href="mailto:avholloway%2Bcisco-voip@gmail.com" target="_blank">avholloway+cisco-voip@gmail.com</a>>
<br>
<b>Sent:</b> Friday, April 17, 2020 4:23 PM<br>
<b>To:</b> Riley, Sean <<a href="mailto:SRiley@robinsonbradshaw.com" target="_blank">SRiley@robinsonbradshaw.com</a>><br>
<b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Renewing Expressway E Cert<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal"><strong><span style="font-size:9pt;font-family:Arial,sans-serif;color:red">WARNING:
</span></strong><strong><span style="font-size:9pt;font-family:Arial,sans-serif;color:black">External Email
</span></strong><span style="font-size:9pt;font-family:Helvetica,sans-serif;color:black"><u></u><u></u></span></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" align="center">
</div>
</div>
<p class="MsoNormal">This might be an unpopular opinion, but I think using the free certs provided by let's encrypt, coupled with it being automatic from now on, it's just an unbeatable combination.<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Here are my cliff notes:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Reference Document:<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"><a href="https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X12-5/exwy_b_certificate-creation-use-deployment-guide/exwy_b_certificate-creation-use-deployment-guide_chapter_0100.html" target="_blank"><span style="color:rgb(5,99,193)">https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X12-5/exwy_b_certificate-creation-use-deployment-guide/exwy_b_certificate-creation-use-deployment-guide_chapter_0100.html</span></a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif"> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">High Level Steps:<u></u><u></u></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Expressway 12.5.7 to avoid ACMEv1 vs ACMEv2 registration issues (<a href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr82346" target="_blank"><span style="color:rgb(5,99,193)">https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvr82346</span></a>)<u></u><u></u></span></li><li class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">For your Unified CM registrations domains don’t use parent domain only (E.g.,
<a href="http://company.com" target="_blank">company.com</a>), switch to CollabEdgeDNS format instead (E.g.,
<a href="http://collab-edge.company.com" target="_blank">collab-edge.company.com</a>), because you’ll need that in the next step<u></u><u></u></span></li><li class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">DNS A records for the Expressway-E FQDN and the CM registration domains<u></u><u></u></span></li><li class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Upload the root and intermediates for Let’s Encrypt (needed on both Expressway-E and Expressway-C) (certs are linked in documentation)<u></u><u></u></span></li><li class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Enable the ACME client on Expressway-E and supply any email address you want to link to this registration (This creates your account with Let’s
Encrypt)<u></u><u></u></span></li><li class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Generate a new CSR (Server Certificate Only, Domain Cert Was Not Needed)<u></u><u></u></span></li><li class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Click button to Submit CSR to ACME<u></u><u></u></span></li><li class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Click button to Deploy New Certificate on Expressway-E (documentation states this is non-service impacting)<u></u><u></u></span></li><li class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Setup the automatic scheduler so you never have to deal with this again<u></u><u></u></span></li><li class="MsoNormal"><span style="font-size:11pt;font-family:Calibri,sans-serif">Sit back, relax and enjoy free shit<u></u><u></u></span></li></ol>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Fri, Apr 17, 2020 at 1:43 PM Riley, Sean <<a href="mailto:SRiley@robinsonbradshaw.com" target="_blank">SRiley@robinsonbradshaw.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">We had our Cisco partner setup our Expressways a couple of years ago. It is a cluster with 2 E’s and 2 C’s currently
at v 12.5.7 using for MRA. I have been managing them, installing updates, troubleshooting etc. The public Edge cert is up for renewal. Can anyone provide advice on renewing this cert? I am planning on just renewing with the same cert provider, but was
interested in if there is anything to watch out for. Example, will there be a service interruption when replacing the cert? Or just install the new cert/pk and rest easy?</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">Thanks in advance.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10pt;font-family:Arial,sans-serif">Sean.</span><u></u><u></u></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
</blockquote></div>
</blockquote></div>