swinog

swinog@lists.swinog.ch

1 participants
2916 discussions

Start a nNew thread

(no subject)
by Roman Hochuli 18 Mar '20

18 Mar '20

FYI -- SwiNOG Organisation Roman Hochuli Board Member

1 0

SwiNOG #37 postponed due to COVID-19
by Roman Hochuli 12 Mar '20

12 Mar '20

Dear Community After careful consideration of risks and benefits and with a heavy heart, we have decided not to go forward with SwiNOG #37 in May 2020 due to the highly uncertain situation regarding the SARS-CoV-2 virus. The critical factors are the travelling, the restrictions placed on events by the government and first and foremost our concern for the health and safety of all our attendees and speakers. We are currently talking to our sponsors and partners to find a solution on how to proceed. We are very sorry we can't give you the great conference in May that many of you have been eagerly anticipating. We do hope you understand that this was, in every way, a very tough decision for us to make. We are trying to do the right thing by putting the health of all of us first. Instead of the two meetings in May and November, we plan for one big Event on Tuesday, September 8th, 2020. If you have any question do not hesitate to contact us. The SwiNOG Core Team -- SwiNOG Organisation Roman Hochuli Board Member

1 0

Looking for contact to: Green Abuse Desk regarding blacklisting caused by backscatter from email sent with fake envelope sender.
by Benoit Panizzon 10 Mar '20

10 Mar '20

Hi Hopefully somebody from the Green Abuse Desk is reading this and willing to contact me off-list regarding the blacklisting of green mail platform ip addresses because of a backscatter issue? I fear abuse(a)green.ch is handled by the enduser customer service as it looks they did not understand the issue. Yes, I would like to put the affected IP ranges into the SWINOG Whitelist to prevent them from getting blacklisted, but Green needs to tell me them. Just reacting to complaints and whitelisting every single ip address separately is a bit cumbersome. And no, the SPF record does not reveal those IP Addresses: hosting-ch.ch descriptive text "v=spf1 include:app.sgizmo.com ~all" app.sgizmo.com descriptive text "v=spf1 ip4:216.46.168.222 ip4:216.46.168.197 ip4:216.58.172.197 ip4:216.58.172.198 ip4:146.20.14.105 ip4:146.20.14.106 ip4:50.56.130.220 ip4:164.177.132.168 ~all" Last two IP addresses that got listed: 212.59.184.16 => elex-mail03.hosting-ch.ch 212.59.184.15 => elex-mail02.hosting-ch.ch. Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

1 0

Brocade NOS any?
by Guazzoni, Daniele [Global IT] 09 Mar '20

09 Mar '20

Does anyone have NOS 7.x.x for VDX 6740? We have a couple of those old VDX laying around and we would like to re-use them for a lab. The problem is that they are running 6.0.2 and we would need a 7.x.x firmware. Please contact me offline. Thanx Daniele Daniele Guazzoni Senior Network Engineer | Global IT O: +41 44 278 8754<tel:+41%2044%20278%208754> | Daniele.Guazzoni(a)solera.com<mailto:Daniele.Guazzoni@solera.com> | Solera.com<https://www.solera.com/> Solera | Elias‑Canetti‑Strasse 2 , Zürich Oerlikon , Zurich , 8050 , SWITZERLAND [cid:image304169.png@84B353CA.E694814D] ________________________________ "This e-mail and any attached files are confidential and intended for the named addressee(s) only. If you have received this message in error please notify the sender and delete the email immediately. The company does not conclude contracts by email and all negotiations are subject to written contract."

1 0

IANA AS Numbers Registry Update
by Selina Harrington 06 Mar '20

06 Mar '20

Hi, The IANA AS Numbers registry has been updated to reflect the allocation of the following block to AFRINIC: 328704-329727 Assigned by AFRINIC 2020-03-05 You can find the registry at: https://www.iana.org/assignments/as-numbers/ The allocation was made in accordance with the Policy for Allocation of ASN Blocks to Regional Internet Registries: https://www.icann.org/resources/pages/global-policy-asn-blocks-2010-09-21-en Best Regards, -- Selina Harrington Lead IANA Services Specialist

1 0

Fwd: [routing-wg] RPKI Outage Post-Mortem
by Massimiliano Stucchi 25 Feb '20

25 Feb '20

If you're not on the routing-wg mailing list, there's something you should know -------- Forwarded Message -------- Subject: [routing-wg] RPKI Outage Post-Mortem Date: Tue, 25 Feb 2020 15:12:15 +0100 From: Nathalie Trenaman <nathalie(a)ripe.net> To: routing-wg(a)ripe.net Dear colleagues, From Saturday 22 February at 08:24 (CET), any newly created, modified, or deleted ROAs (176 in total) could not be added to our publication server due to a disk problem. From that moment on, all the data was stored on the database, but the publication did not happen. The disk did not report any problems and, therefore, no engineer was alerted of this incident. Due to the disk problem, starting from Sunday 23 February at 09:10 (CET), our CRL expired and our repository could not be properly updated. This was reported to us on Monday 24 February at 11:44 (CET). Immediately, our engineers fixed the disk problem, however, since the CRL expired, all underlying objects also expired. Depending on the Relying Party software an operator used, this abnormal behaviour appeared differently. Initially, our engineers tried to do a full re-population of the RPKI repository, but unfortunately, this did not update the CRL in the validation tree. At 15:03 (CET), we performed a full CA key-roll, which was completed at 21:02 (CET) and resolved the problem. At 19:58 (CET), all objects in the backlog were published. We apologise for any inconvenience this may have caused and we are taking all the necessary steps to ensure this incident does not appear again in the future. Kind regards, Nathalie Trenaman Routing Security Programme Manager RIPE NCC

