svn commit: r1917707 - /tomcat/site/trunk/docs/.well-known/security.txt

Author: schultz Date: Mon May 13 18:43:52 2024 New Revision: 1917707 URL: http://svn.apache.org/viewvc?rev=1917707&view=rev Log: Update security.txt with a current expiration date. Modified: tomcat/site/trunk/docs/.well-known/security.txt Modified: tomcat/site/trunk/docs/.well-k

Re: Signature expiration on security.txt

On 20/06/2023 18:09, Christopher Schultz wrote: All, I just discovered that our security.txt file[1] had passed its "expiration date" and just updated it and re-signed it. Is there any existing process for "checking things" where we could insert a check for "is sec

Signature expiration on security.txt

All, I just discovered that our security.txt file[1] had passed its "expiration date" and just updated it and re-signed it. Is there any existing process for "checking things" where we could insert a check for "is security.txt about to expire" into that work

svn commit: r1910521 - /tomcat/site/trunk/docs/.well-known/security.txt

Author: schultz Date: Tue Jun 20 17:03:16 2023 New Revision: 1910521 URL: http://svn.apache.org/viewvc?rev=1910521&view=rev Log: Update security.txt with a new expiration date. Modified: tomcat/site/trunk/docs/.well-known/security.txt Modified: tomcat/site/trunk/docs/.well-k

svn commit: r1901833 - in /tomcat/site/trunk/docs/.well-known: security.txt security.txt.asc

Author: schultz Date: Sat Jun 11 16:18:37 2022 New Revision: 1901833 URL: http://svn.apache.org/viewvc?rev=1901833&view=rev Log: Switch to using a single signed file. Removed: tomcat/site/trunk/docs/.well-known/security.txt.asc Modified: tomcat/site/trunk/docs/.well-known/security

svn commit: r1901831 - /tomcat/site/trunk/docs/.well-known/security.txt

nown/security.txt Modified: tomcat/site/trunk/docs/.well-known/security.txt URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/.well-known/security.txt?rev=1901831&r1=1901830&r2=1901831&view=diff == --- tomcat/site/

svn commit: r1891327 - in /tomcat/site/trunk/docs: .htaccess .well-known/ .well-known/security.txt

Author: schultz Date: Wed Jul 7 01:05:31 2021 New Revision: 1891327 URL: http://svn.apache.org/viewvc?rev=1891327&view=rev Log: Add security.txt file. Added: tomcat/site/trunk/docs/.well-known/ tomcat/site/trunk/docs/.well-known/security.txt Modified: tomcat/site/trunk/

Re: security.txt

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 9/1/20 14:38, Mark Thomas wrote: > On 01/09/2020 18:01, Christopher Schultz wrote: >> All, >> >> I'd like to propose that we publish a security.txt[1] file on our >> web site under /.well-known/security.

Re: security.txt

On Tue, Sep 1, 2020 at 1:01 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > All, > > I'd like to propose that we publish a security.txt[1] file on our web > site under /.well-known/security.txt

Re: security.txt

On Tue, Sep 1, 2020 at 2:38 PM Mark Thomas wrote: > On 01/09/2020 18:01, Christopher Schultz wrote: > > All, > > > > I'd like to propose that we publish a security.txt[1] file on our web > > site under /.well-known/security.txt and /security.txt > > >

Re: security.txt

On 01/09/2020 18:01, Christopher Schultz wrote: > All, > > I'd like to propose that we publish a security.txt[1] file on our web > site under /.well-known/security.txt and /security.txt > > This file contains information we all already know, but it's in > obviously

security.txt

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I'd like to propose that we publish a security.txt[1] file on our web site under /.well-known/security.txt and /security.txt This file contains information we all already know, but it's in obviously "proprietary" locations