Mathstodon

2 posts2 participants0 posts today

ティージェーグレェI submitted a Pull Request to update MacPorts' rpki-client to 9.5 here: <a href="https://github.com/macports/macports-ports/pull/28128" rel="nofollow noopener noreferrer" target="_blank">https://github.com/macports/macports-ports/pull/28128</a> GitHub Continuous Integration checks passed! Update: Or at least I thought they did? Now seeing this error: "Creating port index in /Users/runner/work/macports-ports1597/macports-ports1597/ports Adding port net/rpki-client signal interp lost ports/.github/workflows/bootstrap.sh: line 150: 2047 Abort trap: 6 portindex -e Error: Process completed with exit code 134." o.O From: <a href="https://github.com/artkiver/macports-ports1597/actions/runs/14437970476" rel="nofollow noopener noreferrer" target="_blank">https://github.com/artkiver/macports-ports1597/actions/runs/14437970476</a> Even though previously in the GitHub UI, it showed all three checks as green. wtfh? I mean, I hate GitHub and have less than no reason to trust it, but that's a new one, even for me. If I check: <a href="https://github.com/macports/macports-ports/pull/28128/checks" rel="nofollow noopener noreferrer" target="_blank">https://github.com/macports/macports-ports/pull/28128/checks</a> All is green there too. I am so confused. Regardless, it's up to someone else with commit access to merge it. Meanwhile, still no assistance regarding my request for help on the MacPorts' patches for OpenSSH 10.0p1/2 for ssh-agent.c and sshd-session.c, but someone else did open another Trac issue regarding OpenSSH's logging (or lack thereof) here: <a href="https://trac.macports.org/ticket/72345" rel="nofollow noopener noreferrer" target="_blank">https://trac.macports.org/ticket/72345</a> Though, they also observe the same behavior with the Apple shipped version, so they pontificate if it may be an issue upstream? Ya think? Sometimes, I think folks vastly overestimate what "maintainer" means or how much I might be using some of this software or what they expect me to do about it just because it is "assigned" to me. For example: I basically do not run sshd on any macOS systems, since I only have Apple laptops which sleep a lot and are absolutely awful as anything that should be a server running daemonized software. Did these folks not notice that Apple themselves discontinued their XServe hardware line circa 2004? Or that even their "OS X Server" product was discontinued from the App Store in 2022? I guess they missed the memos, couldn't read the room or writing on the wall? But then, they observed this in macOS Monterey, which itself is from 2021, so maybe they just prefer livin in the past? I have no idea. I am not even sure how to meaningfully reply to that Trac issue. <a href="https://snac.bsd.cafe?t=rpki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> <a href="https://snac.bsd.cafe?t=rpkiーclient" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rpkiーclient</a> <a href="https://snac.bsd.cafe?t=macports" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MacPorts</a> <a href="https://snac.bsd.cafe?t=macos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macOS</a> <a href="https://snac.bsd.cafe?t=bgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BGP</a> <a href="https://snac.bsd.cafe?t=openbgpd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBGPD</a> <a href="https://snac.bsd.cafe?t=opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a>

Peter N. M. Hansteenrpki-client 9.5 released <a href="https://www.undeadly.org/cgi?action=article;sid=20250412123402" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.undeadly.org/cgi?action=article;sid=20250412123402</a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://mastodon.social/tags/rpkiclient" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rpkiclient</a> <a href="https://mastodon.social/tags/rpki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rpki</a> <a href="https://mastodon.social/tags/bgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bgp</a> <a href="https://mastodon.social/tags/pki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pki</a> <a href="https://mastodon.social/tags/crypto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#crypto</a> <a href="https://mastodon.social/tags/cryptography" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cryptography</a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://mastodon.social/tags/routing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#routing</a> <a href="https://mastodon.social/tags/bgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bgp</a> <a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a> <a href="https://mastodon.social/tags/freesoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freesoftware</a> <a href="https://mastodon.social/tags/libresoftware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libresoftware</a>

John KristoffDid you know chrony, the <a href="https://infosec.exchange/tags/NTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NTP</a> implementation, sets up an administrative listener on the loopback interface using UDP/323 by default?Unfortunately in the <a href="https://infosec.exchange/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> rpki-rtr has TCP/323 registered with IANA (see IETF RFC 6810). UDP/323 is reserved. Reserving a transport that is unused by the assigned application is common practice these days.chrony's choice can probably be chalked up to a historical accident since it came first and presumably picked 323 because it "looked" like 123 and was then unassigned.Chrony should probably change their default imo, but maybe it's too late or not worth it now?

