17 Feb
2021
17 Feb
'21
10:34 a.m.
Le 17/02/2021 à 11:16, Rob PE1CHL via 44Net a écrit :
When I get a request like "I am Rob PE1CHL and I
want some addresses
to use on 44Net" there is no way for me to really verify that this
mail is really coming from a licensed operator, and even less to
verify that he keeps that license during the time he can still use
that address.
Maybe it's just a scale problem ? I don't have this one, because I'm
living on a tiny island, and I do know every ham involved in TKNet.
Maybe there should be more delegation, f/ex national coordinator
delegating sub-tasks to trusted local radio-clubs ? Not sure it would be
feasible everywhere, anyway...
If we setup a CA managed by ARDC, then ARDC would be in charge of
identity verification, and would deliver a (multi-purpose) certificate
directly to the end-user. Then, if someone gives you a trusted
certificate, you won't have to do further verification.
Sure, the admittance of only 44Net traffic (44.0.0.0/9
and 44.128.0.0/10) is a first step when guarding a system from access by just everyone,
and try to limit it to mostly radio amateurs with hopefully good intentions.
That's exactly what I meant. :-)
But I never would use it as a method to allow e.g. to
operate a transmitter (as was the example use case).
Of course, it does not replace application-level user authentication.
It's just a first level of filtering for applications that do not
support user authentication (yet).
73 de TK1B1