17 Apr
2014
17 Apr
'14
8:35 p.m.
On Apr 17, 2014, at 1:50 PM, Don Fanning <don(a)00100100.net> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On Thu, Apr 17, 2014 at 10:06 AM, Javier Henderson (javier) <
javier(a)cisco.com> wrote:
How do I know the packet you are sending me is really a LOTW public
certificate? You could be sending secrets against J. Edgar Hoover!
You’d validate it the same way you’d validate the amazon.com SSL certificate.
One
problem that comes to mind is SSL wouldn't be allowed on 44net unless
everyone has the private key and I doubt ARRL will release that.
Why would you need the private key to the ARRL CA root certs?
No, I do know the signature packet itself is just data
or a hash of public
data. Problem is that it is - in essence - encrypted data in which you
only share part of it. The just because it could be argued that it skirts
the legality of the law does it mean that it is clear of the meaning of the
law.
I’m not sure I’m following you here...
73,
-jav k4jh