On Mon Apr 2 10:28:28 EDT 2012, s...@9front.org wrote: > After patching ndb/cs and running nfactotum, I'm still having > some trouble getting the new ssh to successfully login to a > remote system: > > term% ssh2 openbsd > The following key has been offered by the server: > ek=10001 > n=DA58E23128A865ABF57DCEEBB31529854F0EFBB0D50ADC5D930F29D7B5592724E9C8A1D74D01140736B72E17EC2F9EFE130AC59BE7F23A4768F748217012B99AA5F508F963D01BE1D939B450F19B1F7CAF6CAA4A5C1AAD817170654045E4981CA380B1975FD87F60BCF38652CAD44CCE13171E0115733E8085BAB151E4C79621AC186D9A51F3B7325FCC5CAC9A64FD5108509D275F93D48AD4B4E8A774C43A07337135D82A01DA529CCEB6107913A20CD4D576BB9FB2C85E0233E9745BE6092A0E1EAAA5596DF2166B0B0A9845F51AF1121613DE9AB241C00416E9C2B39B1C0394A914C5414D838CE8FF4D62170774E0707CC628E495E210F430BA465BF9B2A7 > > Add this key? (yes, no, session) yes > ssh2: dial: handshake failed > term% ssh2 -d openbsd > Key verification dialog failed > ssh2: dial: handshake failed > term% ssh2 -d -k openbsd > Key verification dialog failed > ssh2: dial: handshake failed
we're working on it. - erik