NLnet LabsWe are pleased to announce the latest release of Routinator, version 0.14.2 ‘Roll Initiative!’ This of our <a href="https://fosstodon.org/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> validator fixes an issue in the bundled UI that caused it to retrieve data from our own test instance rather than the actual Routinator instance. Users of the bundled UI should upgrade. <a href="https://github.com/NLnetLabs/routinator/releases/tag/v0.14.2" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/NLnetLabs/routinator/releases/tag/v0.14.2</a>

Solid TechIs Your Internet Service Provider (ISP) Secure? Test It Now!<a href="https://www.byteswifts.com/2025/02/is-your-isp-secure-test-it-now.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.byteswifts.com/2025/02/is-your-isp-secure-test-it-now.html</a><a href="https://mastodon.social/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CyberSecurity</a> <a href="https://mastodon.social/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ISP</a> <a href="https://mastodon.social/tags/BGPHijacking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BGPHijacking</a> <a href="https://mastodon.social/tags/DataProtection" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DataProtection</a> <a href="https://mastodon.social/tags/OnlineSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OnlineSecurity</a> <a href="https://mastodon.social/tags/TechNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechNews</a> <a href="https://mastodon.social/tags/CyberThreats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CyberThreats</a> <a href="https://mastodon.social/tags/InternetPrivacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InternetPrivacy</a> <a href="https://mastodon.social/tags/SecureInternet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecureInternet</a> <a href="https://mastodon.social/tags/NetworkSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NetworkSecurity</a> <a href="https://mastodon.social/tags/CyberAwareness" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CyberAwareness</a> <a href="https://mastodon.social/tags/Hacking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hacking</a> <a href="https://mastodon.social/tags/TechTips" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechTips</a> <a href="https://mastodon.social/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cloudflare</a> <a href="https://mastodon.social/tags/BGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BGP</a> <a href="https://mastodon.social/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> <a href="https://mastodon.social/tags/ITSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ITSecurity</a> <a href="https://mastodon.social/tags/CyberAttack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CyberAttack</a> <a href="https://mastodon.social/tags/InfoSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InfoSec</a> <a href="https://mastodon.social/tags/CyberDefense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CyberDefense</a> <a href="https://mastodon.social/tags/VPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VPN</a> <a href="https://mastodon.social/tags/OnlinePrivacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OnlinePrivacy</a> <a href="https://mastodon.social/tags/SecurityTips" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecurityTips</a> <a href="https://mastodon.social/tags/CyberSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CyberSec</a> <a href="https://mastodon.social/tags/TechUpdates" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechUpdates</a> <a href="https://mastodon.social/tags/DigitalSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DigitalSecurity</a> <a href="https://mastodon.social/tags/Hackers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hackers</a> <a href="https://mastodon.social/tags/ITSupport" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ITSupport</a> <a href="https://mastodon.social/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Networking</a> <a href="https://mastodon.social/tags/CyberProtection" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CyberProtection</a> <a href="https://mastodon.social/tags/SecureYourData" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecureYourData</a> <a href="https://mastodon.social/tags/DigitalSafety" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DigitalSafety</a> <a href="https://mastodon.social/tags/Tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tech</a>

Dan YorkThis is great news! I have long been a huge of Internet.nl as a test site for compliance with the latest standards- and now they have added <a href="https://mastodon.social/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> into their scoring. (The RPKI test was there for the last 2 years, but didn’t count toward the score - now it does!) This is a way to hopefully get people paying more attention to <a href="https://mastodon.social/tags/RoutingSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RoutingSecurity</a> and <a href="https://mastodon.social/tags/MANRS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MANRS</a> From: <a href="https://mastodon.nl/@internet_nl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@internet_nl</a> <a href="https://mastodon.nl/@internet_nl/113906271350500646" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://mastodon.nl/@internet_nl/113906271350500646</a>

Internet.nl<a href="https://noc.social/@namedbird" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@namedbird</a> <a href="https://mastodon.social/@GuidoKostons" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@GuidoKostons</a> Goed dat je het gefixt hebt! Wel jammer dat je registrar niet helemaal bij de tijd is. Voor andere *Europese* <a href="https://mastodon.nl/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNS</a> providers die -voor zover wij weten- allemaal <a href="https://mastodon.nl/tags/DNSSEC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNSSEC</a> doen zie trouwens: <a href="https://european-alternatives.eu/category/managed-dns-providers" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://european-alternatives.eu/category/managed-dns-providers</a>deSEC is zelfs een voor gebruikers kosteloze dienst: <a href="https://desec.io/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://desec.io/</a>Welke <a href="https://mastodon.nl/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> problemen zie je trouwens bij de mail forwarding via Cloudflare?

