[aprssig] Escaping \r\n in packets for APRS-IS

[spam8mybrain]

Sounds like a plan. Again, that Unicode substitution I do is only for local screens, so that the user doesn't get an uninterpretable rectangular block for a non-printable character.
    
I'll make the change in my next build.Andrew, KA2DDOauthor of YAAC

-------- Original message --------
From: "Iain R. Learmonth" <irl at hambsd.org> 
Date: 5/8/20  10:42  (GMT-05:00) 
To: aprssig at lists.tapr.org 
Subject: Re: [aprssig] Escaping \r\n in packets for APRS-IS 

Hi,On 08/05/2020 15:37, spam8mybrain wrote:> Uh, oh. Not cool. I just checked my APRS-IS and SSL-APRS-IS port drivers> in YAAC, and I send the packet as-is byte-for-byte, assuming it is only> one line with no embedded control characters.Ooops.> Hmmm... in one of my displays, I replace all the ASCII control> characters (byte values 0x00 through 0x1F) with their corresponding> display glyphs in Unicode (\u2400 through \u241F), so they can be> interpreted properly by the user. But that doesn't fix I-gating.That would break MIC-E packets, I'm going with what Dire Wolf and Xastirdo which is to treat either a \r or \n as the end of the packet iffound, and then do the normal checks before gating.It's only \r and \n that have special meaning to the server, all othercharacters are fine.Thanks,Iain MM0ROR.-- https://hambsd.org/_______________________________________________aprssig mailing listaprssig at lists.tapr.orghttp://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20200508/7af9e9d4/attachment.html>