Order Tray | Contact Us | Home | SIG Lists

[aprssig] APRS<=>E-mail

Gregory A. Carter gcarter at openaprs.net
Mon Jan 5 17:36:27 UTC 2009


I believe you're absolutely correct here, the question becomes at what point
should it be cut off?

45 as Steve suggests, 128, 256?  Where?

Greg

NV6G
OpenAPRS.Net

On Mon, Jan 5, 2009 at 8:22 AM, Rusty Hemenway <nnn0fjk at gmail.com> wrote:

> I think a character count should be also be developed.  We don't want
> people
> sending 30 line email messages over APRS.
>
> -----Original Message-----
> From: aprssig-bounces at tapr.org [mailto:aprssig-bounces at tapr.org] On Behalf
> Of Ben Jackson
> Sent: Monday, January 05, 2009 8:11 AM
> To: aprssig at tapr.org; TAPR APRS Mailing List
> Subject: Re: [aprssig] APRS<=>E-mail
>
>
> On 1/5/2009, "Gregory A. Carter" <gcarter at openaprs.net> wrote:
>
>
> >If there is interest in this I'll whip something up and impliment it, let
> me
> >know on or off list...
>
> Since you asked... You're pretty much right on the money. Coming from an
> infosec standpoint, I think there should be a two-stage authentication
> for incoming e-mail:
>
> * User specifies what e-mail addresses can send him mail.
> * Authorized users need to enter a "password" in the subject line for
> each message.
>
> This way this snuffs any kind of "accidental" leakage of spam-ish
> material onto the APRS network.
>
> ~Ben
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.tapr.org/pipermail/aprssig/attachments/20090105/02c89ee7/attachment.htm 


More information about the aprssig mailing list