ssh -o stricthostkeychecking=no works.
There's no ~/.ssh/config
grep Strict /etc/ssh/ssh_config
# StrictHostKeyChecking ask
but it doesn't ask:
ssh new-gateway
@@@
@WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
On 2/17/19 10:24 PM, sean darcy wrote:
> ssh -o stricthostkeychecking=no works.
>
> There's no ~/.ssh/config
>
> grep Strict /etc/ssh/ssh_config
> # StrictHostKeyChecking ask
>
> but it doesn't ask:
>
> ssh new-gateway
> @@@
> @WARNING:
On Sun, 17 Feb 2019 09:24:53 -0500
sean darcy wrote:
> any help appreciated
I gave up trying to deal with these issues because
our lab at work is full of machines being re-genned
every few weeks, so I wrote a little perl script
I could run before ssh to update the ~/.ssh/known_hosts
file by runni
On Fri, 2019-02-15 at 15:48 -0500, John Harris wrote:
> The only way that I personally know how to do with is by setting a
> system wide
> proxy. If you could find the process GNOME uses to sync CalDAV and
> CardDAV,
> you could `torify` it. There is no built-in way to do this in GNOME,
> at leas
sean darcy, 17.02.19 15:24 +0100:
> ssh -o stricthostkeychecking=no works.
>
> There's no ~/.ssh/config
>
> grep Strict /etc/ssh/ssh_config
> # StrictHostKeyChecking ask
>
> but it doesn't ask:
>
> ssh new-gateway
> @@@
> @WARNING:
Allegedly, on or about 15 February 2019, Turritopsis Dohrnii Teo En
Ming sent:
> 3. Cloud storage provider must not be a fly-by-night company, that
> is, it will not suddenly close down the next day.
You can't rely on the permanent existence of ANY external service. At
any time they might decide
Allegedly, on or about 16 February 2019, Beartooth sent:
> $ uname -a
> Linux 2.6.32-042stab134.3 #1 SMP Sun Oct 14 12:26:01 MSK 2018 x86_64
> x86_64 x86_64 GNU/Linux
>
> Is something there the name of a distro?? (I've forgotten
> the proper command, with 'release' in it,for asking a rem
On Sat, 16 Feb 2019 20:37:02 -0500, Matthew Miller wrote:
> Any distro using systemd (so, any modern mainstream distro) will have
> /etc/os-release. You can do `cat /etc/os-release`, but one of the really
> nice things is that this is also a machine-readable file. You can do
>
> $ source /etc/o
On Sun, Feb 17, 2019 at 08:15:03PM -, Beartooth wrote:
> On Sat, 16 Feb 2019 20:37:02 -0500, Matthew Miller wrote:
>
> > Any distro using systemd (so, any modern mainstream distro) will have
> > /etc/os-release. You can do `cat /etc/os-release`, but one of the really
> > nice things is that th
On Sun, 17 Feb 2019, Tim wrote:
> Allegedly, on or about 16 February 2019, Beartooth sent:
>> $ uname -a
>> Linux 2.6.32-042stab134.3 #1 SMP Sun Oct 14 12:26:01 MSK 2018 x86_64
>> x86_64 x86_64 GNU/Linux
>>
>> Is something there the name of a distro?? (I've forgotten
>> the proper comman
On 17/02/2019 20:33, Fred Smith wrote:
On Sun, Feb 17, 2019 at 08:15:03PM -, Beartooth wrote:
On Sat, 16 Feb 2019 20:37:02 -0500, Matthew Miller wrote:
Any distro using systemd (so, any modern mainstream distro) will have
/etc/os-release. You can do `cat /etc/os-release`, but one of the re
Strange: after my last post, I discovered that in Gnome, I could no
longer access ibus.
> ...you may have to run "im-chooser" in a terminal on KDE before
> ibus is made the default input method
If you're implying im-chooser doesn't work in Gnome, you're right.
In KDE, it partially worked.
On 2/18/19 7:54 AM, home user via users wrote:
> Strange: after my last post, I discovered that in Gnome, I could no longer
> access ibus.
>
> > ...you may have to run "im-chooser" in a terminal on KDE before
> > ibus is made the default input method
>
> If you're implying im-chooser doesn't w
13 matches
Mail list logo
