Rémy,
> On Sep 30, 2016, at 09:50, Rémy Maucherat wrote:
>
> 2016-09-30 15:26 GMT+02:00 jean-frederic clere :
>
>>> On 09/29/2016 08:35 PM, Christopher Schultz wrote:
>>> All,
>>>
>>> In the past few years, jfclere has been dong some performance testing
2016-09-30 22:38 GMT+03:00 :
> Author: markt
> Date: Fri Sep 30 19:38:36 2016
> New Revision: 1762955
>
> URL: http://svn.apache.org/viewvc?rev=1762955=rev
> Log:
> Remove unused class now JNDI is no longer used for resource access
1. This class is still mentioned here, in
Author: markt
Date: Fri Sep 30 19:38:36 2016
New Revision: 1762955
URL: http://svn.apache.org/viewvc?rev=1762955=rev
Log:
Remove unused class now JNDI is no longer used for resource access
Removed:
tomcat/tc8.0.x/trunk/java/org/apache/naming/JndiPermission.java
Modified:
Author: markt
Date: Fri Sep 30 19:38:06 2016
New Revision: 1762954
URL: http://svn.apache.org/viewvc?rev=1762954=rev
Log:
Remove unused class now JNDI is no longer used for resource access
Removed:
tomcat/tc8.5.x/trunk/java/org/apache/naming/JndiPermission.java
Modified:
Author: markt
Date: Fri Sep 30 19:37:41 2016
New Revision: 1762953
URL: http://svn.apache.org/viewvc?rev=1762953=rev
Log:
Remove unused class now JNDI is not longer used for resource access
Removed:
tomcat/trunk/java/org/apache/naming/JndiPermission.java
Modified:
tomcat/trunk/build.xml
Author: markt
Date: Fri Sep 30 19:33:33 2016
New Revision: 1762949
URL: http://svn.apache.org/viewvc?rev=1762949=rev
Log:
Remove references to now unused jndi: URLs
Modified:
tomcat/tc8.0.x/trunk/ (props changed)
Author: markt
Date: Fri Sep 30 19:33:01 2016
New Revision: 1762948
URL: http://svn.apache.org/viewvc?rev=1762948=rev
Log:
Remove references to now unused jndi: URLs
Modified:
tomcat/tc8.5.x/trunk/ (props changed)
Author: markt
Date: Fri Sep 30 19:32:32 2016
New Revision: 1762947
URL: http://svn.apache.org/viewvc?rev=1762947=rev
Log:
Remove references to now unused jndi: URLs
Modified:
tomcat/trunk/java/org/apache/jasper/compiler/JspRuntimeContext.java
Author: markt
Date: Fri Sep 30 19:28:31 2016
New Revision: 1762946
URL: http://svn.apache.org/viewvc?rev=1762946=rev
Log:
Investigating https://bz.apache.org/bugzilla/show_bug.cgi?id=60087
If Tomcat is going to start using 'jar:war:file:' URLs as the code source for
classes, ensure that the
Author: markt
Date: Fri Sep 30 19:28:08 2016
New Revision: 1762945
URL: http://svn.apache.org/viewvc?rev=1762945=rev
Log:
Investigating https://bz.apache.org/bugzilla/show_bug.cgi?id=60087
If Tomcat is going to start using 'jar:war:file:' URLs as the code source for
classes, ensure that the
Author: markt
Date: Fri Sep 30 19:27:37 2016
New Revision: 1762944
URL: http://svn.apache.org/viewvc?rev=1762944=rev
Log:
Investigating https://bz.apache.org/bugzilla/show_bug.cgi?id=60087
If Tomcat is going to start using 'jar:war:file:' URLs as the code source for
classes, ensure that the
Hi,
2016-09-26 19:17 GMT+03:00 Mark Thomas :
>
> Version 1.2.10 includes the following change:
>
> - Update minimum recommended OpenSSL version to 1.0.2j
> - Windows binaries built with OpenSSL 1.0.2j
>
> The proposed release artefacts can be found at [1],
> and the build was
2016-09-30 15:26 GMT+02:00 jean-frederic clere :
> On 09/29/2016 08:35 PM, Christopher Schultz wrote:
> > All,
> >
> > In the past few years, jfclere has been dong some performance testing
> > with JSSE-based crypto versus OpenSSL-based crypto, and it had always
> > been clear
On 09/29/2016 08:35 PM, Christopher Schultz wrote:
> All,
>
> In the past few years, jfclere has been dong some performance testing
> with JSSE-based crypto versus OpenSSL-based crypto, and it had always
> been clear that the pure-Java crypto was slower by orders of magnitude.
Correct, it is
https://bz.apache.org/bugzilla/show_bug.cgi?id=60087
--- Comment #4 from Mark Thomas ---
Unfortunately, it doesn't appear to be as clear cut as I would like.
If we look at how the JRE constructs a code path for a JAR, it returns a
"file:" URL to the JAR, not a "jar:" URL.
Author: violetagg
Date: Fri Sep 30 11:37:26 2016
New Revision: 16040
Log:
Adding code signing key.
Modified:
release/tomcat/tomcat-6/KEYS
Modified: release/tomcat/tomcat-6/KEYS
==
--- release/tomcat/tomcat-6/KEYS
2016-09-30 10:23 GMT+03:00 Mark Thomas :
>
> On 29/09/2016 15:38, Violeta Georgieva wrote:
> > Hi,
> >
> > 2016-09-29 17:02 GMT+03:00 Mark Thomas :
> >>
> >> On 20/09/2016 20:07, Mark Thomas wrote:
> >>> All,
> >>>
> >>> It has been a while since 6.0.x and the
Author: violetagg
Date: Fri Sep 30 11:19:14 2016
New Revision: 1762883
URL: http://svn.apache.org/viewvc?rev=1762883=rev
Log:
Adding code signing key.
Modified:
tomcat/tc6.0.x/trunk/ (props changed)
tomcat/tc6.0.x/trunk/KEYS
Propchange: tomcat/tc6.0.x/trunk/
On 26/09/2016 17:17, Mark Thomas wrote:
> Version 1.2.10 includes the following change:
>
> - Update minimum recommended OpenSSL version to 1.0.2j
> - Windows binaries built with OpenSSL 1.0.2j
>
> The proposed release artefacts can be found at [1],
> and the build was done using tag [2].
>
>
2016-09-27 23:23 GMT+09:00 Mark Thomas :
> Tag:
> http://svn.apache.org/viewvc/tomcat/jk/tags/JK_1_2_42/
>
> Source:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-connectors/jk/
>
> This is a maintenance release with a handful of bug fixes. It also
> includes Windows
On 27/09/2016 15:23, Mark Thomas wrote:
> Tag:
> http://svn.apache.org/viewvc/tomcat/jk/tags/JK_1_2_42/
>
> Source:
> https://dist.apache.org/repos/dist/dev/tomcat/tomcat-connectors/jk/
>
> This is a maintenance release with a handful of bug fixes. It also
> includes Windows binaries for IIS.
>
Github user vmassol commented on the pull request:
https://github.com/apache/tomcat/commit/eb195bebac8239b994fa921aeedb136a93e4ccaf#commitcomment-19237685
In java/org/apache/catalina/Context.java:
In java/org/apache/catalina/Context.java on line 1790:
Hi Mark,
Thanks
On 29/09/2016 15:38, Violeta Georgieva wrote:
> Hi,
>
> 2016-09-29 17:02 GMT+03:00 Mark Thomas :
>>
>> On 20/09/2016 20:07, Mark Thomas wrote:
>>> All,
>>>
>>> It has been a while since 6.0.x and the changelog is looking a tad long.
>>> Any takers for RM'ing a release?
>>
>>
All,
Symantec have sent out notification that they are tightening up the code
signing API [1].
The good news for us is that we already send everything, including
credentials, as part of the POST body so this should be a NO-OP for us.
Mark
[1]
24 matches
Mail list logo