16 Feb
2021
16 Feb
'21
4:45 a.m.
On 2/16/21 9:42 AM, Toussaint OTTAVI via 44Net wrote:
Le 09/02/2021 à 00:01, Cliff Sojourner via 44Net a écrit :
Well, I don't think network level security is usable for that. Right now, half the
users do not even make their reverse-DNS working, so you cannot tell whom the incoming
connects are coming from.
And when that would be resolved, it is much too easy to spoof.
This should be solved by validating licensed hams and assigning them an authentication
token, like a certificate or for simpler cases a username/password.
As we have discussed before, we certainly could use a well defined way to do that
validation and hand out the tokens.
But once you have that, it would be usable just as well over the plain internet. As LOTW
and Echolink already do.
Rob
We already have hundreds of SDRs available via
IP. One aggregation is athttp://websdr.org/
Don't think only in terms of bandwidth, but also in terms of services. This is a
perfect example of things that would benefit from a "New Generation" 44net
connection. F/ex, Internet users could be allow to listen only, while 44net users could be
allowed (under some circumstances) to transmit, too.
That's a common problem for people who build Internet-related applications (such as
Echolink, DMR, etc...) : How to ensure users coming from Internet are legitimate ham radio
operators ? Everybody adopts its own solution, with more or less problems, but always with
a huge overhead.
If we can provide a network-level authentication on 44net (still to be defined), then,
the application developers would just have to focus on their app, and not about user
authentication. Checking whether an user is a legitimate ham radio or not would be as
simple as checking if the source IP is in the 44net range...