[aprssig] APRS IS weirdness

[scott at opentrac.org]

Rogue forks of open source code might have the potential to introduce new
problems, but it'd be hard to get anything done in open source without them.
I'd never have gotten aprsd to run on my 64-bit Alpha if I didn't have
access to the source, and I'm sure supporting a small minority of 64-bit
users wasn't a high priority for the developers.

And for what it's worth, it doesn't take access to source code to make most
programs do bad things!

Scott
N1VG

-----Original Message-----
From: aprssig-bounces at lists.tapr.org
[mailto:aprssig-bounces at lists.tapr.org]On Behalf Of Steve Dimse
Sent: Sunday, February 27, 2005 2:44 PM
To: TAPR APRS Mailing List
Subject: RE: [aprssig] APRS IS weirdness


On 2/27/05 at 4:40 PM AE5PL Lists <HamLists at ametx.com> sent:

>Not from looking at the packet log I posted.  In any case, servers
>should not modify in any way the I-Field of a packet which is apparently
>occurring here.  This is why I used byte arrays instead of strings when
>working with packets when designing javAPRSSrvr.  Too many programming
>languages do "special" things with strings which can cause this type of
>problem.

aprsd certainly did this also, and its long deployment history makes the
main
fork an unlikely cause, it is possible someone modified the source code and
runs
it on one server causing the problem. An unspoken 'benefit' of open-source!

Steve K4HG

_______________________________________________
aprssig mailing list
aprssig at lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig