From: Jim Kingdon <kingdon@panix.com>
To: law@redhat.com, drepper@redhat.com
Cc: overseers@sources.redhat.com, angela@redhat.com
Subject: Kerberos status
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <200007062000.QAA08160@panix3.panix.com> (raw)
OK, I've tried to summarize the status quo on Kerberos at
http://sources.redhat.com/sourceware/kerberos.html
As most of you probably recall, we are currently running a
configuration with security holes and we need to upgrade it.
I'm going to assign primary responsibility for fixing this to Jeff Law
and/or Ulrich Drepper, since they seem to be the ones most interested
in Kerberos. They of course will probably try to find someone else to
pass it to, which is fine with me, but I'm planning to play "I don't
work for Red Hat any more, and I'm not volunteering" on this one.
Whoever takes this on should be able to get help from
angela@redhat.com and/or sysadmin@cygnus.com, so it shouldn't be that
bad provided that you work with the people who would be affected.
WARNING: multiple messages have this Message-ID
From: Jim Kingdon <kingdon@panix.com>
To: law@redhat.com, drepper@redhat.com
Cc: overseers@sources.redhat.com, angela@redhat.com
Subject: Kerberos status
Date: Thu, 06 Jul 2000 13:00:00 -0000 [thread overview]
Message-ID: <200007062000.QAA08160@panix3.panix.com> (raw)
Message-ID: <20000706130000.KETHi9jkh_G1rZXntbVaVv4El01AfK95eqZvigf2gvY@z> (raw)
OK, I've tried to summarize the status quo on Kerberos at
http://sources.redhat.com/sourceware/kerberos.html
As most of you probably recall, we are currently running a
configuration with security holes and we need to upgrade it.
I'm going to assign primary responsibility for fixing this to Jeff Law
and/or Ulrich Drepper, since they seem to be the ones most interested
in Kerberos. They of course will probably try to find someone else to
pass it to, which is fine with me, but I'm planning to play "I don't
work for Red Hat any more, and I'm not volunteering" on this one.
Whoever takes this on should be able to get help from
angela@redhat.com and/or sysadmin@cygnus.com, so it shouldn't be that
bad provided that you work with the people who would be affected.
next reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Jim Kingdon [this message]
2000-07-06 13:00 ` Jim Kingdon
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=200007062000.QAA08160@panix3.panix.com \
--to=kingdon@panix.com \
--cc=angela@redhat.com \
--cc=drepper@redhat.com \
--cc=law@redhat.com \
--cc=overseers@sources.redhat.com \
/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).