M Taylor wrote:
>
> Now I would be interested to see if a secure (cryptographic) authenication
> method would be acceptable - no data is encrypted just a secure
> "handshake" to validate a remote operator's identity, perhaps using
> public key digital signatures.
>
You could use OPIE for this.
On Tue, Sep 28, 1999 at 11:12:11AM -0300, M Taylor wrote:
> To control access, I would make certain that you use a recent kernel,
> 2.2.12 works well for me, and have all necessary distribution's
> patches and updates installed. You can use tcp_wrappers for "course"
> access control such 44.*.*.*
On Tue, Sep 28, 1999 at 12:58:00PM +0100, Dirk Koopman wrote:
> What they are actually afraid of, reading between the lines, is
> steganography: ie. hiding messages inside of largish blocks of binary data,
> which exactly what a public key really is.
No, that's winnowing.
===
On Tue, 28 Sep 1999, Andrew Benham wrote:
> On Mon, 27 Sep 1999, M Taylor wrote:
>
> > In Canada an encrypted telnet, ssh, SSL, or encrypted SMTP or POP3 would
> > likely violate Radiocommunication Regulations section 47b:
> >
> > 47. A person who operates radio apparatus that is licensed in th
Greetings, I and many others have been working on a SANS document that talks about a
step
by step instruction on securing a Linux server. This may be of interest to some of you
especially those who are installing a Linux server for the first time on the inet.
I am not sure when it will be relea
On 28-Sep-99 Andrew Benham wrote:
> The encryption schemes around these days use published codes/ciphers,
> it is merely the keys which are secret. I don't know whether this
> is a legal nicety or not - you decide.
>
It doesn't really matter, any kind of public key cryptography whether used
for
On Mon, 27 Sep 1999, M Taylor wrote:
> In Canada an encrypted telnet, ssh, SSL, or encrypted SMTP or POP3 would
> likely violate Radiocommunication Regulations section 47b:
>
> 47. A person who operates radio apparatus that is licensed in the amateur
> radio service may only
> ...
> (b) use a co
On Mon, 27 Sep 1999, M Taylor wrote:
> Now I would be interested to see if a secure (cryptographic) authenication
> method would be acceptable - no data is encrypted just a secure
I suspect an SSH connection using "NONE" as the cryptographic method would
suite. I think it still authenticates u
On Mon, 27 Sep 1999, M Taylor wrote:
> Now I would be interested to see if a secure (cryptographic) authenication
> method would be acceptable - no data is encrypted just a secure
> "handshake" to validate a remote operator's identity, perhaps using
> public key digital signatures.
When I consid
On Tue, 28 Sep 1999, Robert Schelander wrote:
> Are there any possibilities to do encrypted telnet sessions? Encypted SMTP,
> POP3?
In Canada an encrypted telnet, ssh, SSL, or encrypted SMTP or POP3 would
likely violate Radiocommunication Regulations section 47b:
47. A person who operates radio
At 00:11 9/28/99 +0200, Robert Schelander wrote:
>I would be glad if you could tell me about the steps you've taken on your
>TCP/IP servers.
We use the security features built into TNOS on our gateway. It allows
different default privs based upon being a 44-net, non-44net, and local
ax25 user.
De
ptember 27, 1999 2:43 PM
Subject: Security for amateurradio TCP/IP server!
>Hi!
>
>I would be glad if you could tell me about the steps you've taken on your
>TCP/IP servers.
>Automatic creation of users at their first login would be desirable, but I'm
>not
>sure if it is a go
Hi!
I would be glad if you could tell me about the steps you've taken on your
TCP/IP servers.
Automatic creation of users at their first login would be desirable, but I'm
not
sure if it is a good idea that anybody automaticalls gets telnet access.
Just in case I want to do so, how to keep the sys
13 matches
Mail list logo