3 3

MELANI / GovCERT.ch
by Andreas Fink 19 Feb '20

19 Feb '20

Hello Swinog Users, Has anyone of you received some info from MELANI / GovCERT about some IoT vulnerability you might be exposed to? Well I did and I found very very strange things in this report. 1. The report contains only a timestamp, an IP address and a DNS name. Not which vulnerability, not potential loopholes, traces or ANYTHING useful to analyze whats happening. 2. The single IP address in the report is not in my network (I used to have that IP range in the past but I sold it in 2016. So long long ago. ) 3. The abuse email they sent the report to is not in the whois of that network. 4. The DNS name used in the report is not the reverse PTR of that IP. Nor does the forward DNS point to that IP. 5. The DNS name points to a host in my network but that host is definitively not a IoT device which has any kind of default password. Its a solid Linux machine with a up to date distribution with 2 usernames only on it with very secure passwords and only one specific application running which doesn't talk to outside my network at all. If that machine would have gotten hacked, it would surprise me very much. At least I have found nothing unusual on that IP. No unexpected network activity, CPU load, processes etc. So MELANI tells me my big fat Linux server is now a IOT device which has default passwords and I should simply do a factory default (and by doing this erase terabytes of data). I should look for "_SOMETHING_" without specifying it on SOME IP I don't own. And they address such a report to me while I am not the abuse contact of this SOME_IP. Furthermore SOME_IP looked not being reachable anyway when I tested. So the report contains ZERO usable information. The only thing which might not be wrong in the report is the timestamp (but thats not verified neither). I am shocked that a government entity which should take security seriously, is sending out such utter nonsense reports and wasting all our precious time. If they got such reports from 3rd parties it should contain verifiable information and USEFUL information. Apparently MELANI has become some kind of open CERT-SMTP relay without authentication. Let me know your experiences. Andrea Fink Fink Telecom Services --.- .-. - >> ENGLISH VERSION >> >> Dear Sir or Madam >> >> You are receiving this email because your email address is either registered as abuse contact for AS6775 in our system or because your email address is referenced as abuse contact for AS6775 at RIPE. >> >> The Reporting and Analysis Centre for Information Assurance (MELANI) has been informed by a partner about one of more devices (IoT - "Internet of Things") in your network that are likely to be compromised by Hackers and that are being used for malicious purpose. Attached to this email, you can find a list of all IP addresses that has been reported to us in the past 24 hours. >> >> The affected devices have most probably been compromised by hackers, likely due to the usage of a a default password. Therefore, hackers where able to install a malware (Mirai) on the said devices >> >> We therefore recommend you to identify the affected devices or customers, securing them and clean them up (e.g. by doing a factory reset). An overview of recommendations concerning IoT devices can be found on our website: >> >> Security in the internet of things (IoT): >> https://www.melani.admin.ch/iotsecurity <https://www.melani.admin.ch/iotsecurity>

3 2

Invitation for Public Policy Workshop in Bern 26.2.
by Michael Hausding 17 Feb '20

17 Feb '20

Dear SWINOG members Are you interested in the latest development on Dataprotection and E-ID in Switzerland? Before the ISOC-CH General Assembly on Feb 26 2020, we will host again an afternoon session on current Public Policy Topics with presentations and discussions on the following hot-topics in Swiss Politics: • Swiss E-ID (Electronic ID) A referendum to enforce a popular vote has just been successfully completed. More information here (German / French) Speakers: • André Golliez, Swiss Data Alliance / Zetamind AG • Jorgo Ananiadis, ISOC-CH / Piratenpartei • Revision of Swiss Data Protection Legislation The Legislation on Swiss Data Protection is currently under revision with the National Parliament. There are several concerns, e.g. on profiling. More information here (German only). Speaker: • lic. iur. Viktor Györffy, Digitale Gesellschaft / Advokaturbüro Peyrot, Schlegel & Györffy Registration and more information is available here: https://www.isoc.ch/events/policy-workshop-and-discussions-2020 Michael — Michael Hausding Chair ISOC Switzerland Chapter michael.hausding(a)isoc.ch https://isoc.ch

1 0

Telegram group
by Massimiliano Stucchi 17 Feb '20

17 Feb '20

Hi everyone, I created a telegram group for Swinog. It is meant to be a place to have discussions that are more informal than what you could have on the mailing list or simply for something more interactive. The link to join is https://t.me/SWINOG I've created a similar group for ITNOG almost two years ago and it proved to be a good initiative, now with about 450 members and with daily discussion on different topics. Maybe we can make it happen also for Swinog. Keep in mind this is just a personal initiative and not an official one from Swinog. If it works out and it's positive, we'll see if we can make it more official. If you have any question or comment, please feel free to approach me. Ciao! -- Massimiliano Stucchi MS16801-RIPE Twitter/Telegram: @stucchimax

10 13

RIPE Atlas probes as SW
by Steven.Glogger＠swisscom.com 14 Feb '20

14 Feb '20

Hi There Just saw this post by RIPE: https://labs.ripe.net/Members/alun_davies/ripe-atlas-software-probes RIPE Atlas probes are now available as software, offering future hosts a new way to help build the RIPE Atlas network. While not a replacement for their hardware counterparts, software probes will improve coverage by bringing RIPE Atlas to new and previously hard-to-reach places. How cool is that?! 😊 greetings -steven

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog