- opensource-wg - mailman.ripe.net

Opt-in vulnerability-finding service for OSS
by Marcos Sanz 29 Oct '26

29 Oct '26

Dear all, welcome to day 4! I was planning to prepare a lightning talk about this one for yesterday's session, but didn't find the space, so here it is: This is the announcement: https://www.anthropic.com/research/launching-opt-in-vuln-finding-service-for -open-source And the participation instructions https://red.anthropic.com/oss-scanner/ Specially thought for "established projects that have a critical impact on infrastructure" Know what? THAT'S YOU! And I really think it's worth we find the issues ourselves than being flooded externally by more or less reliable vulnerability reports. Have a nice rest of RIPE meeting! Marcos

1 0

EDIC digital commons
by Marco d'Itri 28 Oct '26

28 Oct '26

This is a new initiative by some EU member states to fund free software: https://digital-commons-edic.eu/ -- ciao, Marco

1 0

Draft agenda for RIPE93
by Sasha Romijn 02 Oct '26

02 Oct '26

Hello all, Please find below the draft agenda for our upcoming meeting during RIPE93. Our slot is Wednesday, 28 October, 09:00-10:30 local time (UTC+2). We have three presentations on a wide range of subjects. We also still have a bit of space for Lightning Talks. If you’re interested in doing one, please send a mail to opensource-wg-chairs(a)ripe.net before the Tuesday of the meeting week. If you have any doubts about whether a topic would fit, or other questions, always feel free to contact us. We're looking forward to you joining us in Sofia or online. Thank you to all speakers who submitted for this session! Best regards, Marcos Sanz, Marco d'Itri and Sasha Romijn Working group co-chairs --- 1. Administrative matters - 10 minutes - Welcome - Finalise agenda - Approval of previous minutes - Chair selection results 2. "Beyond NIS2: Software Supply Chains and the Cyber Resilience Act (CRA)" by Barry O'Donovan - 25 minutes 3. "BIRD on an Open Linux Switch: Mainline Linux, switchdev and Hardware L3 Offload" by Bruno Banelli - 25 minutes 4. "Refactoring around an open source project that goes commercial" by Tomek Mrugalski and Victoria Risk - 20 minutes 5. Lightning Talks - details to come

1 0

Draft agenda for RIPE93
by Sasha Romijn 02 Oct '26

02 Oct '26

Hello all, Please find below the draft agenda for our upcoming meeting during RIPE93. Our slot is Wednesday, 28 October, 09:00-10:30 local time (UTC+2). We have three presentations on a wide range of subjects. We also still have a bit of space for Lightning Talks. If you’re interested in doing one, please send a mail to opensource-wg-chairs(a)ripe.net before the Tuesday of the meeting week. If you have any doubts about whether a topic would fit, or other questions, always feel free to contact us. We're looking forward to you joining us in Sofia or online. Thank you to all speakers who submitted for this session! Best regards, Marcos Sanz, Marco d'Itri and Sasha Romijn Working group co-chairs --- 1. Administrative matters - 10 minutes - Welcome - Finalise agenda - Approval of previous minutes - Chair selection results 2. "Beyond NIS2: Software Supply Chains and the Cyber Resilience Act (CRA)" by Barry O'Donovan - 25 minutes 3. "BIRD on an Open Linux Switch: Mainline Linux, switchdev and Hardware L3 Offload" by Bruno Banelli - 25 minutes 4. "Refactoring around an open source project that goes commercial" by Tomek Mrugalski and Victoria Risk - 20 minutes 5. Lightning Talks - details to come

1 0

Open Source WG chair selection - Call for candidates
by Marcos Sanz 15 Sep '26

15 Sep '26

