+1
On Sun, Jul 16, 2017 at 3:30 PM, Karl Pauls wrote:
> +1
>
> regards,
>
> Karl
>
> On Sunday, July 16, 2017, Carsten Ziegeler wrote:
>
> > +1
> >
> >
> >
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
[
https://issues.apache.org/jira/browse/SLING-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-7015:
--
Fix Version/s: Sling Models Impl 1.4.4
Sling Models API 1.3.6
> Add Utility
[
https://issues.apache.org/jira/browse/SLING-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-7015:
--
Attachment: SLING-7015.diff
Proposed change attached
> Add Utility Method to ModelFactory to
[
https://issues.apache.org/jira/browse/SLING-7011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-7011.
-
> fsresource: Detect FileVault .xml JCR XML files
>
[
https://issues.apache.org/jira/browse/SLING-7007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-7007.
-
> fsresource: Support URL-encoded file names
> --
>
>
Hi,
The vote has passed with the following result :
+1 (binding): Stefan Seifert, Carsten Ziegeler, Karl Pauls
I will copy this release to the Sling dist directory and
promote the artifacts to the central Maven repository.
stefan
Severity: Important
Vendor: The Apache Software Foundation
Versions Affected:
Sling XSS Protection API 1.0.8
Description:
The encoding done by the XSSAPI.encodeForJSString() method is not
restrictive enough and for some input patterns allows script tags to
pass through unencoded, leading to
Severity: Important
Vendor: The Apache Software Foundation
Versions Affected:
Sling XSS Protection API 1.0.0
Description:
The method XSS.getValidXML() uses an insecure SAX parser to validate
the input string, which allows for XXE [0] attacks in all scripts
which use this method to validate user
I would like to call a vote on the following releases,
Service User Mapper 1.3.4
We solved 1 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12340608
Resource Resolver 1.5.28
We solved 1 issue in this release:
[
https://issues.apache.org/jira/browse/SLING-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-4752:
--
Fix Version/s: (was: JCR Resource 3.0.4)
JCR Resource 3.0.6
> New resource query
[
https://issues.apache.org/jira/browse/SLING-6402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-6402:
--
Fix Version/s: (was: JCR Base 3.0.4)
JCR Base 3.0.6
> Remove
[
https://issues.apache.org/jira/browse/SLING-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-4752:
--
Fix Version/s: (was: Resource Resolver 1.5.28)
(was: Resource Resolver
[
https://issues.apache.org/jira/browse/SLING-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-6943:
--
Fix Version/s: (was: Resource Resolver 1.5.28)
(was: Resource Resolver
[
https://issues.apache.org/jira/browse/SLING-6943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-6943:
--
Fix Version/s: Resource Resolver 1.5.20
> Don't call into service registry from within a synchronized
[
https://issues.apache.org/jira/browse/SLING-4752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-4752:
--
Fix Version/s: Resource Resolver 1.5.20
> New resource query API
> --
>
>
15 matches
Mail list logo