<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">This is a wide open space of issues.
The fact that licensing, all over the world, is based on pieces of
paper which can't be validated except through extremely laborious
attempts at identity tracking and investigation is at the root of
the problems. One of the things that could be done, would be to
use a certificate based system. But, we'd need a "mediator"
service that would allow Amateur radio operators to prove the
identity to set up and account, and then receive a signed,
public/private key pair. These apps would then require you to
provide your identifying login and password to that site, and they
would get your key. Then, they could check that key for
revocation by the mediator to control their behavior.
Applications, would open a socket connection to viable internet
services, and authenticate. Only services possessing an SSH key
generated by the mediator would be viable services to connect to.
Then, the path to RF could be "validated" by the servers, so that
our iGate's would only connect to "viable" services for accepting
internet traffic, and know that it came from a licensed operator.<br>
<br>
Anyone want to start a new business to help all of us end up with
a chance to have a secure internet to RF and back path? Sure it
would take some administration. But, I'd be willing to pay a
yearly fee to be able to have a working RF to internet to RF path
around the world. That would be a great thing for many reasons.<br>
<br>
Gregg Wonderly<br>
W5GGW<br>
<br>
On 3/14/2013 2:57 PM, Samúel Úlfr Þór Guðjónsson wrote:<br>
</div>
<blockquote
cite="mid:CAKkFkxHpUzC-ucwFuSnSZPcDsE_p3NBY9tC6yR8nuc74si1ObQ@mail.gmail.com"
type="cite">Thanks for the quick response on this matter.<br>
While not implying that iAPRS should be closed upon. I'd guess
that more hams are using that application than pirates.<br>
Hand picking one and one is probably the only solution for now,
but only postpones the problem.<br>
<br>
Hopefully this wont get too widespread, but with the smartphone
market growing and the ease of getting passcodes (there's even a
website offering a passcode generator), I'm afraid this could grow
into a bigger problem.<br clear="all">
<div><br>
73 de TF2SUT - Samúel<br>
</div>
<br>
<br>
<div class="gmail_quote">On 14 March 2013 18:16, Gregory A. Carter
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:gcarter@openaprs.net" target="_blank">gcarter@openaprs.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
iAPRS is a third party app that uses our DCC interface.
Ultimately<br>
I'll take responsibility to disable it's broadcasting through
us. We<br>
use direct email/password accounts locked to callsigns and
typically<br>
try to spot bunk calls but missed this one.<br>
<br>
The account was created yesterday and verified today before it
started<br>
beaconing so it's only been active for 24 hours.<br>
<br>
Greg<br>
<div>
<div class="h5"><br>
On Thu, Mar 14, 2013 at 11:53 AM, Samúel Úlfr Þór
Guðjónsson<br>
<<a moz-do-not-send="true"
href="mailto:tf2sut@ulfr.net">tf2sut@ulfr.net</a>>
wrote:<br>
> Hi all, I'm new to this post list.<br>
><br>
> I have not been very worried of "pirates" using APRS
IS, but today I noticed<br>
> one locally on <a moz-do-not-send="true"
href="http://aprs.fi" target="_blank">aprs.fi</a> using
iAPRS for Apple's IOS.<br>
> As it is only on Internet I'm not that worried,
however, there is a<br>
> possibility that this information could go to a TX
Igate which would<br>
> broadcast the information, being either positon or
messages, as position is<br>
> always gated after a message. That'd make the
operator of the TX igate<br>
> responsable for illegal use of the amateur frequency.
Over here this is a<br>
> great concern, as connecting internet and RF is on a
very gray zone, legally<br>
> speaking.<br>
><br>
> The "pirate":<br>
> <a moz-do-not-send="true"
href="http://aprs.fi/info/a/STEBBI-9" target="_blank">http://aprs.fi/info/a/STEBBI-9</a><br>
><br>
> Now what can be done about this?<br>
> I suppose doing modification on all the TX igates to
do some verification of<br>
> the sender of the message, but it could be quite
painful.<br>
><br>
><br>
> Not very familiar with iAPRS, it seems that it's just
a frontend for<br>
> OpenAPRS, and it seems to me that it does not do any
passcode verification.<br>
> Anyone correct me if I'm wrong. Now I know that
passcode verification is not<br>
> really that much of a verification, but having a bad
verification is the<br>
> better of worse.<br>
><br>
> I'm quite sure that there are other countries than
Iceland who are running<br>
> on gray zone concerning RF to IS and vica versa
traffic. Apperantly France<br>
> has the same concerns, and pirates on APRS-IS is not
helping.<br>
><br>
> So, what should I do? Try to implement blacklisting
on all the TX Igates<br>
> over here? (Thankfully, they are not that many at the
moment) or just stop<br>
> all the TX IGates? That would kind of ruin one of a
very great usable<br>
> feature in APRS.<br>
><br>
> Sorry if this post sounds abit confusing, I'm a
little puzzled about this<br>
> matter.<br>
><br>
> 73 de TF2SUT - Samúel<br>
><br>
</div>
</div>
> _______________________________________________<br>
> aprssig mailing list<br>
> <a moz-do-not-send="true" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br>
> <a moz-do-not-send="true"
href="http://www.tapr.org/mailman/listinfo/aprssig"
target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br>
><br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
--<br>
NV6G<br>
OpenAPRS.Net<br>
OpenAPRS iPhone Edition<br>
Find RC sites and weather in your area on iPhone/iPad with
WhereBRC<br>
_______________________________________________<br>
aprssig mailing list<br>
<a moz-do-not-send="true" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br>
<a moz-do-not-send="true"
href="http://www.tapr.org/mailman/listinfo/aprssig"
target="_blank">http://www.tapr.org/mailman/listinfo/aprssig</a><br>
</font></span></blockquote>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<br>
</body>
</html>