Dear all, It's two months until RIPE 93, where Sasha's current term as a co-chair would regularly end. Thus, and as per the current selection process, we hereby open a call for candidates lasting three weeks and ending 14th September (23:59:59 UTC). Interested people (including the incumbent, if she'd like to run again!) should contact Marco and me off-list expressing their interest. Thanks and regards, Marcos (for all current wg co-chairs)

1 1

Last call for Open Source WG Presentations (RIPE93, Sofia, October 28st, 2026)
by Marco d'Itri 13 Sep '26

13 Sep '26

Dear Working Group members, We now invite you to submit your proposals for the Open Source Working Group session taking place during RIPE 93. The open source working group session is currently scheduled for Wednesday, 28 October, from 09:00 to 10:30 (UTC+2) Please submit your proposals as soon as possible, and definitely by September 21st, 2026. How to submit your talk: 1. Go to the RIPE 93 Call for Presentations page and click on "Submit a proposal": https://ripe93.ripe.net/present/call-for-presentations/ . 2. Follow the instructions[1] to set up an account on Pretalx. 3. Important: When filling in the submission form, please pay attention to the dropdown menu under "Track". This is where you select which working group (track) you would like to submit your talk for, hopefully "Open Source WG". Do not forget to also fill the "duration" field with the length you have in mind. In general, each talk is 15-30 minutes including Q&A (depending on how much time is needed). If you have some idea and are not sure how/if you should present something, then feel free to contact us as well at opensource-wg-chairs(a)ripe.net to discuss the idea! Remote presentations are also possible. As always, we are planning to reserve some time at the end of the WG session for lightning talks. These short (5 to 10 minutes max) updates/talks are decided on the day before the WG session on a time/space available basis. No need to submit to us anything for lightning talks at this time, but you are welcome to do so. [1] Detailed instructions on how to use Pretalx are available here: https://ripe93.ripe.net/present/how-to-submit-a-proposal/ . Thanks, Marco, Marcos and Sasha, Your Open Source WG Chairs -- ciao, Marco

1 0

Call for Open Source WG Presentations (RIPE93, Sofia, October 28st, 2026)
by Marco d'Itri 19 Aug '26

19 Aug '26

Dear Working Group members, We now invite you to submit your proposals for the Open Source Working Group session taking place during RIPE 93. The open source working group session is currently scheduled for Wednesday, 28 October, from 09:00 to 10:30 (UTC+2) Please submit your proposals as soon as possible, and definitely by September 14th, 2026. How to submit your talk: 1. Go to the RIPE 93 Call for Presentations page and click on "Submit a proposal": https://ripe93.ripe.net/present/call-for-presentations/ . 2. Follow the instructions[1] to set up an account on Pretalx. 3. Important: When filling in the submission form, please pay attention to the dropdown menu under "Track". This is where you select which working group (track) you would like to submit your talk for, hopefully "Open Source WG". Do not forget to also fill the "duration" field with the length you have in mind. In general, each talk is 15-30 minutes including Q&A (depending on how much time is needed). If you have some idea and are not sure how/if you should present something, then feel free to contact us as well at opensource-wg-chairs(a)ripe.net to discuss the idea! Remote presentations are also possible. As always, we are planning to reserve some time at the end of the WG session for lightning talks. These short (5 to 10 minutes max) updates/talks are decided on the day before the WG session on a time/space available basis. No need to submit to us anything for lightning talks at this time, but you are welcome to do so. [1] Detailed instructions on how to use Pretalx are available here: https://ripe93.ripe.net/present/how-to-submit-a-proposal/ . Thanks, Marco, Marcos and Sasha, Your Open Source WG Chairs -- ciao, Marco

1 0

Updated WG Chair Selection process
by Marcos Sanz 07 Aug '26

07 Aug '26

Dear working group, we hope you enjoyed last week's RIPE meeting and got back home safe and sound. If you paid attention to the RIPE Chair Team Update during the Community Plenary, you heard the discussion about the WG chair selection principles and the ongoing work on the document https://www.ripe.net/publications/docs/ripe-documents/other-documents/draft… (which will become the successor of RIPE-692). After carefully considering these recommendations/guidelines, and being aware that our current documented process for the open source wg (https://www.ripe.net/community/wg/active-wg/os/open-source-wg-chair-selecti…) is -among others- short of respecting mandatory chair terms, Marco, Sasha and I have reworked that documented process. You'll find the draft of that work attached. Nothing in the attachment should surprise you: terms are now observed (which drove us to introduce the concept of staggering for the sake of continuity). Additionally, we have now documented candidate requirements, which were outspoken in e-mails in the past (e.g. https://mailman.ripe.net/archives/list/opensource-wg@ripe.net/thread/RQP4FL…) but never made it to the official doc. Still, we'd like to ask you for feedback on the attached document, before we publish it on the website. We are opening hereby a comment period of 14 days, that is, until Friday, 12th June, before we move on. Thanks in advance for contributing to shape the future of the group Marcos (for all co-chairs) [1] Number of Co-Chairs: The Open Source WG will have two or three co-chairs. Terms [T1] Length of Term: Each co-chair serves a three-year term. [T2] Term Limits: A co-chair may serve multiple consecutive terms; there is no limit on reappointment, provided the selection process is followed. [T3] Staggered Terms: Terms must be staggered to ensure continuity. * With three co-chairs, no more than two terms may end in the same year. If staggering is lost due to resignation or unexpected changes, the WG may assign an adjusted term length to restore staggering. Chair Requirements A candidate for co-chair must meet the following requirements: [R1] Prior Participation and Process Knowledge: The candidate has attended multiple physical RIPE meetings before and is familiar with RIPE processes and community expectations (e.g. by having studied the RIPE guide for new working group chairs or completing the RIPE NCC Academy working group chair course). [R2] Ongoing Participation: The candidate commits to attending as many RIPE meetings as possible in person while serving as a co-chair. [R3] Attendance at the Current Selection Meeting: The candidate will attend the upcoming autumn RIPE meeting session (either physically or virtually) where the selection process occurs. Selection Process [2] Call for Co-Chair Candidates: Two months before every autumn RIPE meeting there will be a call for candidates for any co-chair position whose term ends that year. The nomination period will be 14 days. Candidates must confirm that they satisfy the Chair Requirements listed in section [R1]-[R3]. [3] New Term for an Existing Co-Chair: Should an existing co-chair whose term ends want to candidate, the incumbent should follow the same process as any other candidates. [4] No Applications: If there are no applications, the current co-chair whose term is ending will continue for the next term, provided the availability and willing to do so. [5] Only One Co-Chair Can Be Replaced Per Year: Only one co-chair position may be filled per year, regardless of the total number of co-chairs, to preserve stability and continuity. Candidate Discussion & Selection [6] If There Is One or More Applications: If there is at least one candidate (other than the incumbent): 1. The current co-chair whose term is ending and the candidate(s) will discuss among themselves who should serve the next term. 2. If consensus among them is reached before 14 days prior to the RIPE meeting, that person is appointed. 3. If no consensus is reached, this is publicly announced in the list and a selection process will take place within the WG at the RIPE meeting. Unforeseen Circumstances [7] Unexpected Resignation: If a co-chair resigns before their term expires: * The WG may appoint an interim co-chair by consensus until the next regular autumn selection process. * The interim period does not count as a full term. * When the position is formally filled at the next autumn cycle, the WG may assign an adjusted term length to preserve staggering (see rule [T3]). [8] Issues Not Covered Any issues relating to the selection, replacement, term management, or staggering of co-chairs not covered by the above rules will be decided by WG consensus during the RIPE meeting. When the WG is unable to reach consensus, the matter will be referred to the RIPE Chair (or their deputy), whose decision shall be final.

2 2

BondingShouldBeFree Open-source Network Aggregation & Redundancy Solution
by Chester A. Unal 21 May '26

21 May '26

Hello everyone. I have written an open-source network bonding solution with intent to have it become the gold standard of network bonding using MPTCP. This post includes all the details: https://forum.openwrt.org/t/bondingshouldbefree-open-source-network-aggrega… I'm looking for ISPs and any other parties interested to deploy it and give me feedback. Cheers. Chester Arinc

2 1

Open Source funding
by Pieter Lexis 20 May '26

20 May '26

Hello folks, As mentioned during the session at RIP92, there are several organizations Open Source projects can request funding from for many aspects of their development process. A few that come to mind are the NLNet Foundation[1], the Sovereign Tech Fund[2], and the GitHub Secure Open Source Fund[3]. As Barry O'Donovan said suting his talk at RIPE92 (as interpreted by my), don't be shy or scared to ask for help with asking for help with security and penetration testing. Should you know more sources of low-bureaucracy Open Source funding, don't hesitate to send a follow-up email to this mailing-list. Best regards, Pieter Lexis 1 - https://nlnet.nl/funding.html 2 - https://www.sovereign.tech/programs/fund 3 - https://github.com/open-source/github-secure-open-source-fund

1 0

Draft agenda for RIPE92
by Sasha Romijn 20 Apr '26

20 Apr '26

Hello all, Please find below the draft agenda for our upcoming meeting during RIPE92. Our slot is Wednesday, 20 May, 09:00-10:30 local time. We have a little space for Lightning Talks, and some submissions for this already. If you’re interested in doing one, please send a mail to opensource-wg-chairs(a)ripe.net <mailto:opensource-wg-chairs@ripe.net> before the Tuesday of the meeting week. If you have any doubts about whether a topic would fit, or other questions, always feel free to contact us. We're looking forward to you joining us in Edinburgh or online. Thank you to all speakers who submitted for this session! Best regards, Marcos Sanz, Marco d'Itri and Sasha Romijn Working group co-chairs --- 1. Administrative matters - 5 minutes - Welcome - Finalise agenda - Approval of previous minutes 2. "Web Application Security - an IXP Manager Perspective" by Barry O'Donovan - 20 minutes 3. "Nominet DNS Fund - how are we adapting to what we have learnt?" by Amy O'Donnell and Dave Knight - 20 minutes 4. "Developing Containerlab - an open-source success story" by Gordon Gidofalvy - 20 minutes 5. "How much of BIRD is vibecoded" by Maria Matejka - 15 minutes 6. Lightning Talks - details to come

1 0

Call for agenda items for RIPE92 in Edinburgh
by Sasha Romijn 02 Mar '26

02 Mar '26

Dear Working Group members, We invite you to submit your proposals for the Open Source Working Group session taking place during RIPE92 in Edinburgh, Scotland, and online, 18-22 May 2026. The open source working group session is currently scheduled for Wednesday, 20 May, from 09:00-10:30 (UTC+1). The deadline for proposals for our session is April 13. But we encourage you to submit your proposal earlier if possible. How to submit your talk: 1. Go to the RIPE 92 Call for Presentations page and click on "Submit a topic": https://ripe92.ripe.net/present/call-for-presentations/ . 2. Follow the instructions to set up an account on Pretalx. [1] 3. Important: When filling in the submission form, please pay attention to the dropdown menu under "Track". This is where you select "Open Source WG". Second, please fill in the "duration" field with the length you have in mind - that helps our planning. In general, each talk is 15-30 mins including Q&A (depending on how much time is needed). If you have an idea for the agenda and are not sure how/if you should do something, then feel free to contact us on opensource-wg-chairs(a)ripe.net to discuss the idea! Remote presentations are also possible. As always, we are planning to reserve some time at the end of the WG session for lightning talks. These short (5 to 10 minutes max) updates/talks are decided on the day before the WG session on a time/space available basis. No need to submit to us anything for lightning talks at this time, but you are welcome to do so. [1] Detailed instructions on how to use Pretalx are available here: https://ripe92.ripe.net/present/how-to-submit-a-talk/ Thanks, Marco, Marcos and Sasha, Your Open Source WG Chairs

1 0

Re: Launch of The Internet Ecosystem Book
by Peter Anderson 09 Feb '26

09 Feb '26

*(Apologies for cross-posting)* As a researcher, I have never come across a highly intensive and inclusive book like "The Internet Ecosystem". The book englobes the whole Internet Ecosystem with the correct information compared to misleading information from blogs/wikipedia on the Internet. This book was reviewed by Vint Cerf. I have just completed the reading, I will highly recommend it and it is nice to have a copy to keep for reference. Professor Peter Anderson Head of Research ------------------------------ *From:* Nikesh B. Simmandree <nikeshbs(a)outlook.com> *Sent:* Monday, August 18, 2025 1:35 PM *To:* alac-announce(a)icann.org <alac-announce(a)icann.org>; alac(a)icann.org < alac(a)icann.org>; at-large(a)icann.org <at-large(a)icann.org>; afri-discuss(a)icann.org <afri-discuss(a)icann.org> *Subject:* Launch of The Internet Ecosystem Book Dear Community, I am thrilled to announce the launch of my book, *The Internet Ecosystem* — a comprehensive exploration of the history, architecture, governance, and future of the Internet. This book distills decades of technological evolution — from ARPANET and packet switching, to AI, Web3, quantum networks, and beyond — into a clear, engaging narrative accessible to both technical and non-technical readers *What the Book Covers* - *The Past:* How Cold War research, ARPANET, and packet switching gave birth to the Internet we know today. - *The Present:* The intricate roles of ISPs, backbone providers, cloud infrastructure, AI, cybersecurity, and global governance shaping our daily online experiences. - *The Future:* Insights into 5G/6G, blockchain, immersive technologies, quantum security, and the Internet in 2050. With *49 detailed chapters*, the book provides a definitive yet approachable reference for students, professionals, policymakers, and curious readers alike. My mission with *The Internet Ecosystem* is to make the Internet’s complexity understandable — showing not only *how* the Internet works, but also *why* it matters and has become one of the most transformative human inventions — while sparking dialogue on how we build a secure, inclusive, and sustainable digital future. In the 21st century, understanding the Internet is not optional — it’s essential. Whether you’re a business leader, policymaker, educator, student, or everyday Internet user, this book provides the context and clarity you need to navigate the opportunities and challenges of our connected world. *Get Your Copy* *The Internet Ecosystem* is now available: https://payhip.com/b/hfvYg Thank you, Best Regards, Nikesh B. Simmandree +230-5-907-3413 nikeshbs(a)outlook.com This message and its attachments are intended only for the person or entity to which it is addressed and are strictly confidential. If you have received this in error, please delete it from any devices after having informed the sender.

2 1

Draft Minutes of RIPE 91 OSS wg meeting
by Marcos Sanz 02 Dec '25

02 Dec '25

Dear all, the draft minutes of our last wg meeting are online now https://www.ripe.net/community/wg/active-wg/os/minutes/open-source-working-g roup-minutes-ripe-91/ Thanks to Alun Davies for scribing, any errors/omissions are on the chairs: please contact us if you find any. Have a nice evening, Marcos

1 0

Call for Open Source WG Presentations (RIPE91, Bucharest, October 21st, 2025)
by Marco d'Itri 20 Oct '25

20 Oct '25

Dear Working Group members, We now invite you to submit your proposals for the Open Source Working Group session taking place during RIPE 91. From RIPE 91 onwards, all plenary and working group proposals can be submitted through the same system, Pretalx. Please submit your proposals by 25 September 2025. How to submit your talk: 1. Go to the RIPE 91 Call for Presentations page and click on "Submit a topic": https://ripe91.ripe.net/present/call-for-presentations/ . 2. Follow the instructions to set up an account on Pretalx. [1] 3. Important: When filling in the submission form, please pay attention to the dropdown menu under "Track". This is where you select which working group (track) you would like to submit your talk for. In general, each talk is 15-30 mins including Q&A (depending on how much time is needed). If you have some idea and are not sure how/if you should present something, then feel free to contact us as well to discuss the idea! Remote presentations are also possible. As always, we are planning to reserve some time at the end of the WG session for lightning talks. These short (5 to 10 minutes max) updates/talks are decided on the day before the WG session on a time/space available basis. No need to submit to us anything for lightning talks at this time, but you are welcome to do so. [1] Detailed instructions on how to use Pretalx are available here: https://ripe91.ripe.net/present/how-to-submit-a-talk/ Thanks, Marco, Marcos and Sasha, Your Open Source WG Chairs -- ciao, Marco

2 1

RIPE 91 OSS wg draft agenda online
by Marcos Sanz 11 Oct '25

11 Oct '25

Dear all, our draft agenda is now online and we hope it can convince you to join us at 9am in the morning of a Wednesday <https://ripe91.ripe.net/programme/meeting-plan/sessions/28/> https://ripe91.ripe.net/programme/meeting-plan/sessions/28/ Looking forward to meeting you all in Bucharest, Marcos

1 0

Draft minutes RIPE 90
by Marcos Sanz 10 Oct '25

10 Oct '25

Dear all, here follow the minutes of our last wg session in Lisbon: https://www.ripe.net/community/wg/active-wg/os/minutes/open-source-working-g roup-minutes-ripe-90/ Please read them and let us know about any wished corrections. Best regards and have a nice weekend, Marcos

1 0

Measuring CRA awareness across OS community
by Romain Bosc 06 Oct '25

06 Oct '25

Colleagues, Something I spotted that could be of interest to this group: FYI, the Open Source Security Foundation, LF Europe, and LF Research are fielding a survey to measure awareness about the recently adopted EU Cyber Resilience Act on a worldwide scale. The survey should take between 5 and 10 minutes, and closes at the end of this week with the goal being to publish the survey data and related report by mid-March. Link: https://www.research.net/r/MR35RMF All best Romain -- Romain Bosc Sr Public Policy & Governance Officer RIPE NCC E: rbosc(a)ripe.net

2 2

Nominet DNS Fund
by Lizzie Griffiths 03 Oct '25

03 Oct '25

Hello, Nominet have launched a fund designed to support both the innovation and maintenance of open source DNS projects. We have identified your publication/newsletter as a valuable opportunity to help us reach our intended audience of applicants. We wondered whether you would consider posting some information on our behalf please. We have included some basic information below but please do let us know if you prefer a different format or need more from us. Applications are open to The Nominet DNS Fund, an initiative designed to support both the innovation and maintenance of open source projects that are vital to the internet’s infrastructure. If you or your team are working on projects that strengthen the backbone of the web, we invite you to apply for funding. Key Details * Primary goal: Fund and improve the security, long-term sustainability, and resilience of DNS open source projects. * Focus: Open source critical infrastructure components relevant to the development, deployment, and operation of the global DNS. * Funding available: £370,000 available in this round, with a maximum of £100k per applicant. * Key dates: applications open on 17th September and will close 26th October. The Nominet DNS Fund is committed to responsible, transparent support for the open source community and welcomes applications from a diverse range of contributors. Nominet operate the UK’s national domain name registry for the millions of individuals and businesses who rely on it every single day. As a public benefit company, we run .UK for the greater good, and work with our members to help bring the benefits of the internet to all. Learn more and apply here: https://nominet.uk/nominet-<https://nominet.uk/?page_id=71982>dns-fund/<https://nominet.uk/?page_id=71982> Please feel free to share this with anyone who might be interested!

1 0

Open Source WG Chair selection - Looking for candidates
by Marcos Sanz 20 Sep '25

20 Sep '25

Dear all, it's two months until the next fall RIPE meeting - and this means it's time again for a Working Group Chair Selection. Our working group has currently 3 chairs: * Marco d'Itri (Since RIPE 90) * Sasha Romjin (Since RIPE 88) * Marcos Sanz (Since RIPE 84) None of us is currently considering stepping down as a WG chair, however we would like to hear from the community if there are any candidates willing to step up. Depending on the resonance and on the specific candidate(s), I personally (as the longest standing chair) would consider either withdrawing from further terms or standing myself for re-selection against the new candidate(s). Criteria/Expectations of a WG chair: - You have attended multiple physical RIPE meetings before (and are familiar with how RIPE works) - You will be attending most RIPE meetings while serving as a chair in person - You will attend this Fall meeting session (Physical or Virtual) For more details, see the Guide for New RIPE Working Group Chairs ( <https://www.ripe.net/publications/docs/ripe-765/> https://www.ripe.net/publications/docs/ripe-765/) or the RIPE Working Group Chair e-learning course ( <https://academy.ripe.net/course/info.php?id=16> https://academy.ripe.net/course/info.php?id=16) If you are interested in serving as a WG chair: Nomination period is until Sept 19th, 2025, 23:59 UTC. Send an email to <mailto:opensource-wg-chairs@ripe.net> opensource-wg-chairs(a)ripe.net to make us aware of your candidacy before this deadline. In the email, please include a short biography and a statement about why you are interested in this position. The day after the aforementioned deadline we will send an email to the list with all candidates, their submitted bio and with a summary of previous RIPE attendance. Then we will open a discussion thread on the list for feedback, statement of support for specific candidates and any other feedback in regard to them. In parallel, the working group chairs will conduct interviews with all candidates (and would politely ask them to make time for these calls and get back to us in a timely manner). Time is short and we need to be prepared before the meeting! Please be aware, these are not elections, but selections. The ultimate decision is taken by the remaining WG chairs as all the chairs need to work together. Marcos (for all current WG co-chairs)

1 1

Re: Interested in CRA standards for network management systems?
by Valerie Aurora 21 Jul '25

21 Jul '25

On 7/12/25 16:53, Paul Menzel wrote: > Dear Marcos, dear Valery, > Am 11.07.25 um 08:35 schrieb Marcos Sanz: >>> Am 07.07.25 um 18:15 schrieb Valerie Aurora via opensource-wg: >>>> I'm part of the team that is developing the CRA vertical standard >>>> for network management systems. >>> Excuse my ignorance, but what is CRA? >> Cyber Resilience Act. Valerie seems to be involved in this (which I admire): >> https://www.etsi.org/newsroom/press-releases/2545-etsi-leverages- global-technical-expertise-to-support-the-eu-cyber-resilience-act That's the one. :) Thanks for replying and for the compliment! > Thank you. I didn’t make the connection, that from that low a standardization progress follows. > Being ignorant about standards, I wonder what the difference between a server and switch is supposed to be, and why “network management systems” and servers should be treated differently. The short version is, "because the people who wrote the legislation thought they should be." :) More seriously, these categories are being clarified and redefined, and part of the work is using our technical expertise to define things better. They are also trying to distinguish different types and levels of risk. If someone compromises a single router, they can misroute or sniff traffic or MiM or inject garbage at that point. If someone compromises a network management system, they can order all the network devices it manages to update their config to trust and route through a malicious router, or simply go offline. Speaking of, I could still use someone with open source NMS experience interested in sitting in on a 2 hour meeting every 2 weeks for the next few months. Let me know if you are interested and I will tell you more. :) Valerie

