<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I think this is a bigger issue.<div><br></div><div>For instance, I tried visiting https://mirror-master.dragonflybsd.org/dports/dragonfly:6.4:x86:64/ with Firefox on my Apple MacBook Pro and got:</div><div>```</div><div><div>Websites prove their identity via certificates, which are valid for a set time period. The certificate for mirror-master.dragonflybsd.org expired on 5/31/2024.</div><div> </div><div>Error code: SEC_ERROR_EXPIRED_CERTIFICATE</div></div><div>```</div><div><br></div><div>Of course, there’s always openssl to tell us what’s up:</div><div><div><br></div><div>(cpython312) InvincibleReason:~$ openssl s_client -servername mirror-master.dragonflybsd.org -connect mirror-master.dragonflybsd.org:443 2>/dev/null | openssl x509 -noout -dates</div><div>notBefore=Mar 2 11:15:56 2024 GMT</div><div>notAfter=May 31 11:15:55 2024 GMT</div></div><div><br></div><div>And before anyone mentions Wolfhound et al, this was confirmed from my MacBook, and two Dragonfly-6.4 boxes. In addition, for giggles, I enabled MUUG repo, did a `sudo pkg update --repository MUUG` and a `sudo pkg upgrade --repository MUUG ca_root_nss`.</div><div><br></div><div>`sudo pkg --debug update --repository Avalon` writes out many lines, most pertinent being</div><div><br></div><div>```</div><div><div>DBG(1)[764867]> CURL> attempting to fetch from https://mirror-master.dragonflybsd.org/dports/dragonfly:6.4:x86:64/LATEST/packagesite.txz, left retry 3</div><div><br></div><div>* Couldn't find host mirror-master.dragonflybsd.org in the .netrc file; using defaults</div><div>* Hostname mirror-master.dragonflybsd.org was found in DNS cache</div><div>* Trying 199.233.90.72:443...</div><div>* Connected to mirror-master.dragonflybsd.org (199.233.90.72) port 443</div><div>* ALPN: curl offers http/1.1</div><div>* SSL certificate problem: certificate has expired</div><div>* Closing connection</div><div>DBG(1)[764867]> CURL> No mirror set url to https://mirror-master.dragonflybsd.org/dports/dragonfly:6.4:x86:64/LATEST/packagesite.txz</div></div><div>```</div><div><br></div><div>Regards,</div><div><br></div><div>Autumn</div><div><br><div><br><blockquote type="cite"><div>On May 31, 2024, at 7:40 AM, Martin Ivanov <marto1980@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div><meta http-equiv="content-type" content="text/html; charset=us-ascii"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Hello Marcin,<div>welcome to DragonFlyBSD! To fix the pkg problem:</div><div><span class="Apple-tab-span" style="white-space: pre;"> </span> 1.in<span style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;"> </span><em style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;">/usr/local/etc/pkg/repos/</em><span style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;">, copy the df-latest.conf.sample to df-latest.conf</span></div><div><span class="Apple-tab-span" style="white-space:pre"> </span> 2. <span style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;">in</span><span style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;"> </span><em style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;">/usr/local/etc/pkg/repos/df-latest.conf</em><span style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;">, disable the Avalon repository and enable the Wolfhound http repository.</span><span style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;"> </span></div><div><span style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;"> 3. </span><strong style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;">pkg install ca_root_nss</strong></div><div><span style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;"><b> 4. </b>in</span><span style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;"> </span><em style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;">/usr/local/etc/pkg/repos/df-latest.conf</em><span style="caret-color: rgb(0, 0, 0); font-family: Tahoma, sans-serif;">, enable the Avalon repository and disable Wolfhound again.</span></div><div><font face="Tahoma, sans-serif"><span style="caret-color: rgb(0, 0, 0);"><br></span></font></div><div><font face="Tahoma, sans-serif"><span style="caret-color: rgb(0, 0, 0);">Best regards,</span></font></div><div><font face="Tahoma, sans-serif"><span style="caret-color: rgb(0, 0, 0);">Martin<br></span></font><div><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On 31 May 2024, at 17:30, Marcin Cieslak <saper@saper.info> wrote:</div><br class="Apple-interchange-newline"><div><div>Hello,<br><br>I just installed DragonFlyBSD for a first time<br>yesterday and unfortunately:<br><br>1) pkg bootstrap broke pkg (as described last month<br>in https://lists.dragonflybsd.org/pipermail/users/2024-April/452255.html<br>The "Avalon" repository (whatever it is) was<br>unreachable.<br><br>2) I gave up troubleshooting pkg yesterday but today<br>the cause is certain: the certificate of https://mirror-master.dragonflybsd.org/ expired.<br>This also got reported to this list a month ago,<br>so it must be a recurring event (Let's Encrypt?)<br><br>3) Out of panic I tried to reinstall pkg, ca_root_nss<br>and other stuff out of dports only to find out that<br>for example security/openssl cannot be installed due to<br>security vulnerability.<br><br>Also many dports do not get installed because they are<br>"unmaintained", but there does not seem to be a clear<br>way to override that.<br><br>I was fighting some DNS issues (unrelated to DragonFly)<br>and I was sadly surprised that there is no DNS server<br>in the base anymore. (And I could not install bind9<br>due to security issue in the port).<br><br>Is there Kerberos in the base? I couldn't find<br>kinit/klist but some ports give me "base Heimdal"<br>as an option - is it just some leftover from FreeBSD<br>ports?<br><br>Initial installation also didn't go smoothly:<br><br>I asked the installer to encrypt /boot and the root filesystem.<br>It nicely refused to encrypt /boot but I could mark the root fs<br>as encrypted.<br><br>During customization phase it asked me for the encryption password<br>again asking for password confirmation, as if we were setting<br>the password again (not just mounting). This was confusing.<br><br>In the end, it didn't work - mountroot bailed out trying<br>to mount stuff from md0 partitions, which apparently didn't get<br>set up during the booting process.<br><br>So I had to go unencrypted.<br><br>I am sure for every problem I have mentioned there can<br>be a fix or a workaround if we go patiently through<br>the troubleshooting. It was just very frustrating<br>and I simply gave up, and I have to send this email<br>from the FreeBSD system instead :(<br><br>There was a one positive surprose though: ACPI event<br>messages are set up properly out of the box<br>(unlike FreeBSD -CURRENT I use as my daily driver).<br><br>Marcin<br></div></div></blockquote></div><br></div></div></div></div></blockquote></div><br></div></body></html>