On Mon, 2004-01-19 at 12:32, [EMAIL PROTECTED] wrote:
> martin 2004/01/19 03:32:59
>
> Modified:.KEYS
> Log:
> No need to spam innocent people
I'd think that the spammers have picked up on the s/@/ at / trick by
now. I don't really see how this fixes things for these peopl
[EMAIL PROTECTED] wrote:
> martin 2003/09/08 04:03:40
>
> Modified:.KEYS
> Log:
> Add my 768/FDE534D1 key
That's a little weak, isn't it?
--
http://www.apache-ssl.org/ben.html http://www.thebunker.net/
"There is no limit to what a man can do or how far he can go i
Ahhh... verification between project RMs of one another's tarballs?
Then don't plug this into KEYS and raise awareness (our workload)
to insurmountable levels. Let's start a wiki^H^H^H^Hdoc page all about
release signatures and PGP. Explain in a nutshell what is signed, why
it is signed and how
--On Tuesday, February 18, 2003 12:06 PM -0600 "William A. Rowe, Jr."
<[EMAIL PROTECTED]> wrote:
I agree that was overkill. However, why put anything on the
contributors web page? I believe that information exists right
there, in the KEYS file, as to who signed a given release, with our
email a
At 11:36 AM 2/18/2003, Justin Erenkrantz wrote:
>--On Tuesday, February 18, 2003 1:25 AM -0600 "William A. Rowe, Jr."
><[EMAIL PROTECTED]> wrote:
>
>>It's a little absurd to try to have folks chasing us down for sigs
>>at home. Don't we all get enough oddball private inquiries?
>
>The original sug
--On Tuesday, February 18, 2003 1:25 AM -0600 "William A. Rowe, Jr."
<[EMAIL PROTECTED]> wrote:
Justin, could you *please* find a better way to say what you were
(rightly) trying to convey about the keys file, below?
I welcome constructive comments, but we should indicate how we want
people to
Justin, could you *please* find a better way to say what you were (rightly)
trying to convey about the keys file, below?
It's a little absurd to try to have folks chasing us down for sigs at home.
Don't we all get enough oddball private inquiries?
A much more rational approach would be a resource
> +Apache developers: please ensure that your key is also available via the
> +PGP keyservers (such as pgpkeys.mit.edu).
That should not be necessary. The KEYS file is in a well known public
location which serves the same purposes for our set of public keys as
the keyserver.
-aaron
Nov 2002 is the current baseline that we Planners are working towards.
Security Travel is looking at hotels and venues as well for that
time frame. We even have some candidate dates as well.
Speaking as an ApacheCon planner, it's pretty authoritative :)
Rich Bowen wrote:
>
> On Mon, 8 Apr 2002,
"Justin Erenkrantz" <[EMAIL PROTECTED]> wrote:
> Especially now that we went GA on 2.0, we should meet to discuss
> 2.1 or 3.0... Waiting until Nov will just suck. -- justin
I'm going to get a gun now! :) Before talking about 2.1, I (and I know I'm
voicing concerns of _a_lot_ of people) would
On Mon, 8 Apr 2002, Jim Jagielski wrote:
> Most likely Nov 2002.
Is this authoritative, or speculation? I am trying to schedule going to
Paraguay for my brother's wedding on the week after the week when I
understood ApacheCon to be. Something authoritative would be handy, so
that I can buy overp
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote :
> On Mon, 8 Apr 2002, Jim Jagielski wrote:
>
> > Most likely Nov 2002.
> >
> > Doesn't help out now, I know.
> >
> > Justin Erenkrantz wrote:
> > >
> > > On Mon, Apr 08, 2002 at 03:25:39PM -0400, Jim Jagielski wrote:
> > > > Hopefully, the next Apac
> From: Cliff Woolley [mailto:[EMAIL PROTECTED]]
> Sent: 08 April 2002 23:03
> On Mon, 8 Apr 2002, Justin Erenkrantz wrote:
>
> > Perhaps we httpd people should get together before November.
> > Are enough core people up for a meeting before then?
>
> +1
I would like this very much, but I'm af
On Mon, 8 Apr 2002, Justin Erenkrantz wrote:
> Perhaps we httpd people should get together before November.
> Are enough core people up for a meeting before then?
+1
--
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
On Mon, Apr 08, 2002 at 03:50:40PM -0400, Cliff Woolley wrote:
> On Mon, 8 Apr 2002, Jim Jagielski wrote:
>
> > Most likely Nov 2002.
Oh great. When were we going to be told that? August really
works better for me. November is just going to suck. I'm really
going to be leery about taking a w
On Mon, 8 Apr 2002, Jim Jagielski wrote:
> Most likely Nov 2002.
>
> Doesn't help out now, I know.
>
> Justin Erenkrantz wrote:
> >
> > On Mon, Apr 08, 2002 at 03:25:39PM -0400, Jim Jagielski wrote:
> > > Hopefully, the next ApacheCon will afford an op for mega signing :)
> >
> > *ahem* When wil
Most likely Nov 2002.
Doesn't help out now, I know.
Justin Erenkrantz wrote:
>
> On Mon, Apr 08, 2002 at 03:25:39PM -0400, Jim Jagielski wrote:
> > Hopefully, the next ApacheCon will afford an op for mega signing :)
>
> *ahem* When will the next ApacheCon be? -- justin
>
--
=
On Mon, Apr 08, 2002 at 03:25:39PM -0400, Jim Jagielski wrote:
> Hopefully, the next ApacheCon will afford an op for mega signing :)
*ahem* When will the next ApacheCon be? -- justin
Hopefully, the next ApacheCon will afford an op for mega signing :)
Cliff Woolley wrote:
>
> On Mon, 8 Apr 2002, Brad Nicholes wrote:
>
> >> Brad, has your key been signed by anyone? I'm not seeing any sigs
> >> under your public key. If you need someone to sign your key (which
> >> you do if y
On Mon, 8 Apr 2002, Brad Nicholes wrote:
>> Brad, has your key been signed by anyone? I'm not seeing any sigs
>> under your public key. If you need someone to sign your key (which
>> you do if you want to sign any httpd binary distros) then let me know.
>
> It has not yet been signed by anybody.
It has not yet been signed by anybody.
Brad
Brad Nicholes
Senior Software Engineer
Novell, Inc., a leading provider of Net business solutions
http://www.novell.com
>>> [EMAIL PROTECTED] Monday, April 08, 2002 1:01:31 PM >>>
On Mon, Apr 08, 2002 at 06:51:04PM -, Brad Nicholes wrote:
> bnich
On Mon, Apr 08, 2002 at 06:51:04PM -, Brad Nicholes wrote:
> bnicholes02/04/08 11:51:04
>
> Modified:.KEYS
> Log:
> Added my public key
Brad, has your key been signed by anyone? I'm not seeing any sigs
under your public key. If you need someone to sign your key (which
y
22 matches
Mail list logo
