home.social

Search

297 results for “nlnetlabs”

  1. Yay, it's working!
    Sure, in my dev environment, so 🤞

    ✅ Checking for @nlnetlabs #Unbound update
    ✅ Building the image when no pre release and not yet built
    ✅ Creating a new branch based on the new version
    ✅ Signed tagging and committing from my new #contibutor madnuttah-bot

    Took me a while and many commits. 🥳

    I like details, behold the #healthcheck in it's whole beauty in my #portainer ❤️

    #dns #dnssec #github #cd #workflow #pipeline #AutomatedBuild

    github.com/madnuttah/unbound-d

  2. Yay, it's working!
    Sure, in my dev environment, so 🤞

    ✅ Checking for @nlnetlabs #Unbound update
    ✅ Building the image when no pre release and not yet built
    ✅ Creating a new branch based on the new version
    ✅ Signed tagging and committing from my new #contibutor madnuttah-bot

    Took me a while and many commits. 🥳

    I like details, behold the #healthcheck in it's whole beauty in my #portainer ❤️

    #dns #dnssec #github #cd #workflow #pipeline #AutomatedBuild

    github.com/madnuttah/unbound-d

  3. Yay, it's working!
    Sure, in my dev environment, so 🤞

    ✅ Checking for @nlnetlabs #Unbound update
    ✅ Building the image when no pre release and not yet built
    ✅ Creating a new branch based on the new version
    ✅ Signed tagging and committing from my new #contibutor madnuttah-bot

    Took me a while and many commits. 🥳

    I like details, behold the #healthcheck in it's whole beauty in my #portainer ❤️

    #dns #dnssec #github #cd #workflow #pipeline #AutomatedBuild

    github.com/madnuttah/unbound-d

  4. Onderzoekers ontdekken ernstige kwetsbaarheden in veelgebruikte radiocommunicatie… of… “in 5 stappen van Vermoeden naar Volkskrant.

    1️⃣ 💶 🇪🇺 NextGen Internet ngi.eu/

    2️⃣ 💡🇳🇱 @nlnetlabs nlnet.nl/project/TETRA-crypto/

    3️⃣ 🕵️‍♂️🔬TETRA:BURST by midnightblue.nl/tetraburst

    4️⃣ 🎓 @bjacobs: “oude meuk” volkskrant.nl/cs-b8f7034a

    5️⃣ 🫣 ETSI: niets aan de hand doorlopen allemaal!

    💪👌🫶🏽: onderzoekers Midnight Blue: Jos Wetzels, Carlo Meijer & Wouter Bokslag

    #c2000 #tetra #backdoor #encryption

  5. I was also involved in bringing the #CyberResilienceAct to #FOSDEM this year:

    fosdem.org/2023/schedule/event

    First, introductory lightning talks by the @EU_Commission introducing the audience to the proposals for a CRA and new #ProductLiabilityDirective. I'll share a @nlnetlabs perspective on the CRA.

    This introduction is then followed by a panel led by Red Hat's @romdalf
    (w/ @gijs and other great panelists) to hear different perspectives on the proposals.

    Looking forward to it!

  6. Awesome to see the switchover from #DNSSEC records signed by the old key to those signed by the new key. #KeyRoll #KSKRoll #KSKRollover (See live(ish) graph at nlnetlabs.nl )

  7. My favorite moment from last weeks #ripe92 in Edinburgh. My two colleagues and friends Peter ‚Pete‘ Eckel and @cstrotm having breakfast in the lovely apartment we had rented. Laptops in front of them and in the midst of a discussion on some DNS stuff. 🥰

    Later that day we presented the PoC we at @sys4 had prepared for our working group along with @iscdotorg , @nlnetlabs , @knotfeed, @PowerDNS and DeNIC.

  8. My favorite moment from last weeks #ripe92 in Edinburgh. My two colleagues and friends Peter ‚Pete‘ Eckel and @cstrotm having breakfast in the lovely apartment we had rented. Laptops in front of them and in the midst of a discussion on some DNS stuff. 🥰

    Later that day we presented the PoC we at @sys4 had prepared for our working group along with @iscdotorg , @nlnetlabs , @knotfeed, @PowerDNS and DeNIC.

  9. My favorite moment from last weeks #ripe92 in Edinburgh. My two colleagues and friends Peter ‚Pete‘ Eckel and @cstrotm having breakfast in the lovely apartment we had rented. Laptops in front of them and in the midst of a discussion on some DNS stuff. 🥰

    Later that day we presented the PoC we at @sys4 had prepared for our working group along with @iscdotorg , @nlnetlabs , @knotfeed, @PowerDNS and DeNIC.

  10. My favorite moment from last weeks #ripe92 in Edinburgh. My two colleagues and friends Peter ‚Pete‘ Eckel and @cstrotm having breakfast in the lovely apartment we had rented. Laptops in front of them and in the midst of a discussion on some DNS stuff. 🥰

    Later that day we presented the PoC we at @sys4 had prepared for our working group along with @iscdotorg , @nlnetlabs , @knotfeed, @PowerDNS and DeNIC.

  11. My favorite moment from last weeks #ripe92 in Edinburgh. My two colleagues and friends Peter ‚Pete‘ Eckel and @cstrotm having breakfast in the lovely apartment we had rented. Laptops in front of them and in the midst of a discussion on some DNS stuff. 🥰

    Later that day we presented the PoC we at @sys4 had prepared for our working group along with @iscdotorg , @nlnetlabs , @knotfeed, @PowerDNS and DeNIC.

  12. @pemensik when a security researcher submits a report, only we can determine if this is a legitimate vulnerability and if so, whether it’s worthy of a CVE process. We can’t outsource this evaluation. That defeats the purpose of responsible disclosure.

    Sharing embargoed information under NDA with organizations we have a business relationship with has been part of paid support services for as long as I can remember. This is a perfectly normal part of industry practices.

    nlnetlabs.nl/security-report/

    #DNS #OpenSource #FOSS

  13. @pemensik when a security researcher submits a report, only we can determine if this is a legitimate vulnerability and if so, whether it’s worthy of a CVE process. We can’t outsource this evaluation. That defeats the purpose of responsible disclosure.

    Sharing embargoed information under NDA with organizations we have a business relationship with has been part of paid support services for as long as I can remember. This is a perfectly normal part of industry practices.

    nlnetlabs.nl/security-report/

    #DNS #OpenSource #FOSS

  14. @pemensik when a security researcher submits a report, only we can determine if this is a legitimate vulnerability and if so, whether it’s worthy of a CVE process. We can’t outsource this evaluation. That defeats the purpose of responsible disclosure.

    Sharing embargoed information under NDA with organizations we have a business relationship with has been part of paid support services for as long as I can remember. This is a perfectly normal part of industry practices.

    nlnetlabs.nl/security-report/

  15. @pemensik when a security researcher submits a report, only we can determine if this is a legitimate vulnerability and if so, whether it’s worthy of a CVE process. We can’t outsource this evaluation. That defeats the purpose of responsible disclosure.

    Sharing embargoed information under NDA with organizations we have a business relationship with has been part of paid support services for as long as I can remember. This is a perfectly normal part of industry practices.

    nlnetlabs.nl/security-report/

    #DNS #OpenSource #FOSS

  16. @pemensik when a security researcher submits a report, only we can determine if this is a legitimate vulnerability and if so, whether it’s worthy of a CVE process. We can’t outsource this evaluation. That defeats the purpose of responsible disclosure.

    Sharing embargoed information under NDA with organizations we have a business relationship with has been part of paid support services for as long as I can remember. This is a perfectly normal part of industry practices.

    nlnetlabs.nl/security-report/

    #DNS #OpenSource #FOSS

  17. @bortzmeyer As the manager of the Cascade project, I feel it's important to provide some context and nuance to the terms "alpha”, “beta" and “production ready”. This applies especially to software that is intended to run in critical infrastructure, with possible grave consequences when there is a failure.

    While @nlnetlabs is building Cascade on 25 years of experience in DNS and software architecture, operators should not take our work for granted based on that.

    This is our plan.

    We have frozen the feature set Cascade has now, for the beta release. That means a DNSSEC signer with HSM support, IXFR in and out with TSIG, deterministic incremental signing, review hooks, and monitoring endpoints.

    We will mark this release as “beta” in the coming weeks, but read this as whatever you feel is appropriate given the context I gave. That being said: we will dogfood this release. Starting this summer, operators can put Cascade in their testing environments to put it through their wringers, so we can iron out bugs and fix corner cases.

    Over the coming months, our aim to have operators build the confidence to start deploying Cascade in production, with the expectation that we'll see real-world Cascade deployments towards the end of this year.

    #DNS #DNSSEC #OARC46 #LoveDNS @dnsoarc

  18. @bortzmeyer As the manager of the Cascade project, I feel it's important to provide some context and nuance to the terms "alpha”, “beta" and “production ready”. This applies especially to software that is intended to run in critical infrastructure, with possible grave consequences when there is a failure.

    While @nlnetlabs is building Cascade on 25 years of experience in DNS and software architecture, operators should not take our work for granted based on that.

    This is our plan.

    We have frozen the feature set Cascade has now, for the beta release. That means a DNSSEC signer with HSM support, IXFR in and out with TSIG, deterministic incremental signing, review hooks, and monitoring endpoints.

    We will mark this release as “beta” in the coming weeks, but read this as whatever you feel is appropriate given the context I gave. That being said: we will dogfood this release. Starting this summer, operators can put Cascade in their testing environments to put it through their wringers, so we can iron out bugs and fix corner cases.

    Over the coming months, our aim to have operators build the confidence to start deploying Cascade in production, with the expectation that we'll see real-world Cascade deployments towards the end of this year.

    #DNS #DNSSEC #OARC46 #LoveDNS @dnsoarc

  19. @bortzmeyer As the manager of the Cascade project, I feel it's important to provide some context and nuance to the terms "alpha”, “beta" and “production ready”. This applies especially to software that is intended to run in critical infrastructure, with possible grave consequences when there is a failure.

    While @nlnetlabs is building Cascade on 25 years of experience in DNS and software architecture, operators should not take our work for granted based on that.

    This is our plan.

    We have frozen the feature set Cascade has now, for the beta release. That means a DNSSEC signer with HSM support, IXFR in and out with TSIG, deterministic incremental signing, review hooks, and monitoring endpoints.

    We will mark this release as “beta” in the coming weeks, but read this as whatever you feel is appropriate given the context I gave. That being said: we will dogfood this release. Starting this summer, operators can put Cascade in their testing environments to put it through their wringers, so we can iron out bugs and fix corner cases.

    Over the coming months, our aim to have operators build the confidence to start deploying Cascade in production, with the expectation that we'll see real-world Cascade deployments towards the end of this year.

    @dnsoarc

  20. @bortzmeyer As the manager of the Cascade project, I feel it's important to provide some context and nuance to the terms "alpha”, “beta" and “production ready”. This applies especially to software that is intended to run in critical infrastructure, with possible grave consequences when there is a failure.

    While @nlnetlabs is building Cascade on 25 years of experience in DNS and software architecture, operators should not take our work for granted based on that.

    This is our plan.

    We have frozen the feature set Cascade has now, for the beta release. That means a DNSSEC signer with HSM support, IXFR in and out with TSIG, deterministic incremental signing, review hooks, and monitoring endpoints.

    We will mark this release as “beta” in the coming weeks, but read this as whatever you feel is appropriate given the context I gave. That being said: we will dogfood this release. Starting this summer, operators can put Cascade in their testing environments to put it through their wringers, so we can iron out bugs and fix corner cases.

    Over the coming months, our aim to have operators build the confidence to start deploying Cascade in production, with the expectation that we'll see real-world Cascade deployments towards the end of this year.

    #DNS #DNSSEC #OARC46 #LoveDNS @dnsoarc

  21. @bortzmeyer As the manager of the Cascade project, I feel it's important to provide some context and nuance to the terms "alpha”, “beta" and “production ready”. This applies especially to software that is intended to run in critical infrastructure, with possible grave consequences when there is a failure.

    While @nlnetlabs is building Cascade on 25 years of experience in DNS and software architecture, operators should not take our work for granted based on that.

    This is our plan.

    We have frozen the feature set Cascade has now, for the beta release. That means a DNSSEC signer with HSM support, IXFR in and out with TSIG, deterministic incremental signing, review hooks, and monitoring endpoints.

    We will mark this release as “beta” in the coming weeks, but read this as whatever you feel is appropriate given the context I gave. That being said: we will dogfood this release. Starting this summer, operators can put Cascade in their testing environments to put it through their wringers, so we can iron out bugs and fix corner cases.

    Over the coming months, our aim to have operators build the confidence to start deploying Cascade in production, with the expectation that we'll see real-world Cascade deployments towards the end of this year.

    #DNS #DNSSEC #OARC46 #LoveDNS @dnsoarc

  22. @drscriptt @jhaas I remember launching #RPKI in 2011. It took years of publishing ROAs, learning from mistakes and fixing bad quality ROAs before the operator community got to the point where they felt comfortable dropping invalid routes.

    ASPA will be the same, although perhaps a bit quicker because of the huge installed base of (ASPA capable) validators: rov-measurements.nlnetlabs.net

  23. 🚀 Behold! Another "innovative" #scripting #language swoops in to save #Rust from... itself? #Roto promises to be both simple and fast, which is programmer-speak for "good luck debugging!" 🎉🔧 Oh, and don't forget to subscribe to the #newsletter for more groundbreaking insights on filtering route announcements. 😂📬
    blog.nlnetlabs.nl/introducing- #innovative #programming #humor #HackerNews #ngated

  24. Nice – :MW: MOULE WORLD is in the Phonebook of the Internet, listed 5 websites before the website of the Moulin Rouge!

    If there's any DNS errors, you can try visiting a website by its IPv4 address.

    nlnetlabs.nl/news/2025/Apr/01/

    #MouleWorld #PhoneBookOfTheInternet #NLnet

  25. Het is weer donatie-tijd. Is er iemand bekend met ANBI stichtingen en/of verenigingen die zich richt op Open Source/Libre software? Ik weet van @waag maar die hebben een iets bredere focus. En we hebben natuurlijk NLnet, dat erg on-topic is.

    (Dit n.a.v. de fundraiser van Framasoft, waar ze in hun formulier Fransen eraan herinneren dat hun gift aftrekbaar is. social.tchncs.de/@Blort/111631)

    CC @nlnetlabs @Piratenpartij @publicspaces
    #donaties #ANBI #belastingdienst #OpenSource #OpenSourceSoftware

  26. Het is weer donatie-tijd. Is er iemand bekend met ANBI stichtingen en/of verenigingen die zich richt op Open Source/Libre software? Ik weet van @waag maar die hebben een iets bredere focus. En we hebben natuurlijk NLnet, dat erg on-topic is.

    (Dit n.a.v. de fundraiser van Framasoft, waar ze in hun formulier Fransen eraan herinneren dat hun gift aftrekbaar is. social.tchncs.de/@Blort/111631)

    CC @nlnetlabs @Piratenpartij @publicspaces
    #donaties #ANBI #belastingdienst #OpenSource #OpenSourceSoftware

  27. Het is weer donatie-tijd. Is er iemand bekend met ANBI stichtingen en/of verenigingen die zich richt op Open Source/Libre software? Ik weet van @waag maar die hebben een iets bredere focus. En we hebben natuurlijk NLnet, dat erg on-topic is.

    (Dit n.a.v. de fundraiser van Framasoft, waar ze in hun formulier Fransen eraan herinneren dat hun gift aftrekbaar is. social.tchncs.de/@Blort/111631)

    CC @nlnetlabs @Piratenpartij @publicspaces
    #donaties #ANBI #belastingdienst #OpenSource #OpenSourceSoftware

  28. Het is weer donatie-tijd. Is er iemand bekend met ANBI stichtingen en/of verenigingen die zich richt op Open Source/Libre software? Ik weet van @waag maar die hebben een iets bredere focus. En we hebben natuurlijk NLnet, dat erg on-topic is.

    (Dit n.a.v. de fundraiser van Framasoft, waar ze in hun formulier Fransen eraan herinneren dat hun gift aftrekbaar is. social.tchncs.de/@Blort/111631)

    CC @nlnetlabs @Piratenpartij @publicspaces
    #donaties #ANBI #belastingdienst #OpenSource #OpenSourceSoftware

  29. Het is weer donatie-tijd. Is er iemand bekend met ANBI stichtingen en/of verenigingen die zich richt op Open Source/Libre software? Ik weet van @waag maar die hebben een iets bredere focus. En we hebben natuurlijk NLnet, dat erg on-topic is.

    (Dit n.a.v. de fundraiser van Framasoft, waar ze in hun formulier Fransen eraan herinneren dat hun gift aftrekbaar is. social.tchncs.de/@Blort/111631)

    CC @nlnetlabs @Piratenpartij @publicspaces
    #donaties #ANBI #belastingdienst #OpenSource #OpenSourceSoftware

  30. [#FridayReads] Did you know the Netherlands 🇳🇱 was the first European country connected to the internet?

    Read this great article by @nemokennislink about the history of internet in the Netherlands and Dutch internet pioneers, including our CEO Erik Huizer @Milkshake and the major role he played in the protocol wars 👉 nemokennislink.nl/publicaties/

    @SURF @ietf @nlnetlabs @SIDN @SIDNlabs

    #Historyoftheinternet #internethistory #internet #internetpioneers #Netherlands