On 25/07/17 16:32, Torbjorn Pettersson wrote:
Hello folks,
I came upon a weird problem with the resolver on Debian 8.
root@myserver:~# cat /etc/resolv.conf
search strul.nu
nameserver 192.168.10.20
nameserver 192.168.20.20
sortlist 192.168.20.0/255.255.254.0
root@myserver:~# grep -i hosts
Hello folks,
I came upon a weird problem with the resolver on Debian 8.
root@myserver:~# cat /etc/resolv.conf
search strul.nu
nameserver 192.168.10.20
nameserver 192.168.20.20
sortlist 192.168.20.0/255.255.254.0
root@myserver:~# grep -i hosts /etc/nsswitch.conf
hosts: files dns
root@my
Torbjorn Pettersson <[EMAIL PROTECTED]> writes:
> It seems like there just was an update of the ssh package from
> the sequrity team, which supposedly fixes the problem.
>
It didn't... It was linked to some version of libcrypto which
wasn't on my machine
Regards
Tobbe
It seems like there just was an update of the ssh package from
the sequrity team, which supposedly fixes the problem.
Regards
--
##
Torbjörn Pettersson # Email [EMAIL PROTECTED]
Vattugatan 5
"Jonathan D. Proulx" <[EMAIL PROTECTED]> writes:
> On Fri, Jan 19, 2001 at 03:54:36PM +0100, Torbjorn Pettersson wrote:
>
> : Are the server a sparc? It seems that the ssh package from the
> :security team is broken on sparc, at least it doesn't work for me
"John F. Davis" <[EMAIL PROTECTED]> writes:
> Hello
>
> I did a apt-get upgrade which restarted ssh and now I can't ssh into
> my box anymore. I keep getting a invalid password response.
>
> I can however login to the box via the console with the same
> password.
>
> What gives?
> --
> We hos
6 matches
Mail list logo