Named Bird<a href="https://mastodon.social/@GuidoKostons" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@GuidoKostons</a> <a href="https://mastodon.nl/@internet_nl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@internet_nl</a> Ik ook! Heb <a href="https://noc.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> aan en de webserver beveiligd op mijn VPSje. Om DNSSEC werkend te krijgen moest ik cloudflare nameservers gebruiken, aangezien mijn registrar dat niet aan heeft staan op hun eigen servers. Toen direct mail forwarding aangezet en haal daar nu ook ~95% op. (geen 100 wegens <a href="https://noc.social/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> problemen bij <a href="https://noc.social/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cloudflare</a>.)

Clement CavadoreNous venons d'implémenter un filtrage basé sur "Autonomous System Provider Authorization" (ASPA) sur un des RS de Lillix (RS2).Etant donné que ASPA n'est pas encore normalisé, on va attendre que ca soit fait pour l'implémenter sur RS1. <a href="https://masto.hivane.net/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> infos sur le blog d'<a href="https://hostux.social/@alarig" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@alarig</a> (qui l'a implémenté chez Lillix): <a href="https://www.swordarmor.fr/securisation-du-routage-bgp-en-utilisant-aspa-avec-routinator-et-bird-cas-de-breizh-ix.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.swordarmor.fr/securisation-du-routage-bgp-en-utilisant-aspa-avec-routinator-et-bird-cas-de-breizh-ix.html</a>

NLnet LabsRoutinator offered support for <a href="https://fosstodon.org/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> Autonomous System Provider Authorization (ASPA) as an experimental feature for a number of years already. Standardization has now progressed far enough in the <a href="https://fosstodon.org/tags/IETF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IETF</a> that we feel comfortable making <a href="https://fosstodon.org/tags/ASPA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ASPA</a> a core feature in Routinator 0.14.1. <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://fosstodon.org/tags/OpenStandards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenStandards</a> <a href="https://github.com/NLnetLabs/routinator/releases/tag/v0.14.1" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/NLnetLabs/routinator/releases/tag/v0.14.1</a>

NLnet LabsWe just released Routinator 0.14.1, fixing CVE-2025-0638, where non-ASCII characters in the file names listed in an <a href="https://fosstodon.org/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> manifest lead to a crash of Routinator: <a href="https://nlnetlabs.nl/downloads/routinator/CVE-2025-0638.txt" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://nlnetlabs.nl/downloads/routinator/CVE-2025-0638.txt</a>You should also be aware of CVE-2024-12084, fixing a heap-based buffer overflow flaw was found in the rsync daemon: <a href="https://nvd.nist.gov/vuln/detail/cve-2024-12084" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://nvd.nist.gov/vuln/detail/cve-2024-12084</a>Please make sure you update both Routinator and rsync. Lastly, because gzip is re-enabled, you’ll save up to 50% bandwidth. <a href="https://nlnetlabs.nl/news/2025/Jan/22/routinator-0.14.1-released/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://nlnetlabs.nl/news/2025/Jan/22/routinator-0.14.1-released/</a>

NLnet Labs“… require contracted providers of Internet services to agencies to adopt and deploy Internet routing security technologies, including publishing Route Origin Authorizations and performing Route Origin Validation filtering."In light of this Executive Order; if you need <a href="https://fosstodon.org/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> solutions that are continually developed, have a proven track record, are trusted by the world’s largest operators and are supported with a service-level agreement, we're here for you. <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a><a href="https://www.whitehouse.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.whitehouse.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/</a>

Bryan Steele :flan_beard:History/backstory in the OpenBSD commit for rpki-client(8), from Job Snijders.<a href="https://marc.info/?l=openbsd-cvs&m=173707299408526&w=2" rel="nofollow noopener noreferrer" target="_blank">https://marc.info/?l=openbsd-cvs&m=173707299408526&w=2</a><a href="https://bsd.network/tags/BGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BGP</a> <a href="https://bsd.network/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a>

Bryan Steele :flan_beard:The ARIN <a href="https://bsd.network/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> TAL (Trust Anchor Locator) has been updated to include a BSD-like disclaimer comment, making it more widely available.<a href="https://www.arin.net/announcements/20250116-tal/" rel="nofollow noopener noreferrer" target="_blank">https://www.arin.net/announcements/20250116-tal/</a>Heads up from Job Snijders on openbsd tech@:<a href="https://marc.info/?l=openbsd-tech&m=173705588431903&w=2" rel="nofollow noopener noreferrer" target="_blank">https://marc.info/?l=openbsd-tech&m=173705588431903&w=2</a>

Jan SchaumannWhoof, this "Executive Order on Strengthening and Promoting Innovation in the Nation’s Cybersecurity" is a lot of words:<a href="https://www.whitehouse.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.whitehouse.gov/briefing-room/presidential-actions/2025/01/16/executive-order-on-strengthening-and-promoting-innovation-in-the-nations-cybersecurity/</a>Notable:"Within 120 days, publish <a href="https://mstdn.social/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> Route Origin Authorizations...""Within 180 days, enable encrypted DNS protocols...""Agencies shall implement PQC key establishment or hybrid key establishment including a PQC algorithm as soon as practicable...""Within 270 days, establish a program to use advanced AI models for cyber defense."

John Kristoff<a href="https://infosec.exchange/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a>'s 2024 Year in Review by <a href="https://bsd.network/@job" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@job</a> <a href="https://mailarchive.ietf.org/arch/msg/sidrops/wI_PqEMsScRh1-jYl8XYPDI-3qE/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://mailarchive.ietf.org/arch/msg/sidrops/wI_PqEMsScRh1-jYl8XYPDI-3qE/</a>

John Kristoff<a href="https://mstdn.social/@jschauma" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jschauma</a> The thing I'd be especially concerned about are <a href="https://infosec.exchange/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> publication points.

Peter N. M. Hansteenrpki-client 9.4 released <a href="https://www.undeadly.org/cgi?action=article;sid=20250108100744" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.undeadly.org/cgi?action=article;sid=20250108100744</a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://mastodon.social/tags/rpki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rpki</a>-client <a href="https://mastodon.social/tags/rpki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rpki</a> <a href="https://mastodon.social/tags/pki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pki</a> <a href="https://mastodon.social/tags/routing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#routing</a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#networking</a>

ティージェーグレェI submitted a Pull Request to update MacPorts' rpki-client to 9.4 here: <a href="https://github.com/macports/macports-ports/pull/27334" rel="nofollow noopener noreferrer" target="_blank">https://github.com/macports/macports-ports/pull/27334</a> The GitHub Continuous Integration checks passed OK. It's up to someone else with commit access to merge it. Also, I noticed on <a href="https://rpki-client.org" rel="nofollow noopener noreferrer" target="_blank">https://rpki-client.org</a> that it still references 9.3, even though the URL linked to by the "rpki-client 9.3" text is the release announcement for 9.4. I'm prepping a submission for undeadly.org as well, but I thought I would let you know about that version number typo on the website in the meantime. Thank you for the continued improvements! <a href="https://snac.bsd.cafe?t=rpki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> <a href="https://snac.bsd.cafe?t=openbgpd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBGPD</a> <a href="https://snac.bsd.cafe?t=openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenBSD</a> <a href="https://snac.bsd.cafe?t=macports" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MacPorts</a> <a href="https://snac.bsd.cafe?t=rpkiclient" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rpkiclient</a> <a href="https://snac.bsd.cafe?t=opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> <a href="https://snac.bsd.cafe?t=routing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Routing</a> <a href="https://snac.bsd.cafe?t=bgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BGP</a>

Vesna ManojlovićToday <a href="https://social.v.st/tags/Day3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Day3</a> at <a href="https://social.v.st/tags/38C3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#38C3</a> Stage <a href="https://social.v.st/tags/YELL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#YELL</a> 14:42 :: we will talk about <a href="https://social.v.st/tags/RIPE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RIPE</a> database, <a href="https://social.v.st/tags/whois" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#whois</a> protocol, <a href="https://social.v.st/tags/BGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BGP</a> security, <a href="https://social.v.st/tags/ASN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ASN</a> <a href="https://social.v.st/tags/policy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#policy</a> , <a href="https://social.v.st/tags/routing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#routing</a> <a href="https://social.v.st/tags/registry" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#registry</a> , <a href="https://social.v.st/tags/RPSL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPSL</a> , <a href="https://social.v.st/tags/RPKI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RPKI</a> , & other <a href="https://social.v.st/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Internet</a> <a href="https://social.v.st/tags/infrastructure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#infrastructure</a> topics (with thanks to <a href="https://social.v.st/tags/xkcd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xkcd</a> who has an illustration for every occasion) <a href="https://events.ccc.de/congress/2024/hub/en/event/the-whois-protocol-for-internet-routing-policy-or-how-plaintext-retrieved-over-tcp-43-ends-up-in-router-configurations/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://events.ccc.de/congress/2024/hub/en/event/the-whois-protocol-for-internet-routing-policy-or-how-plaintext-retrieved-over-tcp-43-ends-up-in-router-configurations/</a>

Recent searches

Search options

Administered by:

Server stats:

#rpki