public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Martin Galvan <martin.galvan@tallertechnologies.com>,
	overseers@sourceware.org
Subject: Re: Lost SSH key
Date: Wed, 02 Mar 2016 06:00:00 -0000	[thread overview]
Message-ID: <m3vb55v2qd.fsf@pepe.airs.com> (raw)
In-Reply-To: <alpine.BSF.2.02.1603020027320.8441@arjuna.pair.com> (Hans-Peter Nilsson's message of "Wed, 2 Mar 2016 00:34:21 -0500 (EST)")

Hans-Peter Nilsson <hp@bitrange.com> writes:

> Another one from the peanut gallery: it's not as simple as a
> missing "chmod go-r ~martingalvan/.ssh/authorized_keys" on
> sourceware, after appending the new key?

I don't think so.  Most, perhaps all, of the authorized_keys files on
sourceware are world-readable.

Ian

  reply	other threads:[~2016-03-02  6:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 19:52 Martin Galvan
2016-02-26  0:36 ` Ian Lance Taylor
2016-03-01 18:15   ` Martin Galvan
2016-03-02  4:47     ` Ian Lance Taylor
2016-03-02  5:34       ` Hans-Peter Nilsson
2016-03-02  6:00         ` Ian Lance Taylor [this message]
2016-03-02 13:29           ` Martin Galvan
2016-03-02 13:51             ` Frank Ch. Eigler
2016-03-02 14:00               ` Martin Galvan
2016-03-02 14:37                 ` Martin Galvan
  -- strict thread matches above, loose matches on Subject: below --
2021-03-11  8:59 Robin Dapp
2019-07-08 13:43 Andrew Sutton
2019-07-08 13:53 ` Carlos O'Donell
2012-02-22 14:54 Lost ssh key Ed Smith-Rowland
2012-02-22 16:10 ` Ian Lance Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3vb55v2qd.fsf@pepe.airs.com \
    --to=ian@airs.com \
    --cc=hp@bitrange.com \
    --cc=martin.galvan@tallertechnologies.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).