[aprssig] Simple Network Paging Protocol to APRS Gateway

[Andrew P.]

One concern about this, is that it doesn't do any excuse at authentication to confirm the person sending a message is a licensed amateur radio operator, so it could allow unlicensed users to transmit to RF. The APRS-IS backbone's passcode mechanism may not be the strongest, but at least it slows down attackers a little bit and requires them to at least claim to be licensed. As this SNPP daemon is implemented now, it leaves the licensee of every transmitter this daemon can get to at risk.

Andrew, KA2DDO

Date: Wed, 17 Sep 2014 17:58:25 -0700
From: kennethfinnegan2007 at gmail.com
To: aprssig at tapr.org; kg4pid at yahoo.com
Subject: Re: [aprssig] Simple Network Paging Protocol to APRS Gateway

Turns out there was two bugs that Max managed to trip. 
* Putty seems to send new lines in separate TCP packets than the line before them, which broke my socket driver. 
* There was an off-by-one error in the argument parser for the PAGEr command. 
I've got quick hacks for both on the live server, but fixes to git are still in the works. 
Putty is a little tricky because it defaults to active telnet mode, so I think the best mode for putty is raw. 
Kenneth Finnegan
On Sep 17, 2014 3:31 PM, "Max Harper" <kg4pid at yahoo.com> wrote:
I may not have been holding my mouth right, but it kept disconnecting on me. Is 444 the port? I tried it using putty in telnet mode.
Max KG4PID
    
    
_______________________________________________

aprssig mailing list

aprssig at tapr.org

http://www.tapr.org/mailman/listinfo/aprssig




_______________________________________________
aprssig mailing list
aprssig at tapr.org
http://www.tapr.org/mailman/listinfo/aprssig
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20140917/2daad24e/attachment.html>