Fire Eagle last spotted me at:

Longmont, CO

Archives

Translator

English flagItalian flagKorean flagChinese (Simplified) flagPortuguese flagGerman flagFrench flagSpanish flag
Japanese flagArabic flagRussian flagGreek flagDutch flagBulgarian flagCzech flagCroat flag
Danish flagFinnish flagHindi flagPolish flagRumanian flagSwedish flagNorwegian flagCatalan flag
Filipino flagHebrew flagIndonesian flagLatvian flagLithuanian flagSerbian flagSlovak flagSlovenian flag
Ukrainian flagVietnamese flag      
By N2H
  • 08Jun

    I use ssh key authentication to rsync data from my weather station to it’s website.  Mysteriously it started failing a few days ago.  After a bit of hair pulling and unhelpful ssh -vvv output, I found the cause.  The permissions of the authorized_keys file on the server were incorrect.

    -rw-rw-r–   1 stan4dnet pg478973  391 2008-05-07 12:14 authorized_keys

    This file is readable by more than just you. Newer versions of ssh see this, recongize it as a security hole, and prevent you from doing something stupid.  Lesson Learned: Make sure that the files in .ssh are writable only by you, on both machines, and non-executable by anyone.

    Some people recommend a simple “chmod 644 *” in your .ssh directories.  I don’t.  I recommend:

    chmod 400 *

    Posted by Joey Stanford @ 09:00

4 Responses

WP_Orange_Techno