* Host authenticity failures
@ 2013-01-02 22:48 Thornburg, Christopher A
2013-01-05 2:50 ` Stewart, David C
0 siblings, 1 reply; 5+ messages in thread
From: Thornburg, Christopher A @ 2013-01-02 22:48 UTC (permalink / raw)
To: yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
I've started getting the following error from bitbake when it's trying to access my git server:
The authenticity of host '[<githost>]:<port>([<IP>]:<port>)' can't be established.
DSA key fingerprint is <blah>
I understand this error means that the server's key has probably changed, and I understand in general how to deal with this via SSH config. When I manually ssh'd to the server the first time after receiving the error, I got the same message, as expected. I entered "yes" and tried again to verify that the error went away. It did. I think ran bitbake again and got the same error. I changed my ~/.ssh/ssh_config file to disable StrictHostKeyChecking and still get the error.
Is bitbake somehow using different known_hosts and ssh_config files from the ones I use for interactive logins? Other ideas on how to resolve this?
[-- Attachment #2: Type: text/html, Size: 2872 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Host authenticity failures
2013-01-02 22:48 Host authenticity failures Thornburg, Christopher A
@ 2013-01-05 2:50 ` Stewart, David C
2013-01-05 2:52 ` Khem Raj
2013-01-07 21:48 ` Thornburg, Christopher A
0 siblings, 2 replies; 5+ messages in thread
From: Stewart, David C @ 2013-01-05 2:50 UTC (permalink / raw)
To: Thornburg, Christopher A, yocto@yoctoproject.org
Is this still a problem?
From: <Thornburg>, Christopher A <christopher.a.thornburg@intel.com<mailto:christopher.a.thornburg@intel.com>>
Date: Wednesday, January 2, 2013 2:48 PM
To: "yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>" <yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>>
Subject: [yocto] Host authenticity failures
I’ve started getting the following error from bitbake when it’s trying to access my git server:
The authenticity of host '[<githost>]:<port>([<IP>]:<port>)' can't be established.
DSA key fingerprint is <blah>
I understand this error means that the server’s key has probably changed, and I understand in general how to deal with this via SSH config. When I manually ssh’d to the server the first time after receiving the error, I got the same message, as expected. I entered “yes” and tried again to verify that the error went away. It did. I think ran bitbake again and got the same error. I changed my ~/.ssh/ssh_config file to disable StrictHostKeyChecking and still get the error.
Is bitbake somehow using different known_hosts and ssh_config files from the ones I use for interactive logins? Other ideas on how to resolve this?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Host authenticity failures
2013-01-05 2:50 ` Stewart, David C
@ 2013-01-05 2:52 ` Khem Raj
2013-01-07 21:48 ` Thornburg, Christopher A
1 sibling, 0 replies; 5+ messages in thread
From: Khem Raj @ 2013-01-05 2:52 UTC (permalink / raw)
To: yocto
On 01/04/2013 06:50 PM, Stewart, David C wrote:
> Is this still a problem?
>
> From: <Thornburg>, Christopher A <christopher.a.thornburg@intel.com<mailto:christopher.a.thornburg@intel.com>>
> Date: Wednesday, January 2, 2013 2:48 PM
> To: "yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>" <yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>>
> Subject: [yocto] Host authenticity failures
>
> I’ve started getting the following error from bitbake when it’s trying to access my git server:
>
> The authenticity of host '[<githost>]:<port>([<IP>]:<port>)' can't be established.
> DSA key fingerprint is <blah>
>
> I understand this error means that the server’s key has probably changed, and I understand in general how to deal with this via SSH config. When I manually ssh’d to the server the first time after receiving the error, I got the same message, as expected. I entered “yes” and tried again to verify that the error went away. It did. I think ran bitbake again and got the same error. I changed my ~/.ssh/ssh_config file to disable StrictHostKeyChecking and still get the error.
>
> Is bitbake somehow using different known_hosts and ssh_config files from the ones I use for interactive logins? Other ideas on how to resolve this?
>
bitbake is not hosted on yp dot org but on oe dot org
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Host authenticity failures
2013-01-05 2:50 ` Stewart, David C
2013-01-05 2:52 ` Khem Raj
@ 2013-01-07 21:48 ` Thornburg, Christopher A
1 sibling, 0 replies; 5+ messages in thread
From: Thornburg, Christopher A @ 2013-01-07 21:48 UTC (permalink / raw)
To: Stewart, David C, yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
Yes...this is still happening. :(
From: Stewart, David C
Sent: Friday, January 04, 2013 7:50 PM
To: Thornburg, Christopher A; yocto@yoctoproject.org
Subject: Re: [yocto] Host authenticity failures
Is this still a problem?
From: <Thornburg>, Christopher A <christopher.a.thornburg@intel.com<mailto:christopher.a.thornburg@intel.com>>
Date: Wednesday, January 2, 2013 2:48 PM
To: "yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>" <yocto@yoctoproject.org<mailto:yocto@yoctoproject.org>>
Subject: [yocto] Host authenticity failures
I've started getting the following error from bitbake when it's trying to access my git server:
The authenticity of host '[<githost>]:<port>([<IP>]:<port>)' can't be established.
DSA key fingerprint is <blah>
I understand this error means that the server's key has probably changed, and I understand in general how to deal with this via SSH config. When I manually ssh'd to the server the first time after receiving the error, I got the same message, as expected. I entered "yes" and tried again to verify that the error went away. It did. I think ran bitbake again and got the same error. I changed my ~/.ssh/ssh_config file to disable StrictHostKeyChecking and still get the error.
Is bitbake somehow using different known_hosts and ssh_config files from the ones I use for interactive logins? Other ideas on how to resolve this?
[-- Attachment #2: Type: text/html, Size: 5681 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Host authenticity failures
@ 2013-01-02 22:55 Thornburg, Christopher A
0 siblings, 0 replies; 5+ messages in thread
From: Thornburg, Christopher A @ 2013-01-02 22:55 UTC (permalink / raw)
To: yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
I've started getting the following error from bitbake when it's trying to access my git server:
The authenticity of host '[<githost>]:<port>([<IP>]:<port>)' can't be established.
DSA key fingerprint is <blah>
I understand this error means that the server's key has probably changed, and I understand in general how to deal with this via SSH config. When I manually ssh'd to the server the first time after receiving the error, I got the same message, as expected. I entered "yes" and tried again to verify that the error went away. It did. I then ran bitbake again and got the same error. I changed my ~/.ssh/ssh_config file to disable StrictHostKeyChecking and still get the error.
Is bitbake somehow using different known_hosts and ssh_config files from the ones I use for interactive logins? Other ideas on how to resolve this?
[-- Attachment #2: Type: text/html, Size: 2915 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-01-07 21:48 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-02 22:48 Host authenticity failures Thornburg, Christopher A
2013-01-05 2:50 ` Stewart, David C
2013-01-05 2:52 ` Khem Raj
2013-01-07 21:48 ` Thornburg, Christopher A
-- strict thread matches above, loose matches on Subject: below --
2013-01-02 22:55 Thornburg, Christopher A
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.