Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Today, John Abreau gleaned this insight: > Against my advice, my manager decided to go with the commercial F/Secure > SSH server for our Unix hosts, instead of openssh. We had been using ssh > 2.0.13 originally, and I had begun migrating systems over to OpenSSH > before this decision came through. A new server was built recently, and > F/secure ssh 2.3.0 was installed on it, and now I find that the openssh > client won't connect to it; it gives the error > > Disconnecting: Corrupted HMAC on input. > > Is this something simple to fix, or is 2.3.0 just incompatible? This sounds like an "I told you so" moment... ;) -- You know that everytime I try to go where I really want to be, It's already where I am, cuz I'm already there... --------------------------------------------------------------- Derek D. Martin | Unix/Linux Geek ddm at MissionCriticalLinux.com | derek at cerberus.ne.mediaone.net --------------------------------------------------------------- - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |