▲ 128 r/alaska
Somone should start a petition to ban political mail flyers
I've probably gotten 100 of them in the last week. they all go straight to the trash.
u/os2mac — 8 days ago
▲ 1 r/Starlink
What’s the process to upgrade an antenna on the same account?
I have a gen 2(I think) on a roam plan in an area with congestion fees. I’d like to upgrade to a mini for portability battery use etc . How do I replace my antenna on my account without getting charged congestion fees?
u/os2mac — 20 days ago
Curated map of RV campgrounds in South Central Alaska
From Talkeetna to Homer and Valdez to Anchor point and all points in between. If I've missed something (this is geared to RV's up to 30ft) please message me with the details and I'll add it. Have Fun camping!
https://www.google.com/maps/d/edit?mid=1qclLW5NaBK8kY8HPCGtjQ7p6DuVSh9U&usp=sharing
u/os2mac — 2 months ago
▲ 0 r/ADSB
PiAware / FlightAware apt repo package still generates an HTTP source
I noticed that flightaware-apt-repository 1.3 on Debian Bookworm generates
this apt source:
URIs: http://apt.svc.flightaware.com/piaware/release
Signed-By: /usr/share/keyrings/flightaware-archive-keyring.gpg
The repo is not unsigned. The InRelease file verifies against the packaged
FlightAware archive key, and apt-get update succeeds. The issue is that the
generated apt source still uses plain http://, then relies on the server
redirecting to HTTPS.
That is weaker than it needs to be. Apt signatures protect package/index
integrity, but HTTP still leaks repository access and depends on redirect
behavior. The package should emit
https://apt.svc.flightaware.com/piaware/release directly.
I also saw the repo metadata is co-signed by a second RSA key that is not
present in the installed keyring:
NO_PUBKEY B931BB28DE85F0DD
Apt accepts the repo because the installed FlightAware key has a valid
signature, but the extra missing-key signature is noisy and should either be
shipped in the keyring package or removed from the repo metadata.
One more hardening gap: the Release metadata does not include Valid-Until, so
clients cannot naturally detect stale replayed metadata. A local workaround is
to add Valid-Until-Max, but ideally FlightAware should publish Valid-Until.
Short-term local fix:
Types: deb
URIs: https://apt.svc.flightaware.com/piaware/release
Suites: bookworm
Components: piaware
Architectures: armhf arm64
Signed-By: /usr/share/keyrings/flightaware-archive-keyring.gpg
Valid-Until-Max: 2592000
Also disable the generated source by setting ENABLED=no in /etc/default/
flightaware-apt-repository, otherwise the package may regenerate the HTTP
source later.
u/os2mac — 3 months ago