1 0

Interested in CRA standards for network management systems?
by Valerie Aurora 12 Jul '25

12 Jul '25

Hi all, I'm part of the team that is developing the CRA vertical standard for network management systems. One thing we would find really valuable is having an expert in at least one open source NMS participating in the NMS standards meetings. Normally, you would have to be an employee of a company that is a member of ETSI to do this. But we have a way that we can make an open source community member an ETSI delegate. Do you know anyone who has this expertise and would be interested in improving the CRA standard for NMS? Thanks, Valerie

3 3

Project Maintenance Terms project
by Valerie Aurora 21 Jun '25

21 Jun '25

I thought this was an interesting project: This repository is an effort to create a short snippet of text to add to a README or other file making it explicit that the creators or maintainers of software provided free and as-is will not accept any further burdens or impositions with respect to responsiveness, maintenance or updates, particularly any attempts to impose obligations, schedules, or to define any other terms of engagement. https://github.com/mhoye/maintenance-terms More discussion from the author here: https://mastodon.social/@mhoye/114705202798599910 I'm curious if the folks here who sell support contracts already have some language around not providing free maintenance, or other related thoughts? Valerie

1 0

Draft minutes of RIPE 89
by Marcos Sanz 14 May '25

14 May '25

Dear all, we realized yesterday, and we are a bit ashamed to admit, that we forgot to publish/announce the minutes of our last meeting in Prague. Here they are: <https://www.ripe.net/community/wg/active-wg/os/minutes/open-source-working- group-minutes-ripe-89/> https://www.ripe.net/community/wg/active-wg/os/minutes/open-source-working-g roup-minutes-ripe-89/ Please read them and send any corrections, if need be, because we'd like to declare them final during our Thursday session (tomorrow!) We apologize for this last minute rush, Marcos (for all co-chairs)

1 0

Agenda opensource-wg RIPE90
by Sasha Romijn 22 Apr '25

22 Apr '25

Hello all, We received a number of interesting proposals for the open source working group at RIPE90, and are excited to share our draft agenda: 1. Administrative Matters • Welcome • Finalise agenda • Approval of previous minutes 2. Money and Open Source Sustainability - Victoria Risk (ISC) 3. BIND 9 fast(er) - Ondřej Sury (ISC) 4. Growing a team - Maria Matejka (CZ.NIC) 5. goSDN - Martin Stiemerling (da/net) 6. AOB Our session is on Thursday, May 15, at 11:00, in the side room. As usual, you can also participate remotely. Marcos, Marco and Sasha Working group chairs

1 0

Call for Open Source WG Presentations (RIPE90, Lisboa, 15th May, 2025)
by Marcos Sanz 31 Mar '25

31 Mar '25

Dear all, next RIPE Meeting is around the corner - your chance to go nuts about Open Source! Our meeting slot is allocated as usual on Thursday, 15th May 11h-12:30h (UTC+1, local time). If you would like to give a presentation during the session, please contact us (the WG chairs). In general, each talk is 15-30 mins including Q&A (depending on how much time is needed). If you have some idea and are not sure how/if you should present something, then feel free to contact us as well to discuss the idea! Remote presentations are also possible. As always, we are planning to reserve some time at the end of the WG session for lightning talks. These short (5 to 10 minutes max) updates/talks are decided on the day before the WG session on a time/space available basis. No need to submit to us anything for lightning talks at this time, but welcome to do so. We encourage you to step ahead, share your open source thoughts and make this world a better place! Thanks, Sasha, Marco, Marcos Your Open Source WG Chairs

1 1

RIPE NCC Open House: 2024 Community Projects Fund Recipients
by Alastair Strachan 03 Feb '25

03 Feb '25

Dear all, We are pleased to invite you to the 'RIPE NCC Open House: 2024 Community Projects Fund Recipients'. This event will take place on Thursday, 6 February from 15:00 to 16:30 CET and will provide a detailed look at the achievements, challenges, and future goals of the projects supported by the Community Projects Fund (CPF) 2024. Each project team will deliver a presentation, followed by a Q&A session where you can engage directly with the recipients to learn more about their work. The 2024 CPF recipients and their projects are: - Petros Gkigkis – OpenPenny: An open-source tool to identify non-spoofed traffic - Melchior Aelmans – Open Source Distributed Symmetric Key Exchange Implementation - Anna Maria Mandalari – Policy Certification and Verification for Cybersecurity in the Internet of Things (IoT) - Pere Barlet-Ros – GuardXP: From Data Privacy to Improved Cybersecurity - Soroush Rafiee Rad – Open Domain Rank: A community-developed measure for domain reputation ranking based on unique identifiers’ relationships We will also discuss the decision to pause the CPF for 2025 and share insights about the fund's future direction. For more information and to register for the event, please visit the event page at: https://www.ripe.net/meetings/open-house/ripe-ncc-open-house-2024-community… Kind Regards Alastair Strachan RIPE NCC

1 0

RV: [ripe-list] Update on the Community Projects Fund 2024
by Marcos Sanz 19 Nov '24

19 Nov '24

