[routing-wg] request to enable ICMP echo-reply on rpki.ripe.net?
- Previous message (by thread): [routing-wg] request to enable ICMP echo-reply on rpki.ripe.net?
- Next message (by thread): [routing-wg] request to enable ICMP echo-reply on rpki.ripe.net?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Wed May 5 12:32:40 CEST 2021
Hi, On Wed, May 05, 2021 at 12:30:01PM +0200, Kurt Kayser wrote: > I understand your point. But there is really no big effort to check if > Port 873 is working: > > <host>nc -zvw100 rpki.ripe.net 873 > Connection to rpki.ripe.net 873 port [tcp/rsync] succeeded! > > Let's make a security comparison, if this is really a necessary feature? So where exactly is the *security* drawback of permitting ICMP echo? But yes, of course, we can all do tcpping instead - which is much more likely to have an adverse effect on the actual service... Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/routing-wg/attachments/20210505/fcf03bc6/attachment.sig>
- Previous message (by thread): [routing-wg] request to enable ICMP echo-reply on rpki.ripe.net?
- Next message (by thread): [routing-wg] request to enable ICMP echo-reply on rpki.ripe.net?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]