From: Andrew Cagney <ac131313@cygnus.com>
To: Chris Faylor <cgf@redhat.com>
Cc: Mark Mitchell <mark@codesourcery.com>, overseers@gcc.gnu.org
Subject: Re: GCC maintainer account
Date: Mon, 31 Dec 2001 19:40:00 -0000 [thread overview]
Message-ID: <3A8DE3D8.97CBD65@cygnus.com> (raw)
In-Reply-To: <20010215221019.A14965@redhat.com>
Chris Faylor wrote:
> I've set this account up but this could possibly be retroactively vetoed
> by the other overseers if they see this as a security risk.
If I've the right of veto then I'd like to veto this move. It is a
serious security risk :-( It scares the crap out of me.
I think the obvious thing to do is to kick this stuff (especially all my
GDB cronjobs :-) off of that machine and onto a second machine that, by
its nature, is assumed to be compromised.
Given that probably won't happen, could you please look at alternatives.
Jeff suggested a common account for a select set of users. Going down
that path, you could even set up a separate CVS repository and put the
crontab entry in that. Installing a crontab from a script is pretty
easy. (I should note this still isn't very secure as the obvious thing
to put in a crontab is `cp ~ftp/incomming/xyz ~/.ssh/authorize_keys`.)
Another possability is some sort of chrooted environment. Anyway, there
must be HOWTOs somewhere that give hints on how to set this up.
enjoy,
Andrew
;
WARNING: multiple messages have this Message-ID
From: Andrew Cagney <ac131313@cygnus.com>
To: Chris Faylor <cgf@redhat.com>
Cc: Mark Mitchell <mark@codesourcery.com>, overseers@gcc.gnu.org
Subject: Re: GCC maintainer account
Date: Sat, 17 Feb 2001 10:45:00 -0000 [thread overview]
Message-ID: <3A8DE3D8.97CBD65@cygnus.com> (raw)
Message-ID: <20010217104500.xSmeKkZGdHrlFcKXAn9UDpdp73K1UZwG4vUeaZj2Wbw@z> (raw)
In-Reply-To: <20010215221019.A14965@redhat.com>
Chris Faylor wrote:
> I've set this account up but this could possibly be retroactively vetoed
> by the other overseers if they see this as a security risk.
If I've the right of veto then I'd like to veto this move. It is a
serious security risk :-( It scares the crap out of me.
I think the obvious thing to do is to kick this stuff (especially all my
GDB cronjobs :-) off of that machine and onto a second machine that, by
its nature, is assumed to be compromised.
Given that probably won't happen, could you please look at alternatives.
Jeff suggested a common account for a select set of users. Going down
that path, you could even set up a separate CVS repository and put the
crontab entry in that. Installing a crontab from a script is pretty
easy. (I should note this still isn't very secure as the obvious thing
to put in a crontab is `cp ~ftp/incomming/xyz ~/.ssh/authorize_keys`.)
Another possability is some sort of chrooted environment. Anyway, there
must be HOWTOs somewhere that give hints on how to set this up.
enjoy,
Andrew
;
next prev parent reply other threads:[~2001-12-31 19:40 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 19:40 Mark Mitchell
2001-02-15 18:19 ` Mark Mitchell
2001-12-31 19:40 ` Christopher Faylor
2001-02-15 18:31 ` Christopher Faylor
2001-12-31 19:40 ` Mark Mitchell
2001-02-15 18:42 ` Mark Mitchell
2001-12-31 19:40 ` Chris Faylor
2001-02-15 19:10 ` Chris Faylor
2001-12-31 19:40 ` Jason Molenda
2001-02-15 20:51 ` Jason Molenda
2001-12-31 19:40 ` Mark Mitchell
2001-02-15 21:17 ` Mark Mitchell
2001-12-31 19:40 ` Christopher Faylor
2001-02-15 21:56 ` Christopher Faylor
2001-12-31 19:40 ` Gerald Pfeifer
2001-02-16 0:47 ` Gerald Pfeifer
2001-12-31 19:40 ` Mark Mitchell
2001-02-16 8:30 ` Mark Mitchell
2001-12-31 19:40 ` Christopher Faylor
2001-02-16 9:09 ` Christopher Faylor
2001-12-31 19:40 ` Alexandre Oliva
2001-02-16 11:24 ` Alexandre Oliva
2001-12-31 19:40 ` Phil Edwards
2001-02-16 10:17 ` Phil Edwards
2001-12-31 19:40 ` Mark Mitchell
2001-02-15 19:24 ` Mark Mitchell
2001-12-31 19:40 ` Alexandre Petit-Bianco
2001-02-15 19:33 ` Alexandre Petit-Bianco
2001-12-31 19:40 ` Chris Faylor
2001-02-15 19:41 ` Chris Faylor
2001-12-31 19:40 ` Chris Faylor
2001-02-15 19:52 ` Chris Faylor
2001-12-31 19:40 ` Mark Mitchell
2001-02-15 20:05 ` Mark Mitchell
2001-12-31 19:40 ` Mark Mitchell
2001-02-15 19:21 ` Mark Mitchell
2001-12-31 19:40 ` Jeffrey A Law
2001-02-16 7:56 ` Jeffrey A Law
2001-12-31 19:40 ` Andrew Cagney [this message]
2001-02-17 10:45 ` Andrew Cagney
2001-02-17 15:23 ` Phil Edwards
2001-02-17 22:25 ` Jeffrey A Law
2001-02-18 13:40 ` several messages Gerald Pfeifer
2001-12-31 19:40 ` GCC maintainer account Mark Mitchell
2001-02-17 12:10 ` Mark Mitchell
2001-02-17 17:12 ` Chris Faylor
2001-12-31 19:40 ` Tom Tromey
2001-02-17 15:51 ` Tom Tromey
2001-12-31 19:40 ` Andrew Cagney
2001-02-20 8:27 ` Andrew Cagney
2001-02-20 11:39 ` Andrew Cagney
2001-12-31 19:40 ` Andrew Cagney
2001-02-16 6:18 ` Andrew Cagney
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=3A8DE3D8.97CBD65@cygnus.com \
--to=ac131313@cygnus.com \
--cc=cgf@redhat.com \
--cc=mark@codesourcery.com \
--cc=overseers@gcc.gnu.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).