FYI. Sorry for the cross-posting. > -----Mensaje original----- > De: Alastair Strachan <projectsfund(a)ripe.net> > Enviado el: jueves, 14 de noviembre de 2024 12:55 > Para: ripe-list(a)ripe.net > Asunto: [ripe-list] Update on the Community Projects Fund 2024 > > Dear all, > > After the announcement of this year’s Community Projects Fund recipients, > some challenges emerged with the RIPE Atlas distributed network telescope > project which would have prevented the project from achieving the goals > outlined in the project plan. > > After careful consideration, the Selection Committee made the difficult > decision to withdraw funding for the project. While we understand this is > really disappointing for the recipients, we sincerely hope they will continue > initiatives that bring value to our community and the Internet. > > The Selection Committee has now chosen another project to support from our > pool of finalists: OpenPenny - An open-source tool to identify non-spoofed > traffic. You can read about the project on the Community Projects Fund 2024 > page: > https://www.ripe.net/community/community-initiatives/cpf/previous- > funding-recipients/funding-recipients-2024/ > <https://www.ripe.net/community/community-initiatives/cpf/previous- > funding-recipients/funding-recipients-2024/> > > Warm regards, > Alastair Strachan > Community Projects Fund Coordinator

4 3

Fwd: Save the Date: European Open Source Awards
by Vesna Manojlovic ＠ RIPE.net 06 Nov '24

06 Nov '24

FYI -------- Forwarded Message -------- Subject: Save the Date: European Open Source Awards Date: Thu, 31 Oct 2024 09:14:31 +0000 From: OpenForum Europe <info(a)openforumeurope.org> Reply-To: OpenForum Europe <info(a)openforumeurope.org> To: becha(a)ripe.net Save the Date: European Open Source Awards Mark your calendar for the inaugural ceremony of the European Open Source Awards <https://openforumeurope.us10.list-manage.com/track/click?u=92e540ce342922d8…> /*Save the date:*/ *The European Open Source Awards* /Thursday 30th of January 2025, 6:30pm, Brussels/ *We are delighted to announce the inaugural European Open Source Awards, a milestone event to celebrate European excellence in open source.* Whilst open source plays a critical role in driving European innovation and competitiveness, its recognition by political and business leaders has not kept pace with it. Time has come to bring the deserved spotlight on the European Open Source Community. The European Open Source Awards are part of an exciting new EU-funded initiative to celebrate European excellence in open source and its invaluable contribution to Europe’s Digital Sovereignty. The Awards will be the opportunity to recognise those remarkable individuals who have helped build a vibrant open source community in Europe. /*Mark your calendar and keep your eyes open, further details about this landmark initiative will be shared soon.*/ Add your Event to the EU Open Source Week <https://openforumeurope.us10.list-manage.com/track/click?u=92e540ce342922d8…> *Opening the EU Open Source Week* The European Open Source Awards will take place at the start of the EU Open Source Week, which aims to amplify the impact of FOSDEM <https://openforumeurope.us10.list-manage.com/track/click?u=92e540ce342922d8…> and of the EU Open Source Policy Summi <https://openforumeurope.us10.list-manage.com/track/click?u=92e540ce342922d8…>t, and is designed to facilitate cross-expertise discussion on open source. The EU Open Source Week aims to ensuring that everyone in Brussels for the first week of February can effortlessly transition from developer rooms and community meet-ups to policy panels and governance workshops, maximising the value of their visit and forging lasting connections. Through this initiative, we are uniting European and global networks, reinforcing the strategic importance of open source in Europe’s digital and industrial policies, and further bridging the technical and policy realms. Add your event to the EU Open Source Week here <https://openforumeurope.us10.list-manage.com/track/click?u=92e540ce342922d8…>. View this email in your browser <https://mailchi.mp/bd437baecdab/published-today-ec-study-on-the-impact-of-o…> /Copyright © 2024 OpenForum Europe, All rights reserved./ You are receiving this email because you are subscribed to the OFE mailing list. *Our mailing address is:* OpenForum Europe Bd. Charlemagne 96 Brussels 1000 Belgium Add us to your address book <https://openforumeurope.us10.list-manage.com/vcard?u=92e540ce342922d890e7dc…> Want to change how you receive these emails? You can update your preferences <https://openforumeurope.us10.list-manage.com/profile?u=92e540ce342922d890e7…> or unsubscribe from this list <https://openforumeurope.us10.list-manage.com/unsubscribe?u=92e540ce342922d8…>.

1 0

The Open Source Pledge & philosophy behind it
by Vesna Manojlovic ＠ RIPE.net 15 Oct '24

15 Oct '24

Dear colleagues, last week, "The Open Source Pledge" was launched, supported by 25 companies and 6 large foundations: https://opensourcepledge.com The call is for every organisation that uses & depends on "Open Source software" to *pay* maintainers, (minimum of $2,000 per year per developer at your company) & to self-report annually in a blog post. In addition to "about" pages, https://opensourcepledge.com/about/ There is also a blog post describing the "philosophy" behind it: https://vladh.net/the-philosophy-of-the-open-source-pledge/ ... which ends with this "call to action" : > If you’re an employee, tell your company to pay the maintainers of the software it relies on. And if you’re a key decision maker such as a CEO, CFO or CTO? Do the right thing — it will benefit you, your brand, and the ecosystem you live and work in. ... I find it interesting, if a bit North-American-Centric... What are your thought about this approach? Are there any European companies that would join? And do you have other examples of funding FLOSS ? (in addition to the grants from NLNET, NGI, RIPE NCC Sovern Tech Fund (mentioned in the blog)... ). Regards, Vesna Manojlovic Senior Community Builder RIPE NCC

6 7

Draft agenda open source wg RIPE89
by Sasha Romijn 14 Oct '24

14 Oct '24

Hello all, Please find below the draft agenda for our upcoming meeting during RIPE89. As usual, we have space for Lightning Talks. If you’re interested in doing one, please send a mail to opensource-wg-chairs(a)ripe.net before the Tuesday of the meeting week. If you have any doubts about whether a topic would fit, or other questions, always feel free to contact us. Best regards, Marcos Sanz, Martin Winter and Sasha Romijn Working group chairs —— Thursday, October 31st, 11:00-12:30 CEST 1. Administrative matters - Welcome - Finalise agenda - Approval of previous minutes 2. Chair changes 3. Leveraging Vagrant to Simulate Complex Systems for Network Application Development - Barry O’Donovan We need to model complex environments when developing web applications in a network engineering domain. These environments often consist of routers, switches, BGP daemons, SNMP daemons, looking glasses, and more. While mocking can be useful, it has limitations, and testing in a live production environment poses significant risks. This is where Vagrant — a tool designed to create and configure reproducible and portable development environments — can prove invaluable. In this talk, Barry O’Donovan will showcase how the IXP Manager project leverages Vagrant to simulate the complex network systems of an IXP. He will demonstrate the modeling of multiple Bird instances (both IXP-side and customer), integration of looking glasses to communicate with these Bird daemons, and the use of SNMP simulators to replicate IXP switches. The audience will gain an understanding of Vagrant and come away with concrete ideas on how it can be used to provide a comprehensive framework for developing and testing applications. 4. PiranhaBGP: Failure Detection in BGP Networks - Pascal Gloor PiranhaBGP provides a high-performance solution for rapid failure detection, analysis and debugging in BGP IP, VPN, and EVPN networks by efficiently collecting BGP updates and maintaining the state of each BGP speaker in a centralized database. 5. Lightning Talks - details to come

1 0

Open Source WG Chair selection over - Marco d'Itri to replace Martin Winter
by Martin Winter 07 Oct '24

07 Oct '24

In light of just one candidate and (so far) only positive feedback from the community and us chairs, I declare this selection over in agreement with the other co-chairs. As one of the founding WG Chairs (together with Ondrej Filip) at RIPE 66 in Dublin (first WG session at RIPE67) it's time for me to hand over the last part of the controls to new chairs. The working group started with BoF's at RIPE 66 and previous RIPE as Quagga/Bird sessions, but we liked the idea of getting the Open Source community and the Operator community closer together. Overall, I think we succeeded. We definitely had a few remarkable sessions. But this RIPE will be my 23rd RIPE as a WG chair and stepping down after more than 10 years in the same role sounds like the right thing to do. I will continue to look for other things to do in this community and potentially end up in a different role or WG as a chair in a different group. With that said, this RIPE 89 will be my last as WG chair and Marco d'Itri will start his new role as Open Source WG chair immediately after this RIPE meeting along with the existing other WG chairs Marcos Sanz and Sasha Romijn. Regards, Martin Winter Open Source WG co-chair

3 2

Call for Open Source WG Presentations (RIPE89, Prague, 31st October, 2024)
by Marcos Sanz 01 Oct '24

01 Oct '24

Dear all, the next RIPE Meeting is around the corner - your chance to present about some interesting Open Source! Our working group meeting slot is allocated on Thursday, 31st October, 11h-12:30h local time. If you would like to give a presentation during the Open Source WG session, then please contact us (the WG chairs). In general, each talk is 15-30 mins including Q&A (depending on how much time is needed). If you have some idea and are not sure how/if you should present something, then feel free to contact us as well to discuss the idea! Remote presentations are also possible. As always, we are planning to reserve some time at the end of the WG session for lightning talks. These short (5 to 10 minutes max) updates/talks are decided on the day before the WG session on a time/space available basis. No need to submit to us anything for these talks at this time. Big thanks in advance Marcos, Martin, Sasha Your Open Source WG Chairs

1 1

End of Nomination Period for WG Chair - One candidate. Opinions?
by Martin Winter 30 Sep '24

30 Sep '24

The time for the nomination period is over and we got one nomination for WG Chair: Marco d'Itri Marco is probably well known to many of you as a regular attendee to RIPE meetings. From his bio: Marco d'Itri has been involved in various roles with the Internet in Italy since the late '90s, and has been a Debian Developer since 1997. He is employed by an italian cloud infrastructure, web hosting and colocation provider and also helps to run MINAP, the alternative IXP of Milano. We would like to hear some feedback from the community now. Do you think he i a good candidate or have any reservations? Please reply to the list with your approval or disapproval. In case you don't want to share any concerns publicly, then please email the opensource-wg-chairs(a)ripe.net and we will keep these concerns private. But in general, public feedback and comments are preferred. Regards, Martin Winter Open Source WG Chair

8 7

Fwd: EU set up a CRA Expert Group + consultations on EU Cybersecurity Act
by Sasha Romijn 24 Sep '24

