On Sun, 10 Mar 2019 18:55:29 -0400, Rich Freeman wrote:
> > Mar 11 00:33:37 localhost ntpdate[4553]: Exiting, name server cannot
> > be used: Temporary failure in name resolution (-3)11 Mar 00:33:37
> > ntpdate[4553]: name server cannot be used: Temporary failure in name
> > resolution (-3)
>
>
On Monday, 11 March 2019 05:41:19 GMT Philip Webb wrote:
[snip ...]
> However, I've tried to insert an instruction in config files,
> but nothing changes after a reboot.
> I've tried adding to ~/.ssh/config & /etc/ssh/ssh_config :
>
> Host 128.100.160.1
> KexAlgorithms +diffie-hellman-gr
On Mon, 11 Mar 2019 01:41:19 -0400, Philip Webb wrote:
> That forum contains a solution :
>
> ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 123.123.123.123
>
> That gets me thro' & I can do my work there.
>
> > Enable legacy and possible less secure key exchange formats and
> > ciphers only
On Monday, 11 March 2019 08:31:33 GMT Neil Bothwick wrote:
> On Mon, 11 Mar 2019 01:41:19 -0400, Philip Webb wrote:
> > That forum contains a solution :
> > ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 123.123.123.123
> >
> > That gets me thro' & I can do my work there.
> >
> > > Enable lega
On Mon, 11 Mar 2019 08:43:52 +, Mick wrote:
> > Try without the +, that works for me here. I have an appliance that
> > uses outdated algorithms and this config works for me
> >
> > Host 1.2.3.4
> > Ciphers 3des-cbc
> > KexAlgorithms diffie-hellman-group1-sha1
> > HostKeyAlgorithm
190311 Neil Bothwick + Mick wrote:
NB> Try without the +, that works for me here. I have an appliance
> that uses outdated algorithms and this config works for me
> Host 1.2.3.4
> Ciphers 3des-cbc
> KexAlgorithms diffie-hellman-group1-sha1
> HostKeyAlgorithms ssh-dss
I tried adding the
On 11/3/19 5:23 pm, Philip Webb wrote:
> 190311 Neil Bothwick + Mick wrote:
> NB> Try without the +, that works for me here. I have an appliance
>> that uses outdated algorithms and this config works for me
>> Host 1.2.3.4
>> Ciphers 3des-cbc
>> KexAlgorithms diffie-hellman-group1-sha1
>>
Hi,
eix-sync and eix-diff reports (newer) packages from disabled overlays
(via layman -D ...).
How can I tell eix to ignore these?
I'm using eix GIT from 2019/03/06.
Many thanks for a hint,
Helmut
On Mon, 11 Mar 2019 05:23:36 -0400, Philip Webb wrote:
> NB> That's how I read it, but it says it appends to the list,
> > so this is the last option tried,
> > while an earlier one could possibly be triggering the failure.
> > With + would be better, but it would be worth trying without.
>
> I
190311 Neil Bothwick wrote:
> Have you run ssh with -v
> to see what configuration options it is reading from where.
> Bear in mind that ssh stops at the first matching host definition,
> so if you have a "host *" in your config, it must be last.
This is what I get :
522: ~> ssh -v
OpenSSH_7
On Mon, 11 Mar 2019 09:08:14 -0400, Philip Webb wrote:
> 190311 Neil Bothwick wrote:
> > Have you run ssh with -v
> > to see what configuration options it is reading from where.
> > Bear in mind that ssh stops at the first matching host definition,
> > so if you have a "host *" in your config, it
On 2019.03.10 22:50, tu...@posteo.de wrote:
Hi,
I've got this this morning:
strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment -R
.GCC.command.line -R .note.gnu.gold-version
/usr/lib64/libmxml.so.1.6
* checking 9 files for package collisions
* This package will overwrite one o
On Monday, 11 March 2019 13:42:14 GMT Neil Bothwick wrote:
> On Mon, 11 Mar 2019 09:08:14 -0400, Philip Webb wrote:
> > 190311 Neil Bothwick wrote:
> > > Have you run ssh with -v
> > > to see what configuration options it is reading from where.
> > > Bear in mind that ssh stops at the first matchin
On Mon, 11 Mar 2019 16:06:59 +, Mick wrote:
> > It shows that ssh is reading your config file, but not picking up the
> > options for this host. I would expect to see something like
> >
> > debug1: Reading configuration data /home/nelz/.config/ssh
> > debug1: /home/nelz/.config/ssh line N: Ap
On March 10, 2019 1:24:14 PM UTC, Dan Johansson wrote:
>After updating a server from kernel-4.14.83 to 4.19.27-r1 (same problem
>
>with 4.19.23) the server will not boot.
>
>Grub starts fine and I can select the new kernel.
>The kernel starts booting and after mounting "/" and "/usr" (this is a
>
On 11.03.19 20:55, J. Roeleveld wrote:
On March 10, 2019 1:24:14 PM UTC, Dan Johansson wrote:
After updating a server from kernel-4.14.83 to 4.19.27-r1 (same problem
with 4.19.23) the server will not boot.
Grub starts fine and I can select the new kernel.
The kernel starts booting and after m
On Monday, 11 March 2019 17:34:20 GMT Neil Bothwick wrote:
> On Mon, 11 Mar 2019 16:06:59 +, Mick wrote:
> > > It shows that ssh is reading your config file, but not picking up the
> > > options for this host. I would expect to see something like
> > >
> > > debug1: Reading configuration data
On Mon, 11 Mar 2019 21:35:54 +, Mick wrote:
> > > > It shows that ssh is reading your config file, but not picking up
> > > > the options for this host. I would expect to see something like
> > > >
> > > > debug1: Reading configuration data /home/nelz/.config/ssh
> > > > debug1: /home/nelz/.c
Am Montag, 11. März 2019, 10:48:38 CET schrieb Helmut Jarausch:
> Hi,
>
> eix-sync and eix-diff reports (newer) packages from disabled overlays
> (via layman -D ...).
> How can I tell eix to ignore these?
>
> I'm using eix GIT from 2019/03/06.
>
> Many thanks for a hint,
> Helmut
Did you alread
Am Montag, 11. März 2019, 23:35:35 CET schrieb Marc Joliet:
> Am Montag, 11. März 2019, 10:48:38 CET schrieb Helmut Jarausch:
> > Hi,
> >
> > eix-sync and eix-diff reports (newer) packages from disabled overlays
> > (via layman -D ...).
> > How can I tell eix to ignore these?
> >
> > I'm using ei
20 matches
Mail list logo
