Hello,
On Thu, Jul 17, 2008 at 11:11 PM, Stroller
<[EMAIL PROTECTED]> wrote:
> I keep the following command in my .bash_profile:
>
> alias ssg="ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/
> dev/null"
Ah. That's very useful.
Thanks for sharing!
--
Regards
Torfinn Ingolfsen
I keep the following command in my .bash_profile:
alias ssg="ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/
dev/null"
I then `ssg` to hosts which are liable to have changing ssh keys.
Joachim Steiger's suggestion, limiting relaxed HostKeyChecking to a
single IP is less useful to m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> My local network is 192.168.0.0/24, so it makes a problem to route to
|> Freerunner default IP... I use this script as root on my Fedora host
|> laptop to take care of assigning an IP and hst route and when
> My local network is 192.168.0.0/24, so it makes a problem to route to
> Freerunner default IP... I use this script as root on my Fedora host
> laptop to take care of assigning an IP and hst route and whenever I hook
> a Freerunner up
why don't you simple change the ip?
_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| pay attention that if you ssh to that other computer you'll get the same
| warning.
|
| note: 192.168.0.202 is IANA private use, so it's normal to have
| duplicates of that IP among different
| network
My
>
> Somewhere on the wiki is a description how to shut this
> behaviour off,
> but I hope nobody will ever inactivate this vigilance.
>
> Thanks for the explanation...
>
> Regards...
>
I have to add that Joachim Steigers suggestion is very okay too, as it
only
On Fri, Jul 18, 2008 at 12:56 AM, Marcus Bauer <[EMAIL PROTECTED]>
wrote:
>
> Paul Bonser answered already with the fix.
yeah , it solved the problem.
>
>
> I'll add the reason: whenever you connect to an unknown system, you are
> asked if you want to accept the key like this:
>
> -
Paul Bonser answered already with the fix.
I'll add the reason: whenever you connect to an unknown system, you are
asked if you want to accept the key like this:
-
The authenticity of host '192.168.0.202 (192.168.0.202)' can't be
es
for people who often reflash and thus have new host keys on their mokos
i can share this ~/.ssh/config snippet:
Host moko
HostName 192.168.0.202
StrictHostKeyChecking no
UserKnownHostsFile /dev/null
User root
the result is that one can just 'ssh moko' press return and be done
(logged in) every ti
Hi,
You need the remove the old host identification in your ~/.ssh/known_hosts
/Johan
On Thu, Jul 17, 2008 at 21:10, saurabh gupta <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I followed the steps given in "Getting started with freerunner" on wiki to
> install the sample application in my free runne
On Thu, Jul 17, 2008 at 2:10 PM, saurabh gupta
<[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I followed the steps given in "Getting started with freerunner" on wiki to
> install the sample application in my free runner. I started the FR normally
> and then connect it through a usb cable. However after
Hi all,
I followed the steps given in "Getting started with freerunner" on wiki to
install the sample application in my free runner. I started the FR normally
and then connect it through a usb cable. However after executing the
command :
sudo ifconfig usb0 192.168.0.200 netmask 255.255.255.0
whe
12 matches
Mail list logo
