<div>It would not happen to be a letsencrypt root certificate, would it?<br></div><div><br></div><div><a href="https://www.theregister.com/2021/09/30/lets_encrypt_xero_slack_outages/">https://www.theregister.com/2021/09/30/lets_encrypt_xero_slack_outages/</a><br></div><div><br></div><div><a href="https://www.jwz.org/blog/2021/09/welp-lets-encrypt-screwed-the-pooch-again/">https://www.jwz.org/blog/2021/09/welp-lets-encrypt-screwed-the-pooch-again/</a><br></div><div><br></div><div><br></div><div ><br></div><div class="ik_mail_quote"><div>On 2021-10-01T18:14:59.000+02:00, Tobias Pape <Das.Linux@gmx.de> wrote:</div><blockquote class="ws-ng-quote"><pre style="white-space: normal;"><blockquote class="ws-ng-quote">  On 1. Oct 2021, at 18:06, gettimothy via Squeak-dev <<a class="defaultMailLink" href="mailto:squeak-dev@lists.squeakfoundation.org">squeak-dev@lists.squeakfoundation.org</a>> wrote:<br> <br> Still getting the error via Monticello.<br> <br> I can log into squeaksource just fine with my browser.<br> <br> I have a pharo image and I was able to open the repo with it.<br> <br> Is there something in squeak I need to clear?<br></blockquote> <br>Whats your os and (if linux) what's you openssl?<br>-t<br><blockquote class="ws-ng-quote"> </pre></blockquote></div>