24 Sep '24

Dear open-source working group, Please see the mail below from cooperation-wg about the EU setting up a CRA Expert Group, and two consultations. We’ve particularly discussed the CRA and its potential impact on open source software before. Sasha Forwarded message: > From: Romain Bosc <rbosc(a)ripe.net> > To: cooperation-wg(a)ripe.net > Subject: [cooperation-wg] EU set up a CRA Expert Group + consultations > on EU Cybersecurity Act > Date: Tue, 24 Sep 2024 09:12:49 +0200 > > Dear all, > > Just to flag that the European Commission has launched a call for > applications to join a newly established Expert Group on the > cybersecurity > of products with digital elements (CRA Expert Group) -- the group will > assist and advise the Commission on issues relevant to the > implementation > of the Cyber Resilience Act (CRA) -- deadline to apply is on 17 > October > 2024: > > https://digital-strategy.ec.europa.eu/en/news/call-applications-cyber-resil… > > In addition, the European Commission has opened two consultations > relating > to the implementation of the EU Cybersecurity Act adopted in June > 2019, > which introduces an EU-wide cybersecurity certification framework for > ICT > products, services and processes. > > One is about the Draft Implementing Regulation relating to the > European > Common Criteria-based cybersecurity certification scheme (EUCC), and > state-of-the-art documents specifying evaluation methods, techniques > and > tools that apply to the certification of ICT products, or security > requirements: > > https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/1… > > The other consultation is on the Draft Implementing Regulation > establishing > the circumstances, formats and procedures for notifications relevant > to > Conformity Assessment Bodies (CABs): > > https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/1… > > Any questions, please let us know. > > All best > Romain > -- > Romain Bosc > Sr Public Policy & Governance Officer > RIPE NCC > E: rbosc(a)ripe.net > ----- > To unsubscribe from this mailing list or change your subscription > options, please visit: > https://mailman.ripe.net/mailman3/lists/cooperation-wg.ripe.net/ > As we have migrated to Mailman 3, you will need to create an account > with the email matching your subscription before you can change your > settings. > More details at: > https://www.ripe.net/membership/mail/mailman-3-migration/

1 0

Contribution and credits policy BCP draft
by Maria Matejka 23 Sep '24

23 Sep '24

Dear fellow OSS WG participants, following up on my talk today, I'm sending here the BCP draft for further discussion. > Open-source projects SHOULD publish their contribution and credits policy and > be open about how (and if) people can contribute. Open-source project > maintainers SHOULD adhere to the published policy and update it when > circumstances change. > > To create such a policy, maintainers can use a [policy guide](https://github.com/contribution-credit/policy/blob/main/policy_guide… > as a starting point. Maintainers are advised to be as open and friendly as they can. For reference, you can also [replay my talk](https://ripe88.ripe.net/programme/meeting-plan/os-wg/) or [see RIPE 87 OSS WG session](https://ripe87.ripe.net/programme/meeting-plan/os-wg/). And here are some previous relevant threads in this list: - [first draft](https://www.ripe.net/ripe/mail/archives/opensource-wg/2023-December/… - [second draft](https://www.ripe.net/ripe/mail/archives/opensource-wg/2024-January/0… - [article at LWN](https://www.ripe.net/ripe/mail/archives/opensource-wg/2024-May/000270.… And that's probably all information you may need for context so please comment and roast this BCP draft. Happy contributing and crediting! Maria -- Maria Matejka (she/her) | BIRD Team Leader | CZ.NIC, z.s.p.o.

5 4

Open Source WG Chair selection - Looking for candidates
by Martin Winter 20 Sep '24

20 Sep '24

