Re: [4.0.3] [VOTES] Upcoming release and security fix

2002-03-01 Thread jean-frederic clere
Remy Maucherat wrote: Since there are apparently diverging opinions on the subject (and also since I didn't get any +1s for a possible 4.0.3 b1, or a 4.0.2a release), here's a formal request for vote. On the security problem reported yesterday, affecting the security manager sandboxing.

RE: [4.0.3] [VOTES] Upcoming release and security fix

2002-03-01 Thread GOMEZ Henri
Since there are apparently diverging opinions on the subject (and also since I didn't get any +1s for a possible 4.0.3 b1, or a 4.0.2a release), here's a formal request for vote. On the security problem reported yesterday, affecting the security manager sandboxing. We should: ballot A [ ]

Re: [4.0.3] [VOTES] Upcoming release and security fix

2002-03-01 Thread Pier Fumagalli
GOMEZ Henri [EMAIL PROTECTED] wrote: 4.0.2a + 4.0.3b1 :) Just to be a pain in the ass I don't really like the concept of an A version (never happened in httpd land)... So, I would call them 4.0.3 and 4.0.4b1 My $ 0.02 Pier -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For

Re: [4.0.3] [VOTES] Upcoming release and security fix

2002-03-01 Thread costinm
On Fri, 1 Mar 2002, Pier Fumagalli wrote: GOMEZ Henri [EMAIL PROTECTED] wrote: 4.0.2a + 4.0.3b1 :) Just to be a pain in the ass I don't really like the concept of an A version (never happened in httpd land)... So, I would call them 4.0.3 and 4.0.4b1 He's right... However a small

RE: [4.0.3] [VOTES] Upcoming release and security fix

2002-03-01 Thread GOMEZ Henri
On Fri, 1 Mar 2002, Pier Fumagalli wrote: GOMEZ Henri [EMAIL PROTECTED] wrote: 4.0.2a + 4.0.3b1 :) Just to be a pain in the ass I don't really like the concept of an A version (never happened in httpd land)... So, I would call them 4.0.3 and 4.0.4b1 Ok let's do 'a la HTTPd', 4.0.3

Re: [4.0.3] [VOTES] Upcoming release and security fix

2002-03-01 Thread Remy Maucherat
Just to be a pain in the ass I don't really like the concept of an A version (never happened in httpd land)... So, I would call them 4.0.3 and 4.0.4b1 Ok let's do 'a la HTTPd', 4.0.3 (fix security problems in 4.0.2) and 4.0.4b1 Thanks for the feedback. It will then be 4.0.3 + 4.0.4b1 +

Re: [4.0.3] [VOTES] Upcoming release and security fix

2002-03-01 Thread costinm
On Fri, 1 Mar 2002, Remy Maucherat wrote: Just to be a pain in the ass I don't really like the concept of an A version (never happened in httpd land)... So, I would call them 4.0.3 and 4.0.4b1 Ok let's do 'a la HTTPd', 4.0.3 (fix security problems in 4.0.2) and 4.0.4b1 Thanks

Re: [4.0.3] [VOTES] Upcoming release and security fix

2002-02-28 Thread Jason Brittain
Hi Remy and gang.. Below is my non-binding vote (for fun!): Remy Maucherat wrote: Since there are apparently diverging opinions on the subject (and also since I didn't get any +1s for a possible 4.0.3 b1, or a 4.0.2a release), here's a formal request for vote. On the security problem

Re: [4.0.3] [VOTES] Upcoming release and security fix

2002-02-28 Thread Craig R. McClanahan
+1 for option A and B together (they don't have to be mutually exclusive, and we can examine user behavior to see if binary patches are an idea worth pursuing. +1 for 4.0.3-b1. Craig On Thu, 28 Feb 2002, Remy Maucherat wrote: Date: Thu, 28 Feb 2002 11:09:08 -0800 From: Remy Maucherat

Re: [4.0.3] [VOTES] Upcoming release and security fix

2002-02-28 Thread Bill Barker
- Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, February 28, 2002 11:09 AM Subject: [4.0.3] [VOTES] Upcoming release and security fix ballot A [+0] Make a full 4.0.3 (or 4.0.2a) release which would only include the security fix B

Re: [4.0.3] [VOTES] Upcoming release and security fix

2002-02-28 Thread costinm
On Thu, 28 Feb 2002, Remy Maucherat wrote: On the security problem reported yesterday, affecting the security manager sandboxing. We should: ballot A [] Make a full 4.0.3 (or 4.0.2a) release which would only include the security fix B [+1] Make the security fix available as a binary patch