some jurisdictions also require at least periodic
transmission of the operator's callsign.
Ongoing debate about whether the wifi SSID fulfills this sufficiently for the FCC
requirement...
Cliff K6CLS CM87
On September 28, 2023 7:11:31 PM PDT, Philip Paeps via 44net
<44net(a)mailman.ampr.org> wrote:
On 2023-09-27 17:22:47 (+0800), Peter Hannay via 44net
wrote:
In relation to general internet access you
prevent access to encrypted
services via traffic inspection or use a transparent proxy to strip
encryption upstream before it hits the radio link.
Some sites would break if they use HSTS, but many services would work just
fine.
You'd want to make sure users understand this though, as accessing anything
that requires a login would be a terrible idea.
One would hope that amateur RF users understand that there is no expectation of privacy on
amateur RF bands. Those users are expected to be licensed and understand the conditions
of their licence.
Just some thoughts I've had as I'm
planning to provide some limited access
to the internet via RF and want to make sure I'm doing things in a
completely above board manner.
Please do report on how well this ends up working. I've been thinking of setting this
up too.
With a lot of the public internet becoming end-to-end encrypted, I would expect to see
transparent proxies struggle to decrypt everything. Additionally, some jurisdictions also
require at least periodic transmission of the operator's callsign. Ideally, this
would be done by the client (e.g. by adding an X-HAM-OPERATOR: header to HTTP traffic),
but doing it in a proxy may be easier. Food for thought!
Philip VR2WTZ
--
Philip Paeps
Senior Reality Engineer
Alternative Enterprises
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org