home.social

#rpki — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rpki, aggregated by home.social.

fetched live
  1. Job Snijders (job@) has imported a new network daemon to #OpenBSD -current, not yet linked to the build.

    job@ modified src/usr.sbin/{rtrd,rtrctl}/*: Import rtrd(8), an easy-to-use RPKI-To-Router protocol implementation

    The rtrd(8) program is intended as a scalable distribution layer to deliver data produced by rpki-client(8) to clients such as bgpd(8) in multi-node/multi-vendor IXP and ISP deployments.
    A single rtrd(8) instance can concurrently serve many BGP routers and route servers.

    Many thanks to Ralph Covelli from Hurricane Electric for creating rtrd!

    OK deraadt@ claudio@

    #RPKI #BGP

  2. Job Snijders (job@) has imported a new network daemon to #OpenBSD -current, not yet linked to the build.

    job@ modified src/usr.sbin/{rtrd,rtrctl}/*: Import rtrd(8), an easy-to-use RPKI-To-Router protocol implementation

    The rtrd(8) program is intended as a scalable distribution layer to deliver data produced by rpki-client(8) to clients such as bgpd(8) in multi-node/multi-vendor IXP and ISP deployments.
    A single rtrd(8) instance can concurrently serve many BGP routers and route servers.

    Many thanks to Ralph Covelli from Hurricane Electric for creating rtrd!

    OK deraadt@ claudio@

    #RPKI #BGP

  3. Job Snijders (job@) has imported a new network daemon to #OpenBSD -current, not yet linked to the build.

    job@ modified src/usr.sbin/{rtrd,rtrctl}/*: Import rtrd(8), an easy-to-use RPKI-To-Router protocol implementation

    The rtrd(8) program is intended as a scalable distribution layer to deliver data produced by rpki-client(8) to clients such as bgpd(8) in multi-node/multi-vendor IXP and ISP deployments.
    A single rtrd(8) instance can concurrently serve many BGP routers and route servers.

    Many thanks to Ralph Covelli from Hurricane Electric for creating rtrd!

    OK deraadt@ claudio@

    #RPKI #BGP

  4. Job Snijders (job@) has imported a new network daemon to #OpenBSD -current, not yet linked to the build.

    job@ modified src/usr.sbin/{rtrd,rtrctl}/*: Import rtrd(8), an easy-to-use RPKI-To-Router protocol implementation

    The rtrd(8) program is intended as a scalable distribution layer to deliver data produced by rpki-client(8) to clients such as bgpd(8) in multi-node/multi-vendor IXP and ISP deployments.
    A single rtrd(8) instance can concurrently serve many BGP routers and route servers.

    Many thanks to Ralph Covelli from Hurricane Electric for creating rtrd!

    OK deraadt@ claudio@

    #RPKI #BGP

  5. Job Snijders (job@) has imported a new network daemon to #OpenBSD -current, not yet linked to the build.

    job@ modified src/usr.sbin/{rtrd,rtrctl}/*: Import rtrd(8), an easy-to-use RPKI-To-Router protocol implementation

    The rtrd(8) program is intended as a scalable distribution layer to deliver data produced by rpki-client(8) to clients such as bgpd(8) in multi-node/multi-vendor IXP and ISP deployments.
    A single rtrd(8) instance can concurrently serve many BGP routers and route servers.

    Many thanks to Ralph Covelli from Hurricane Electric for creating rtrd!

    OK deraadt@ claudio@

    #RPKI #BGP

  6. We recently published our LLM policy, requiring all code and documentation contributions to be authored by a human. We do accept reports of vulnerabilities found with LLMs.

    It has drawn a lot of feedback, both positive and negative. In this article we want to explain the background and motivation behind our choices.

    #OpenSource #DNS #BGP #RPKI #softwaredevelopment

    blog.nlnetlabs.nl/maintaining-

  7. We recently published our LLM policy, requiring all code and documentation contributions to be authored by a human. We do accept reports of vulnerabilities found with LLMs.

    It has drawn a lot of feedback, both positive and negative. In this article we want to explain the background and motivation behind our choices.

    #OpenSource #DNS #BGP #RPKI #softwaredevelopment

    blog.nlnetlabs.nl/maintaining-

  8. We recently published our LLM policy, requiring all code and documentation contributions to be authored by a human. We do accept reports of vulnerabilities found with LLMs.

    It has drawn a lot of feedback, both positive and negative. In this article we want to explain the background and motivation behind our choices.

    #OpenSource #DNS #BGP #RPKI #softwaredevelopment

    blog.nlnetlabs.nl/maintaining-

  9. We recently published our LLM policy, requiring all code and documentation contributions to be authored by a human. We do accept reports of vulnerabilities found with LLMs.

    It has drawn a lot of feedback, both positive and negative. In this article we want to explain the background and motivation behind our choices.

    #OpenSource #DNS #BGP #RPKI #softwaredevelopment

    blog.nlnetlabs.nl/maintaining-

  10. We recently published our LLM policy, requiring all code and documentation contributions to be authored by a human. We do accept reports of vulnerabilities found with LLMs.

    It has drawn a lot of feedback, both positive and negative. In this article we want to explain the background and motivation behind our choices.

    #OpenSource #DNS #BGP #RPKI #softwaredevelopment

    blog.nlnetlabs.nl/maintaining-

  11. We released beta7 of our #DNSSEC signer Cascade, named “Gezellig”.

    We can now read TSIG key data from a file, supporting the NSD, BIND, and Knot formats. There are various bug fixes and improvements for using Cascade with an HSM.

    Starting today Cascade is being included in the AI-assisted security scanning that has been performed on most of our other #DNS, #BGP and #RPKI projects since last year. This means even the very first production release will be very solid.

    github.com/NLnetLabs/cascade/r

  12. We released beta7 of our #DNSSEC signer Cascade, named “Gezellig”.

    We can now read TSIG key data from a file, supporting the NSD, BIND, and Knot formats. There are various bug fixes and improvements for using Cascade with an HSM.

    Starting today Cascade is being included in the AI-assisted security scanning that has been performed on most of our other #DNS, #BGP and #RPKI projects since last year. This means even the very first production release will be very solid.

    github.com/NLnetLabs/cascade/r

  13. We released beta7 of our #DNSSEC signer Cascade, named “Gezellig”.

    We can now read TSIG key data from a file, supporting the NSD, BIND, and Knot formats. There are various bug fixes and improvements for using Cascade with an HSM.

    Starting today Cascade is being included in the AI-assisted security scanning that has been performed on most of our other #DNS, #BGP and #RPKI projects since last year. This means even the very first production release will be very solid.

    github.com/NLnetLabs/cascade/r

  14. We released beta7 of our #DNSSEC signer Cascade, named “Gezellig”.

    We can now read TSIG key data from a file, supporting the NSD, BIND, and Knot formats. There are various bug fixes and improvements for using Cascade with an HSM.

    Starting today Cascade is being included in the AI-assisted security scanning that has been performed on most of our other #DNS, #BGP and #RPKI projects since last year. This means even the very first production release will be very solid.

    github.com/NLnetLabs/cascade/r

  15. We released beta7 of our #DNSSEC signer Cascade, named “Gezellig”.

    We can now read TSIG key data from a file, supporting the NSD, BIND, and Knot formats. There are various bug fixes and improvements for using Cascade with an HSM.

    Starting today Cascade is being included in the AI-assisted security scanning that has been performed on most of our other #DNS, #BGP and #RPKI projects since last year. This means even the very first production release will be very solid.

    github.com/NLnetLabs/cascade/r

  16. Without a ROA, your prefix announced from someone else's network looks exactly like your prefix announced from yours. A router has nothing to check it against.

    A ROA names which network is allowed to originate your prefix. Anyone else announcing it is then RPKI invalid, and networks filtering on validation drop them. That is the whole reason to sign.

    With isp6 it's a button on the dashboard: type your origin AS, press Add, and we publish the ROA to RIPE.

    #RPKI #BGP #IPv6

  17. Without a ROA, your prefix announced from someone else's network looks exactly like your prefix announced from yours. A router has nothing to check it against.

    A ROA names which network is allowed to originate your prefix. Anyone else announcing it is then RPKI invalid, and networks filtering on validation drop them. That is the whole reason to sign.

    With isp6 it's a button on the dashboard: type your origin AS, press Add, and we publish the ROA to RIPE.

    #RPKI #BGP #IPv6

  18. Without a ROA, your prefix announced from someone else's network looks exactly like your prefix announced from yours. A router has nothing to check it against.

    A ROA names which network is allowed to originate your prefix. Anyone else announcing it is then RPKI invalid, and networks filtering on validation drop them. That is the whole reason to sign.

    With isp6 it's a button on the dashboard: type your origin AS, press Add, and we publish the ROA to RIPE.

    #RPKI #BGP #IPv6

  19. Approximately 3.5% of ASNs seen making #BGP announcements have created RPKI #ASPA objects.

    This is a decent ramp up before the spec is even out of draft and the big iron from commercial router vendors have production code deployed for validating these (ASPA) paths from the #RPKI.

    social.bgp.tools/@newaspa/stat

  20. Approximately 3.5% of ASNs seen making #BGP announcements have created RPKI #ASPA objects.

    This is a decent ramp up before the spec is even out of draft and the big iron from commercial router vendors have production code deployed for validating these (ASPA) paths from the #RPKI.

    social.bgp.tools/@newaspa/stat

  21. Approximately 3.5% of ASNs seen making #BGP announcements have created RPKI #ASPA objects.

    This is a decent ramp up before the spec is even out of draft and the big iron from commercial router vendors have production code deployed for validating these (ASPA) paths from the #RPKI.

    social.bgp.tools/@newaspa/stat

  22. Approximately 3.5% of ASNs seen making #BGP announcements have created RPKI #ASPA objects.

    This is a decent ramp up before the spec is even out of draft and the big iron from commercial router vendors have production code deployed for validating these (ASPA) paths from the #RPKI.

    social.bgp.tools/@newaspa/stat

  23. Approximately 3.5% of ASNs seen making #BGP announcements have created RPKI #ASPA objects.

    This is a decent ramp up before the spec is even out of draft and the big iron from commercial router vendors have production code deployed for validating these (ASPA) paths from the #RPKI.

    social.bgp.tools/@newaspa/stat

  24. For future reference:

    /usr/bin/sh -c 'awk -v RS="" "/protocol static {\n\s+aspa/,/^}/" < /etc/bird-rpki/bird > /etc/bird-rpki/birdfilt'

    #rpki #bird #bgp

  25. For future reference:

    /usr/bin/sh -c 'awk -v RS="" "/protocol static {\n\s+aspa/,/^}/" < /etc/bird-rpki/bird > /etc/bird-rpki/birdfilt'

    #rpki #bird #bgp

  26. For future reference:

    /usr/bin/sh -c 'awk -v RS="" "/protocol static {\n\s+aspa/,/^}/" < /etc/bird-rpki/bird > /etc/bird-rpki/birdfilt'

    #rpki #bird #bgp

  27. For future reference:

    /usr/bin/sh -c 'awk -v RS="" "/protocol static {\n\s+aspa/,/^}/" < /etc/bird-rpki/bird > /etc/bird-rpki/birdfilt'

    #rpki #bird #bgp

  28. Can I get ASPA validation (with Debian stable packages?)
    fort-validator 1.6.6 does not seem to have it (only 1.7.0-experimental?)
    stayrtr 0.6.4 apparently doesn't either.
    What now?

    #bgp #rpki #aspa

  29. Can I get ASPA validation (with Debian stable packages?)
    fort-validator 1.6.6 does not seem to have it (only 1.7.0-experimental?)
    stayrtr 0.6.4 apparently doesn't either.
    What now?

    #bgp #rpki #aspa

  30. Can I get ASPA validation (with Debian stable packages?)
    fort-validator 1.6.6 does not seem to have it (only 1.7.0-experimental?)
    stayrtr 0.6.4 apparently doesn't either.
    What now?

    #bgp #rpki #aspa

  31. Can I get ASPA validation (with Debian stable packages?)
    fort-validator 1.6.6 does not seem to have it (only 1.7.0-experimental?)
    stayrtr 0.6.4 apparently doesn't either.
    What now?

    #bgp #rpki #aspa

  32. BGP security stack complete for AS201379: ASPA records published for upstream authorization, backed by valid RPKI ROAs and IRR objects.

    #AS201379 #BGP #RPKI #ASPA #IPv6 #RoutingSecurity #NetOps

  33. BGP security stack complete for AS201379: ASPA records published for upstream authorization, backed by valid RPKI ROAs and IRR objects.

    #AS201379 #BGP #RPKI #ASPA #IPv6 #RoutingSecurity #NetOps

  34. BGP security stack complete for AS201379: ASPA records published for upstream authorization, backed by valid RPKI ROAs and IRR objects.

    #AS201379 #BGP #RPKI #ASPA #IPv6 #RoutingSecurity #NetOps

  35. BGP security stack complete for AS201379: ASPA records published for upstream authorization, backed by valid RPKI ROAs and IRR objects.

    #AS201379 #BGP #RPKI #ASPA #IPv6 #RoutingSecurity #NetOps

  36. BGP security stack complete for AS201379: ASPA records published for upstream authorization, backed by valid RPKI ROAs and IRR objects.

    #AS201379 #BGP #RPKI #ASPA #IPv6 #RoutingSecurity #NetOps