It’s two months until the next fall RIPE meeting - and this means it’s time again for a Working Group Chair Selection. To avoid the issues from the last meeting, we would like to clarify on how we want to do the selection this time and the requirements, selection process etc. There is some progress by RIPE to define a new common process for all the working groups, however, this is not ready yet and we thus announce the following: Our working group has currently 3 chairs: - Martin Winter (Since Start of WG, RIPE 66) - Marcos Sanz (Since RIPE 84) - Sasha Romjin (Since RIPE 88) Martin Winter is currently considering stepping down as a WG chair to make space for somebody new with fresh ideas. However, this will depend on getting candidates as well. Martin will decide after the new candidates are known, if he will either withdraw from further terms or stand as a candidate for re-election against the new candidates. Criteria/Expectations of a WG chair: - You have attended multiple physical RIPE meetings before (and are familiar with how RIPE works) - You will be attending most RIPE meetings while serving as a chair in person - You will attend this Fall meeting session (Physical or Virtual) For more details, see the Guide for New RIPE Working Group Chairs (https://www.ripe.net/publications/docs/ripe-765/) or the RIPE Working Group Chair e-learning course (https://academy.ripe.net/course/info.php?id=16) If you are interested to serve as a WG chair: Nomination period is until Sept 27, 2024, 23:59 UTC. Send an email to opensource-wg-chairs(a)ripe.net to make us aware of your candidacy before this deadline. In the email, please include a short bio and statement why you are interested. On Sep 28, we will then send an email with all candidates, their submitted bio and a summary of previous RIPE attendance of each candidate to the list and open a discussion for feedback, statement of support for specific candidates and any other feedback in regards to them. In parallel, the working group chairs will run interviews and discussions with all the candidates and we require the candidates to make time for these calls and get back to us in a timely manner to email requests during this month. The time is short and we need to be prepared before the meeting! Please be aware, these are not elections, but selections. The ultimate decision is by the remaining WG chairs as all the chairs need to work together. Martin, Marcos & Sasha (the current WG chairs)

2 1

Fwd: Support needed for Free Software in EU Consultation
by Vesna Manojlovic ＠ RIPE.net 16 Sep '24

16 Sep '24

-------- Forwarded Message -------- Subject: Support needed for Free Software in EU Consultation Date: Wed, 11 Sep 2024 13:21:53 +0200 From: Bonnie Mehring <bonnie(a)fsfe.org> Hej The European Commission has recently cut the funding for the Next Generation Internet (NGI), which supports Free Software projects, by €27 million [1]. This underscores the fragility and precarious nature of funding for Free Software and the need for sustainable support has become more evident than ever. We encourage you, as hackerspace, to join us in safeguarding the future of software freedom by participating in the ongoing consultation for the Digital Europe Programme [2]. This consultation presents a key opportunity to advocate for stable funding and ensure Free Software remains a priority in Europe’s digital strategy. Collective action is vital, especially in light of the non-transparent and unclear process behind the Next Generation Internet (NGI) funding cuts. The deadline of the consultation is 20 September (midnight Brussels time). We already participated [3] and here are some key points to consider while submitting the consultation: Software is integral to every aspect of our lives. It’s essential that this technology empowers, not restricts, by granting everyone the right to use, understand, adapt, and share software. We urge the EU to prioritise Free Software, ensuring financial support for related projects and ecosystems. Sustainable, long-term funding will enhance independence, resilience, control, security, and sovereignty. The Digital Europe Programme could only unfold its full potential if it is systematically focusing on the support of Free Software solutions. Free Software is crucial to avoiding future dependencies and lock-ins. By adopting a “Free Software first” approach, the EU can ensure taxpayer money is used efficiently, fostering collaboration and interoperability across Europe. If it’s public money, it should be public code. If you are willing to participate in the consultation and support the proposal for Free Software funding, please let us know via email contact(a)fsfe.org Best Regards, Bonnie [1] https://fsfe.org/news/2024/news-20240719-01.html [2] https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/1… [3] https://fsfe.org/news/2024/news-20240911-02.html -- Bonnie Mehring - Project manager - Free Software Foundation Europe Schönhauser Allee 6/7, 10119 Berlin, Germany | t +49-30-27595290 Registered at Amtsgericht Hamburg, VR 17030 |(fsfe.org/support)

1 0

RV: [ripe-list] Announcing Green Tech Hackathon: in December, in Amsterdam (& online)
by Marcos Sanz 28 Aug '24

28 Aug '24

FYI. Sorry for cross-posting. > -----Mensaje original----- > De: Vesna Manojlovic @ RIPE.net <becha(a)ripe.net> > Enviado el: martes, 27 de agosto de 2024 12:24 > Para: ripe-list(a)ripe.net > Asunto: [ripe-list] Announcing Green Tech Hackathon: in December, in > Amsterdam (& online) > > Dear colleagues, > > Join the next RIPE NCC hackathon focused on Green Tech this December! > Our goals are to develop tools, policies and protocols to reduce the > environmental impact of Internet infrastructure. > > RIPE NCC hackathons are non-commercial and non-competitive. We focus on > cooperation and openness - all the code produced is FLOSS, and all the > results are published on public software repositories, wikis, and on > blogs to help others further create, experiment, and develop ideas and > tools. > > Please find more information in this RIPE Labs article: > https://labs.ripe.net/author/becha/announcing-the-green-tech-hackathon/ > > Direct link to application form: > https://www.ripe.net/participate/forms/apply/green-tech-20234/ > > Regards, > Vesna Manojlović > > -- > Senior Community Builder > RIPE NCC > > > ----- > To unsubscribe from this mailing list or change your subscription options, > please visit: https://mailman.ripe.net/mailman3/lists/ripe-list.ripe.net/ > As we have migrated to Mailman 3, you will need to create an account with > the email matching your subscription before you can change your settings. > More details at: https://www.ripe.net/membership/mail/mailman-3- > migration/

1 0

"The European Union must keep funding free software", open letter to EU about NGI
by Vesna Manojlovic ＠ RIPE.net 22 Jul '24

22 Jul '24

Dear community, this is an open letter, published by more than 42 organisations & individuals, as a reaction to the announcements by EU to stop funding NGI: https://pad.public.cat/lettre-NCP-NGI Next Generation Internet (NGI) programmes, since 2020 part of European Commission's Horizon programme, fund free software in Europe . This year, according to the Horizon Europe working draft detailing funding programmes for 2025, NGI is not mentioned any more as part of Cluster 4. Therefore, I share this call with RIPE community, to gather support & influence EU to keep on funding free software. Regards, Vesna Manojlovic -- Senior Community Builder RIPE NCC

1 0

RIPE88 open source WG meeting minutes
by Sasha Romijn 13 Jun '24

13 Jun '24

Hello all, The minutes for our meeting at RIPE88 have now been published: https://www.ripe.net/community/wg/active-wg/os/minutes/open-source-working-… Please let the chairs know if you have any comments. Thanks to Sean Mottles and other RIPE NCC staff for taking and editing them. Sasha

1 0

Final reminder for RIPE88 lightning talks
by Sasha Romijn 20 May '24

20 May '24

Hello all, We look forward to our session this Thursday afternoon at RIPE88! Meanwhile, I wanted to remind you that we still have space for lightning talks. If you would like to present a short update on your RIPE-related open source project, or have something else to share that is relevant to the group, please send a short message to opensource-wg-chairs(a)ripe.net by noon CEST tomorrow. Talks will be selected on Tuesday afternoon. Marcos Sanz & Martin Winter & Sasha Romijn

1 0

Open-source Software Risk Mitigation Practices survey
by Sasha Romijn 15 May '24

15 May '24

Hello all, As you can see on the agenda, Petr Špaček from ISC will do a talk on Open-source QA in our RIPE88 session. They’ve set up a survey on this subject, and we encourage you all to submit: https://ec.europa.eu/eusurvey/runner/RIPE88OpenSourceWGSurvey The data from this survey will serve as input for both the presentation and the discussion we can have afterwards. Looking forward to insightful discussions from your survey input! Best regards, Marcos Sanz & Martin Winter & Sasha Romijn Open-source WG chairs

2 1

Credit and contributions policy guide launches May 20
by Valerie Aurora 14 May '24

14 May '24

Hi all, I'm happy to say that, thanks to Maria Matějka, the guide to creating a contributions and credit policy is up on GitHub and ready for PRs: https://github.com/contribution-credit/policy Feel free to share this starting now, but the "official" launch will be May 20, when Linux Weekly News publishes an article on the policy guide. We are open to improvements of all sorts, and especially additions to the list of projects that already have such a policy: https://github.com/contribution-credit/policy/blob/main/policies.md And of course you can check out our own contributions and credit policy :) https://github.com/contribution-credit/policy/blob/main/CONTRIBUTING.md Thanks again to Maria Matějka for many contributions, edits, structural improvements, and creating the GitHub repo, Marcos Sanz and Martin White for early support and important input, and many others from the OS WG for their input. If you'd like to add yourself as a named contributor or update your entry on the credits, please do! Valerie

1 1

Draft agenda open source wg RIPE 88
by Marcos Sanz 10 May '24

10 May '24

Dear all, Please find attached the draft agenda for the upcoming open source working group meeting during RIPE 88. It will soon be online. As always, we'd still welcome any lightning talks! No formal submission is required ahead of RIPE 88, but please send a short message to the chairs by noon on Tuesday of the meeting week. Talks will be selected on Tuesday afternoon. Best regards, Martin Winter & Sasha Romijn & Marcos Sanz Open Source WG Chairs -- Thursday, 23rd May, 14:00-15:30 CEST * Administrivia * Chair selection process review (Martin Winter, co-chair) * Open-source QA process (Petr Špaček, Internet Systems Consortium) Speculative session with WG participant survey & open mic discussion about how WG sees open-source Q&A processes. We will compare wishes of the WG with real example of what is being done today around BIND DNS server. * Contribution and credits policy for open-source projects (Maria Matejka, BIRD | CZ.NIC) After RIPE 87 in Rome, several people thought more about contributing to open-source software and crediting people. We created a template or example how a policy on contributions and credits may look like, and it's ready for use. * Lightning talks * AOB --

1 0

Register for RIPE NCC Training Courses: Zagreb, Croatia: 15-16-17 May 2024.
by Vesna Manojlovic ＠ RIPE.net 30 Apr '24

30 Apr '24

Dear colleagues, We invite you to register for the the RIPE NCC*LIR,**RIPE Database and BGP Routing Security Training Course* which will take place in *Zagreb* on *15-16-17 May 2024*. : https://learning.ripe.net For each of those topics, we promote Free/Libre & Open Source tools to help you in your work. Our training courses are free of charge and *delivered* in *English*. Trainers will be Gerardo Viviers and Ralph Smit. If you have already benefitted from a RIPE NCC training, we encourage you to share this email with your colleagues who might be interested in attending our courses. *General Information:* ------------------- Register to attend your chosen course(s) through our learning platform: https://learning.ripe.net We have a limited number of places, and registration will close once we are at capacity. The course includes lunch and printed training materials. If you have any questions, please contact learning(a)ripe.net. We are looking forward to seeing you in Zagreb! Kind regards, RIPE NCC Learning and Development (& Vesna, your link between RIPE NCC Croatia ;-) ======= *LIR Training Course:* ------------------ Date: *Wednesday, 15 May 2024* Time: 09:00-17:30 local time Hosted by: Carnet <https://www.carnet.hr/en/> at this location: Josipa Marohnića 5, 10 000 Zagreb <https://www.google.com/maps/place/Croatian+Academic+and+Research+Network+-+…> The *LIR Training Course* is a one-day introduction to the RIPE NCC's administrative procedures and RIPE Policies related to obtaining and distributing Internet resources (i.e. IP addresses, AS Numbers and reverse DNS delegation) and operating a Local Internet Registry (LIR). The course includes a basic introduction to the RIPE Database. You should attend this training course: if you are a staff member of a Local Internet Registry (LIR) in the RIPE NCC service region. For more information visit our: *Course information* and *registration page* <https://learning.ripe.net/w/courses/1-lir-training-course> === **RIPE Database Training Course*:* ---------------------------- Date: *Thursday, 16 May 2024* Time: 09:00-17:30 local time Hosted by: Carnet <https://www.carnet.hr/en/> at this location: Josipa Marohnića 5, 10 000 Zagreb <https://www.google.com/maps/place/Croatian+Academic+and+Research+Network+-+…> The *RIPE Database Training Course* is a one-day course. We'll make you a capable user of the RIPE Database. Mixing hands-on activities with theory, the course participants will get a comprehensive idea of what the RIPE Database is and what they can do with it. You should attend this training course if you are part of the staff of a Local Internet Registry (LIR) in the RIPE NCC service region, and need to register networks in the RIPE Database. You should attend this training course if you are part of the staff of a Local Internet Registry (LIR) in the RIPE NCC service region, and need to register networks in the RIPE Database. For more information visit our: *Course information* and *registration page* <https://learning.ripe.net/w/courses/2-ripe-database-training-course> === *BGP Routing Security Training Course:* ----------------------------- Date: *Friday, 17 May 2024* Time: 09:00-17:30 local time Hosted by: Carnet <https://www.carnet.hr/en/> at this location: Josipa Marohnića 5, 10 000 Zagreb <https://www.google.com/maps/place/Croatian+Academic+and+Research+Network+-+…> BGP Routing Security training course is a one-day course covering different aspects of the security of BGP protocol. The participant will gain insight and a high-level understanding of the need for security in BGP, the main threats it faces and the main security measures that can be applied nowadays. Some future developments on the topic will also be covered. The course includes theory and hands-on exercises. You should attend this training course if you are using, or plan to use, BGP in your network and want to know more about the potential threats and the security solutions available to make your BGP routing more secure. For more information visit our: *Course information and registration page* <https://learning.ripe.net/w/courses/34-bgp-routing-security-training-course…>

1 0

Invitation to RIPE NCC Open House Events – Community Projects Fund Recipients 2023
by Alastair Strachan 22 Apr '24

22 Apr '24

Dear Colleagues, We are pleased to invite you to participate in the upcoming RIPE NCC Open House events. If you are thinking of applying for the Community Projects Fund this year or want to get updates about the projects selected for the 2023 RIPE NCC Community Projects Fund, make sure you attend these sessions to gain insights into the progress, challenges, and future goals of the supported initiatives. During the sessions, recipients of the 2023 RIPE NCC Community Projects Fund will present detailed updates on their projects, summarising their journey thus far and their current advancements. Each presentation will be followed by a Q&A segment, offering you the chance to interact directly with the project teams and gain a deeper understanding of their work. https://www.ripe.net/membership/meetings/open-house/cpf-recipients-2024/ Session Schedule: First Session: April 26, 2024, 10:00 - 11:30 CEST (08:00 - 09:30 UTC) Thomas Holterbach: Designing the Next Generation of Public BGP Route Collection Infrastructures Tobias Fiebig: Measurement.network - Organizing Active Measurements Ioana Livadariu: SubZero - Monitoring the Deployment Impact of the Submarine Cable System Second Session: May 2, 2024, 10:00 - 11:30 CEST (08:00 - 09:30 UTC) Marcus Dansarie: : Secure Time for IoT Devices - Developing the Roughtime Proposed Standard Raffaele Sommese: Anycast Discovery - Daily Mapping the Anycast Landscape for Enhanced Internet Resilience Suelette Dreyfus and Richard Prospesel: Community Canary - Exploring Tor's Rust Implementation, Arti We encourage all members of the Internet technical community and anyone interested in the advancement of Internet infrastructure to attend these insightful sessions. Looking forward to your participation in fostering innovation and progress within our community. Kind Regards Alastair Strachan RIPE NCC

1 0

xz incident shows the need for structural change (in FLOSS maintenance & funding)
by Vesna Manojlovic 11 Apr '24

11 Apr '24

FYI: by Sovereign Tech Fund https://www.sovereigntechfund.de/news/xz-structural-change APRIL 4, 2024 BY ADRIANA GROH " xz incident shows the need for structural change" At Sovereign Tech Fund, we're following the xz incident closely and listening to the many voices in the FOSS maintainer community. There are clear signs that this is a sophisticated attack, but experts are still analyzing it, and it seems we won't know all the facts for a while. At this time, we don't want to point at any single cause and certainly don’t want to suggest a quick fix. We would, however, like to point out again the huge importance of digital infrastructure, which is regrettably overlooked and invisible to most of us. xz is merely the most recent example to illustrate how important the open source ecosystem is for all of us. At the same time, it shows very clearly how serious the structural issues are: for example, not enough new contributors, too few experienced contributors, too little recognition, and not enough (long-term) support from various stakeholders. One consequence is burnout among unpaid volunteers, which is unfortunately not a rare occurrence. If we keep ignoring these systemic issues, this house of cards will be our undoing (see our favorite xkcd comic). A great many companies and organizations incorporate and use critical open source components without ensuring that they are maintained and secured at all. We see this kind of maintenance as an undertaking that is in the public interest. It should not be the responsibility of unpaid volunteers alone, nor should it rest wholly on the private sector. It's a task whose importance society as a whole needs to acknowledge, and should be prioritized accordingly. As we saw with Heartbleed (2014), Log4Shell (2021) and other incidents, foundational open source technologies are essential parts of modern digital infrastructure. They underpin all (not just digital) endeavors, both in the public and private sectors. Just as physical infrastructure like roads, railways, and water systems are constantly being maintained, these digital components also need to be serviced and updated in order to serve as the foundation for digital sovereignty, a successful economy, and a resilient democratic society. Since the creation of the Sovereign Tech Fund, we have been exploring different support mechanisms to fulfill our mission of supporting the development, improvement, and maintenance of open digital infrastructure. We are currently working on more ways to tackle these challenges. Financial support for the people behind the code is a good first step and an important building block. However, to increase the long-term success of our mission, complementary and reinforcing mechanisms are needed. We are in contact with maintainers and FOSS communities as we develop and test these additional mechanisms. Our areas of focus include improving software maintainability, increasing bug resilience, better developer tooling, reducing technical debt, and expanding the communities of FOSS contributors. We welcome you to share your ideas, feedback, or constructive criticism with us. Through Sunday, 7 April 2024, we are especially eager to hear from open source maintainers who would like to fill out our fellowship pilot program survey. https://www.sovereigntechfund.de/news/foss-maintainer-fellowship-survey We see the creation of and commitment to the Sovereign Tech Fund by SPRIND and the German Ministry for Economic Affairs and Climate Action as a clear sign of the increasing awareness of the open source ecosystem’s significance. We hope that our plans for the future will inspire many others to join us in this work and have a lasting impact together. Incidents like xz – others will surely follow – show that we have a major task ahead of us for the foreseeable future.

2 1

On the xz/liblzma breach and open source maintainer burnout
by Johan Helsingius 30 Mar '24

30 Mar '24

Rob Mensching: A Microcosm of the interactions in Open Source projects https://robmensching.com/blog/posts/2024/03/30/a-microcosm-of-the-interacti…

1 0

Teo En Ming's Notes on Basic Configuration of Cisco ASA 5516-X Firewall - Version 1
by Turritopsis Dohrnii Teo En Ming 21 Mar '24

21 Mar '24

Subject: Teo En Ming's Notes on Basic Configuration of Cisco ASA 5516-X Firewall - Version 1 Good day from Singapore, Author: Mr. Turritopsis Dohrnii Teo En Ming Country: Singapore Date of Publication: 20 March 2024 Wednesday Document Version: 1 I have bought this refurbished/second hand/used Cisco ASA 5516-X firewall with FirePOWER Services for SGD$100 at Bukit Panjang Ring Road on 17 Mar 2024 Sunday at about 8.30 PM Singapore Time. On 19 March 2024 Tuesday, I have completed basic configuration of this firewall. Configuration Start: 19 March 2024 Tuesday, 9.22 PM Configuration End: 19 March 2024 Tuesday, 11.33 PM Below are my notes on configuring the Cisco ASA 5516-X firewall (basic). Part 1: Factory reset the Cisco ASA 5516-X firewall =================================================== Reference guide: Clearing, resetting or erasing configuration on Cisco ASA Link: https://www.linkedin.com/pulse/clearing-resetting-erasing-configuration-cis… cisco> en Password: ***** cisco# conf t cisco(config)# ***************************** NOTICE ***************************** Help to improve the ASA platform by enabling anonymous reporting, which allows Cisco to securely receive minimal error and health information from the device. To learn more about this feature, please visit: http://www.cisco.com/go/smartcall Would you like to enable anonymous error reporting to help improve the product? [Y]es, [N]o, [A]sk later: Y Enabling anonymous reporting. Adding "call-home reporting anonymous" to running configuration... Creating trustpoint "_SmartCallHome_ServerCA" and installing certificate... Trustpoint CA certificate accepted. Please remember to save your configuration. cisco(config)# configure factory-default Based on the inside IP address and mask, the DHCP address pool size is reduced to 250 from the platform limit 256 WARNING: The boot system configuration will be cleared. The first image found in disk0:/ will be used to boot the system on the next reload. Verify there is a valid image on disk0:/ or the system will not boot. Begin to apply factory-default configuration: Clear all configuration Executing command: ! Executing command: interface Management1/1 Executing command: management-only Executing command: no nameif Executing command: no security-level Executing command: no ip address Executing command: no shutdown Executing command: exit Executing command: ! Executing command: interface GigabitEthernet1/1 Executing command: nameif outside INFO: Security level for "outside" set to 0 by default. Executing command: security-level 0 Executing command: ip address dhcp setroute Executing command: no shutdown Executing command: exit Executing command: ! Executing command: interface GigabitEthernet1/2 Executing command: nameif inside INFO: Security level for "inside" set to 100 by default. Executing command: security-level 100 Executing command: ip address 192.168.1.1 255.255.255.0 Executing command: no shutdown Executing command: exit Executing command: ! Executing command: object network obj_any Executing command: subnet 0.0.0.0 0.0.0.0 Executing command: nat (any,outside) dynamic interface Executing command: exit Executing command: ! Executing command: http server enable Executing command: http 192.168.1.0 255.255.255.0 inside Executing command: ! Executing command: dhcpd auto_config outside Executing command: dhcpd address 192.168.1.5-192.168.1.254 inside Executing command: dhcpd enable inside Executing command: ! Executing command: logging asdm informational Executing command: ! Executing command: ! Executing command: ! Factory-default configuration is completed ciscoasa(config)# reload System config has been modified. Save? [Y]es/[N]o: y Cryptochecksum: 200435a9 cee9c848 4fb5e91d ac201631 3250 bytes copied in 0.150 secs Proceed with reload? [confirm] ciscoasa(config)# *** *** --- START GRACEFUL SHUTDOWN --- Shutting down isakmp Shutting down webvpn Shutting down sw-module Shutting down License Controller Shutting down File system *** *** --- SHUTDOWN NOW --- Process shutdown finished Rebooting... (status 0x9) .. INIT: Sending processes the TERM signal Deconfiguring network interfaces... done. Sending all processes the TERM signal... Sending all processes the KILL signal... Deactivating swap... Unmounting local filesystems... Rebooting... Part 2: Basic Configuration of Cisco ASA 5516-X Firewall ========================================================= Reference guide: Basic Cisco ASA 5506-x Configuration Example Link: https://www.speaknetworks.com/basic-cisco-asa-5506-x-configuration-example/ ciscoasa> en Password: ciscoasa# ciscoasa# show bootvar BOOT variable = Current BOOT variable = CONFIG_FILE variable = Current CONFIG_FILE variable = Step 1: Configure ASA interfaces and assign appropriate security levels =========================================================================== ciscoasa# conf t ciscoasa(config)# interface GigabitEthernet1/1 ciscoasa(config-if)# description to WAN ciscoasa(config-if)# nameif outside ciscoasa(config-if)# security-level 0 ciscoasa(config-if)# ip address dhcp setroute ciscoasa(config-if)# exit ciscoasa(config)# interface GigabitEthernet1/2 ciscoasa(config-if)# description to LAN ciscoasa(config-if)# nameif inside ciscoasa(config-if)# security-level 100 ciscoasa(config-if)# ip address 192.168.1.1 255.255.255.0 ciscoasa(config-if)# exit ciscoasa(config)# interface GigabitEthernet1/3 ciscoasa(config-if)# description to DMZ1 ciscoasa(config-if)# nameif dmz1 ciscoasa(config-if)# security-level 50 ciscoasa(config-if)# ip address 192.168.2.1 255.255.255.0 ciscoasa(config-if)# exit Step 2: Configure ASA as an Internet gateway, enable Internet access ======================================================================== Configure NAT rules. ciscoasa(config)# nat (inside,outside) after-auto source dynamic any interface ciscoasa(config)# nat (dmz1,outside) after-auto source dynamic any interface Allow ping requests to go out. ciscoasa(config)# policy-map global_policy ciscoasa(config-pmap)# class inspection_default ciscoasa(config-pmap-c)# inspect icmp ciscoasa(config-pmap-c)# exit ciscoasa(config-pmap)# exit Step 3: Configure static NAT to web servers, grant Internet inbound access to web servers =========================================================================================== I will skip this step because I am not planning to have any public facing web servers at home at the moment. Step 4: Configure DHCP service on the ASA ============================================ Configure DHCP server for LAN network. ciscoasa(config)# dhcpd address 192.168.1.2-192.168.1.254 inside ciscoasa(config)# dhcpd dns 8.8.8.8 8.8.4.4 ciscoasa(config)# dhcpd lease 3600 ciscoasa(config)# dhcpd ping_timeout 50 ciscoasa(config)# dhcpd enable inside ciscoasa(config)# dhcprelay timeout 60 Configure DHCP Server for DMZ network. ciscoasa(config)# dhcpd address 192.168.2.2-192.168.2.254 dmz1 ciscoasa(config)# dhcpd enable dmz1 ciscoasa(config)# exit (Optional) Step 5: Redirect traffic to the FirePOWER module for deeper level inspection ======================================================================================== I don't think I have any FirePOWER feature license, so I will skip this step for the moment. Step 6: Hardening the device =============================== Shutdown unused interfaces. ciscoasa(config)# interface GigabitEthernet1/4 ciscoasa(config-if)# shutdown ciscoasa(config-if)# interface GigabitEthernet1/5 ciscoasa(config-if)# shutdown ciscoasa(config-if)# interface GigabitEthernet1/6 ciscoasa(config-if)# shutdown ciscoasa(config-if)# interface GigabitEthernet1/7 ciscoasa(config-if)# shutdown ciscoasa(config-if)# interface GigabitEthernet1/8 ciscoasa(config-if)# shutdown ciscoasa(config-if)# exit Enable SSH access for admin. ciscoasa(config)# hostname ASA5516X ASA5516X(config)# crypto key generate rsa modulus 1024 (change to 4096 in future) WARNING: You have a RSA keypair already defined named <Default-RSA-Key>. Do you really want to replace them? [yes/no]: yes Keypair generation process begin. Please wait... Hosts from the internet are not allowed to ssh into the firewall. LAN users are allowed to ssh into the firewall. ASA5516X(config)# ssh 192.168.1.0 255.255.255.0 inside DMZ users are not allowed to ssh into the firewall. ASA5516X(config)# ssh timeout 30 ASA5516X(config)# ssh version 2 ASA5516X(config)# aaa authentication ssh console LOCAL WARNING: local database is empty! Use 'username' command to define local users. Step 7: Configure time and enable logging =========================================== I didn't set the time or timezone correctly. Will fix it in the future. ASA5516X(config)# clock set 22:37:00 Mar 19 2024 ASA5516X(config)# clock timezone GMT +8 ASA5516X(config)# logging enable ASA5516X(config)# logging timestamp ASA5516X(config)# logging buffer-size 512000 ASA5516X(config)# logging buffered debugging Part 3: Create LOCAL users for SSH ================================== Reference guide: Cisco ASA Firewall Management Interface Configuration (with Example) Link: https://www.networkstraining.com/using-the-management-interface-of-the-cisc… ASA5516X(config)# username cisco password cisco privilege 15 Part 4: Enable ASA Web Interface ================================= Reference guide: How do I perform a basic setup of Cisco ASA 5516-X firewall? Link: https://community.cisco.com/t5/network-security/how-do-i-perform-a-basic-se… ASA5516X(config)# http server enable ASA5516X(config)# http 192.168.1.0 255.255.255.0 inside ASA5516X(config)# enable password cisco level 15 Hosts from the internet are not allowed to access the ASA web interface. Hosts from the DMZ are not allowed to access the ASA web interface. Part 5: Saving the Firewall Configuration ========================================== ASA5516X(config)# write mem Building configuration... Cryptochecksum: 5857f4ec 34234f34 4cec64f6 f85d7cd4 7180 bytes copied in 0.150 secs [OK] ASA5516X(config)# write mem Building configuration... Cryptochecksum: 5857f4ec 34234f34 4cec64f6 f85d7cd4 7180 bytes copied in 0.150 secs [OK] Part 6: show run output ======================= ASA5516X# show run : Saved : : Serial Number: JAD****00ZZ : Hardware: ASA5516, 8192 MB RAM, CPU Atom C2000 series 2416 MHz, 1 CPU (8 cores) : ASA Version 9.7(1)4 ! hostname ASA5516X enable password $sha512$5000$LuFgFhttGYuAEdvYbB7Y9g==$M2/7xYvePzQsOAQNrQsxTg== pbkdf2 names ! interface GigabitEthernet1/1 description to WAN nameif outside security-level 0 ip address dhcp setroute ! interface GigabitEthernet1/2 description to LAN nameif inside security-level 100 ip address 192.168.1.1 255.255.255.0 ! interface GigabitEthernet1/3 description to DMZ1 nameif dmz1 security-level 50 ip address 192.168.2.1 255.255.255.0 ! interface GigabitEthernet1/4 shutdown no nameif no security-level no ip address ! interface GigabitEthernet1/5 shutdown no nameif no security-level no ip address ! interface GigabitEthernet1/6 shutdown no nameif no security-level no ip address ! interface GigabitEthernet1/7 shutdown no nameif no security-level no ip address ! interface GigabitEthernet1/8 shutdown no nameif no security-level no ip address ! interface Management1/1 management-only no nameif no security-level no ip address ! ftp mode passive clock timezone GMT 8 object network obj_any subnet 0.0.0.0 0.0.0.0 pager lines 24 logging enable logging timestamp logging buffer-size 512000 logging buffered debugging logging asdm informational mtu outside 1500 mtu inside 1500 mtu dmz1 1500 no failover no monitor-interface service-module icmp unreachable rate-limit 1 burst-size 1 no asdm history enable arp timeout 14400 no arp permit-nonconnected arp rate-limit 16384 ! object network obj_any nat (any,outside) dynamic interface ! nat (inside,outside) after-auto source dynamic any interface nat (dmz1,outside) after-auto source dynamic any interface timeout xlate 3:00:00 timeout pat-xlate 0:00:30 timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 sctp 0:02:00 icmp 0:00:02 timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00 timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00 timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute timeout tcp-proxy-reassembly 0:01:00 timeout floating-conn 0:00:00 timeout conn-holddown 0:00:15 timeout igp stale-route 0:01:10 user-identity default-domain LOCAL aaa authentication ssh console LOCAL http server enable http 192.168.1.0 255.255.255.0 inside no snmp-server location no snmp-server contact service sw-reset-button crypto ipsec security-association pmtu-aging infinite crypto ca trustpoint _SmartCallHome_ServerCA no validation-usage crl configure crypto ca trustpool policy crypto ca certificate chain _SmartCallHome_ServerCA certificate ca 18dad19e267de8bb4a2158cdcc6b3b4a 308204d3 308203bb a0030201 02021018 dad19e26 7de8bb4a 2158cdcc 6b3b4a30 0d06092a 864886f7 0d010105 05003081 ca310b30 09060355 04061302 55533117 30150603 55040a13 0e566572 69536967 6e2c2049 6e632e31 1f301d06 0355040b 13165665 72695369 676e2054 72757374 204e6574 776f726b 313a3038 06035504 0b133128 63292032 30303620 56657269 5369676e 2c20496e 632e202d 20466f72 20617574 686f7269 7a656420 75736520 6f6e6c79 31453043 06035504 03133c56 65726953 69676e20 436c6173 73203320 5075626c 69632050 72696d61 72792043 65727469 66696361 74696f6e 20417574 686f7269 7479202d 20473530 1e170d30 36313130 38303030 3030305a 170d3336 30373136 32333539 35395a30 81ca310b 30090603 55040613 02555331 17301506 0355040a 130e5665 72695369 676e2c20 496e632e 311f301d 06035504 0b131656 65726953 69676e20 54727573 74204e65 74776f72 6b313a30 38060355 040b1331 28632920 32303036 20566572 69536967 6e2c2049 6e632e20 2d20466f 72206175 74686f72 697a6564 20757365 206f6e6c 79314530 43060355 0403133c 56657269 5369676e 20436c61 73732033 20507562 6c696320 5072696d 61727920 43657274 69666963 6174696f 6e204175 74686f72 69747920 2d204735 30820122 300d0609 2a864886 f70d0101 01050003 82010f00 3082010a 02820101 00af2408 08297a35 9e600caa e74b3b4e dc7cbc3c 451cbb2b e0fe2902 f95708a3 64851527 f5f1adc8 31895d22 e82aaaa6 42b38ff8 b955b7b1 b74bb3fe 8f7e0757 ecef43db 66621561 cf600da4 d8def8e0 c362083d 5413eb49 ca595485 26e52b8f 1b9febf5 a191c233 49d84363 6a524bd2 8fe87051 4dd18969 7bc770f6 b3dc1274 db7b5d4b 56d396bf 1577a1b0 f4a225f2 af1c9267 18e5f406 04ef90b9 e400e4dd 3ab519ff 02baf43c eee08beb 378becf4 d7acf2f6 f03dafdd 75913319 1d1c40cb 74241921 93d914fe ac2a52c7 8fd50449 e48d6347 883c6983 cbfe47bd 2b7e4fc5 95ae0e9d d4d143c0 6773e314 087ee53f 9f73b833 0acf5d3f 3487968a ee53e825 15020301 0001a381 b23081af 300f0603 551d1301 01ff0405 30030101 ff300e06 03551d0f 0101ff04 04030201 06306d06 082b0601 05050701 0c046130 5fa15da0 5b305930 57305516 09696d61 67652f67 69663021 301f3007 06052b0e 03021a04 148fe5d3 1a86ac8d 8e6bc3cf 806ad448 182c7b19 2e302516 23687474 703a2f2f 6c6f676f 2e766572 69736967 6e2e636f 6d2f7673 6c6f676f 2e676966 301d0603 551d0e04 1604147f d365a7c2 ddecbbf0 3009f343 39fa02af 33313330 0d06092a 864886f7 0d010105 05000382 01010093 244a305f 62cfd81a 982f3dea dc992dbd 77f6a579 2238ecc4 a7a07812 ad620e45 7064c5e7 97662d98 097e5faf d6cc2865 f201aa08 1a47def9 f97c925a 0869200d d93e6d6e 3c0d6ed8 e6069140 18b9f8c1 eddfdb41 aae09620 c9cd6415 3881c994 eea28429 0b136f8e db0cdd25 02dba48b 1944d241 7a05694a 584f60ca 7e826a0b 02aa2517 39b5db7f e784652a 958abd86 de5e8116 832d10cc defda882 2a6d281f 0d0bc4e5 e71a2619 e1f4116f 10b595fc e7420532 dbce9d51 5e28b69e 85d35bef a57d4540 728eb70e 6b0e06fb 33354871 b89d278b c4655f0d 86769c44 7af6955c f65d3208 33a454b6 183f685c f2424a85 3854835f d1e82cf2 ac11d6a8 ed636a quit telnet timeout 5 ssh stricthostkeycheck ssh 192.168.1.0 255.255.255.0 inside ssh timeout 30 ssh version 2 ssh key-exchange group dh-group1-sha1 console timeout 0 dhcpd dns 8.8.8.8 8.8.4.4 dhcpd auto_config outside ! dhcpd address 192.168.1.2-192.168.1.254 inside dhcpd enable inside ! dhcpd address 192.168.2.2-192.168.2.254 dmz1 dhcpd enable dmz1 ! dhcprelay timeout 60 threat-detection basic-threat threat-detection statistics access-list no threat-detection statistics tcp-intercept dynamic-access-policy-record DfltAccessPolicy username cisco password $sha512$5000$G5B9+ZfYxXVvcUPZ67ndpg==$SzTisL+GxQG2Nr/K7hh9gA== pbkdf2 privilege 15 ! class-map inspection_default match default-inspection-traffic ! ! policy-map type inspect dns preset_dns_map parameters message-length maximum client auto message-length maximum 512 no tcp-inspection policy-map global_policy class inspection_default inspect dns preset_dns_map inspect ftp inspect h323 h225 inspect h323 ras inspect rsh inspect rtsp inspect esmtp inspect sqlnet inspect skinny inspect sunrpc inspect xdmcp inspect sip inspect netbios inspect tftp inspect ip-options inspect icmp ! service-policy global_policy global prompt hostname context call-home reporting anonymous Cryptochecksum:2cf585656729bff783f7247b760f1d15 : end Part 7: Corrective Steps for DMZ network ======================================== ASA5516X(config)# interface GigabitEthernet1/3 ASA5516X(config-if)# no shut ASA5516X(config-if)# exit ASA5516X(config)# write mem Building configuration... Cryptochecksum: 2cf58565 6729bff7 83f7247b 760f1d15 7170 bytes copied in 0.150 secs [OK] That's all. Regards, Mr. Turritopsis Dohrnii Teo En Ming Targeted Individual in Singapore Blogs: https://tdtemcerts.blogspot.com https://tdtemcerts.wordpress.com

1 0