Paul E Condon wrote:
> I go into this seeming unnecessary detail because the behavior ot ssh
> in this environment is very strange:
I think it makes sense and can be explained.
> Sitting at Big, logged in as user pec, I can:
>
> connect to pec@gq without giving any password
> connect to root@gq
Quoting Paul E Condon (pecon...@mesanetworks.net):
> I agree with your reasoning, But I am having a problem on which I need help:
>
> I have three computers, Big, Dl2, and Gq. Big is the computer at which I sit
> when I reading this list and other user-type activities. The other two I use
> server
On 20150513_1117+0100, Jonathan Dowland wrote:
> On Tue, May 12, 2015 at 12:36:15PM -0400, Eike Lantzsch wrote:
> > I put more trust into the OpenBSD/OpenSSH developers. Apparent and not-so-
> > apparent bugs ought to be reported to them IMHO. That way an excellent
> > product
> > may become even
On Tue, May 12, 2015 at 12:36:15PM -0400, Eike Lantzsch wrote:
> I put more trust into the OpenBSD/OpenSSH developers. Apparent and not-so-
> apparent bugs ought to be reported to them IMHO. That way an excellent
> product
> may become even better.
I'd likewise stick with openssh personally, but
On Tuesday 12 May 2015 09:04:36 Paul E Condon wrote:
> By accident, while struggling with a number of problems
> in my pure Jessie home LAN, I came across some Debian
> packages which I had no clue existed. They are:
>
> lsh-client
> lsh-server
> lsh-utils
>
> The short descriptions in the aptitu
By accident, while struggling with a number of problems
in my pure Jessie home LAN, I came across some Debian
packages which I had no clue existed. They are:
lsh-client
lsh-server
lsh-utils
The short descriptions in the aptitude display describes them as a new
implementation of the whole ssh secu
6 matches
Mail list logo
