Re: Top Level Security Page

2014-09-10 Thread Gary Gregory
ah, I have HttpsEverywhere and it redirs my request to HTTPS which there is none, plain HTTP works. Looks good. Gary On Wed, Sep 10, 2014 at 7:39 AM, Stefan Bodewig wrote: > On 2014-09-10, Gary Gregory wrote: > > > Hm... "The requested URL /security.html was not found on this server." > > I cop

Re: Top Level Security Page

2014-09-10 Thread Stefan Bodewig
On 2014-09-10, Gary Gregory wrote: > Hm... "The requested URL /security.html was not found on this server." I copy pasted the link from my browser. The page has been there for almost two weeks now, so we can rule out stale caches. Are you sure you are trying the URL that contains "staging" insi

Re: Top Level Security Page

2014-09-10 Thread Gary Gregory
Hm... "The requested URL /security.html was not found on this server." Gary On Wed, Sep 10, 2014 at 6:16 AM, Stefan Bodewig wrote: > Hi > > I've just added a link to the security page inside the main navigation, > see > > http://commons.staging.apache.org/security.html > > The page is insid

Re: Top Level Security Page

2014-09-10 Thread Stefan Bodewig
Hi I've just added a link to the security page inside the main navigation, see http://commons.staging.apache.org/security.html The page is inside the staging area only, but I'd like to publish it sooner rather than later - and update the commons parent to include the same link. Should the l

Re: Top Level Security Page

2014-09-01 Thread Stefan Bodewig
On 2014-09-01, sebb wrote: > On 1 September 2014 04:53, Stefan Bodewig wrote: >> On 2014-09-01, sebb wrote: >>> The page mentions denial of service - not sure that applies to any of >>> the Commons components? >> The one issue with Compress could be used for a DoS attack. > I think that would

Re: Top Level Security Page

2014-09-01 Thread sebb
On 1 September 2014 04:53, Stefan Bodewig wrote: > On 2014-09-01, sebb wrote: > >> Might be useful to add a link to the security page under "General >> Information". > > Right. > > >> The page mentions denial of service - not sure that applies to any of >> the Commons components? > > The one issue

Re: Top Level Security Page

2014-08-31 Thread Stefan Bodewig
On 2014-09-01, sebb wrote: > Might be useful to add a link to the security page under "General > Information". Right. > The page mentions denial of service - not sure that applies to any of > the Commons components? The one issue with Compress could be used for a DoS attack. Stefan -

Re: Top Level Security Page

2014-08-31 Thread sebb
Might be useful to add a link to the security page under "General Information". The page mentions denial of service - not sure that applies to any of the Commons components? On 31 August 2014 13:40, Stefan Bodewig wrote: > On 2014-08-31, Gary Gregory wrote: > >> I get a 404... > > strange. Tak

Re: Top Level Security Page

2014-08-31 Thread Stefan Bodewig
On 2014-08-31, Gary Gregory wrote: > I get a 404... strange. Take note of "staging" in the URL > http://commons.staging.apache.org/security.html Stefan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For addition

Re: Top Level Security Page

2014-08-31 Thread Gary Gregory
I get a 404... Gary Original message From: Stefan Bodewig Date:08/31/2014 06:52 (GMT-05:00) To: Commons Developers List Subject: Re: Top Level Security Page On 2014-08-31, Gary Gregory wrote: > Great idea! > Every Commons component should have such a page indee

Re: Top Level Security Page

2014-08-31 Thread Stefan Bodewig
On 2014-08-31, Gary Gregory wrote: > Great idea! > Every Commons component should have such a page indeed, can be a link > to the same page for all of Commons IMO. > Some changes though are needed. > It should be made clearer that there is an important distinction > between undisclosed and disc

RE: Top Level Security Page

2014-08-31 Thread Gary Gregory
Great idea! Every Commons component should have such a page indeed, can be a link to the same page for all of Commons IMO. Some changes though are needed. It should be made clearer that there is an important distinction between undisclosed and disclosed issues.  One way to do this is with two