[jira] [Resolved] (SLING-8369) Download plugins via https only
[ https://issues.apache.org/jira/browse/SLING-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-8369. Resolution: Fixed Thanks a lot for the PR [~hugo.hirsch]! > Download plugins via https only > --- > > Key: SLING-8369 > URL: https://issues.apache.org/jira/browse/SLING-8369 > Project: Sling > Issue Type: Improvement >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Parent 36 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] [sling-parent] rombert merged pull request #7: SLING-8369: Update pom.xml to use https only
rombert merged pull request #7: SLING-8369: Update pom.xml to use https only URL: https://github.com/apache/sling-parent/pull/7 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [sling-parent] rombert commented on issue #7: SLING-8369: Update pom.xml to use https only
rombert commented on issue #7: SLING-8369: Update pom.xml to use https only URL: https://github.com/apache/sling-parent/pull/7#issuecomment-485532548 Perfect, thanks @ottlinger ! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [sling-parent] ottlinger opened a new pull request #7: SLING-8369: Update pom.xml to use https only
ottlinger opened a new pull request #7: SLING-8369: Update pom.xml to use https only URL: https://github.com/apache/sling-parent/pull/7 Download plugins via https instead of http. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [sling-parent] ottlinger commented on issue #7: SLING-8369: Update pom.xml to use https only
ottlinger commented on issue #7: SLING-8369: Update pom.xml to use https only URL: https://github.com/apache/sling-parent/pull/7#issuecomment-485510546 @rombert hopefully this PR can be merged :-) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [sling-parent] ottlinger commented on issue #6: Update pom.xml
ottlinger commented on issue #6: Update pom.xml URL: https://github.com/apache/sling-parent/pull/6#issuecomment-485509915 Since I'm unable to amend the commit and checkout the branch locally I'll open a new PR with the correct reference to ASF-jira - thanks, @rombert This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [sling-parent] ottlinger closed pull request #6: Update pom.xml
ottlinger closed pull request #6: Update pom.xml URL: https://github.com/apache/sling-parent/pull/6 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (SLING-8369) Download plugins via https only
[
https://issues.apache.org/jira/browse/SLING-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823340#comment-16823340
]
Philipp Ottlinger commented on SLING-8369:
--
Mail via ASF:
{code:java}
Hi Apache Security Team,
This email is to responsibly disclose a security vulnerability in
several of the projects under the Apache organization.
CWE-829: Inclusion of Functionality from Untrusted Control Sphere
CWE-494: Download of Code Without Integrity Check
Impact Locations
I've been doing a cursory sweep of popular Github Gradle and Maven
based projects and I've been seeing this vulnerability in a lot of
places.
Kafka:
https://github.com/apache/kafka/blob/3cdc78e6bb1f83973a14ce1550fe3874f7348b05/gradle/buildscript.gradle#L20
Geode:
https://github.com/apache/geode/blob/964b6f40d038d15038331bc34b9f135e078d68f1/build.gradle#L20
https://github.com/apache/geode/blob/964b6f40d038d15038331bc34b9f135e078d68f1/build.gradle#L23
https://github.com/apache/geode/blob/964b6f40d038d15038331bc34b9f135e078d68f1/build.gradle#L61
Storm:
https://github.com/apache/storm/blob/8a475696e908c53f1c06bf1a8f373d8ac0483427/external/storm-mqtt/pom.xml#L32-L43
https://github.com/apache/storm/blob/8a475696e908c53f1c06bf1a8f373d8ac0483427/external/storm-hdfs/pom.xml#L38-L43
https://github.com/apache/storm/blob/604ecf7fc87ec25b3a2ac1269bc0bd0b4eea0a82/pom.xml#L1090-L1099
Storm (PRODUCTION SOURCE):
https://github.com/apache/storm/blob/21bb1388414d373572779289edc785c7e5aa52aa/storm-submit-tools/src/main/java/org/apache/storm/submit/dependency/Booter.java#L50
Bigtop:
https://github.com/apache/bigtop/blob/2c3490cc3a1c564354cfeb35601452beb7e41eba/bigtop-bigpetstore/bigpetstore-transaction-queue/build.gradle#L45-L47
https://github.com/apache/bigtop/blob/2c3490cc3a1c564354cfeb35601452beb7e41eba/bigtop-tests/smoke-tests/odpi-runtime/build.gradle#L22-L26
Airavata:
https://github.com/apache/airavata/blob/eb07965fbe9028e21c40bb0ed0f331603762c781/modules/user-profile-migration/pom.xml#L24-L34
https://github.com/apache/airavata/blob/eb07965fbe9028e21c40bb0ed0f331603762c781/pom.xml#L538-L573
Buildr:
https://github.com/apache/buildr/blob/6f357ea1b19576ccaab9259638af7dd9b2e3b43d/tests/generateFromPom/pom.xml#L275-L286
https://github.com/apache/buildr/blob/6f357ea1b19576ccaab9259638af7dd9b2e3b43d/tests/generateFromPom/pom.xml#L288-L348
Drat:
https://github.com/apache/drat/blob/b9b71db12001526d507bbc9d748e882d6b81bc2e/pom.xml#L19-L34
Tomee (Examples):
https://github.com/apache/tomee/search?l=Maven+POM&p=1&q=%3Curl%3Ehttp%3A%2F%2F
I'm almost completely certain I haven't found all of the instances of
this vulnerability in Apache Projects. I'd reccomend that the Apache
Security team reach out to all of it's project maintainers using Maven
or Gradle and request that they check their software for this
vulnerability.
Exploitability
This isn't just a theoretical attack vector; POC code exists already
to maliciously compromise jar file inflight as part of a MITM attack
https://max.computer/blog/how-to-take-over-the-computer-of-any-java-or-clojure-or-scala-developer/
https://github.com/mveytsman/dilettante
Additionally, MITM attacks aren't rare either:
https://serverfault.com/a/153065
https://security.stackexchange.com/a/12050
ISPs like Comcast have a history of using their MITM position to
inject Javascript into webpages loaded over HTTP (2017):
https://thenextweb.com/insights/2017/12/11/comcast-continues-to-inject-its-own-code-into-websites-you-visit/
{code}
> Download plugins via https only
> ---
>
> Key: SLING-8369
> URL: https://issues.apache.org/jira/browse/SLING-8369
> Project: Sling
> Issue Type: Improvement
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Parent 36
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SLING-8370) SonarCloud: enlist committer cli and project archetype repositories
[ https://issues.apache.org/jira/browse/SLING-8370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823332#comment-16823332 ] Fabrice Bellingard commented on SLING-8370: --- Done [~rombert]! > SonarCloud: enlist committer cli and project archetype repositories > --- > > Key: SLING-8370 > URL: https://issues.apache.org/jira/browse/SLING-8370 > Project: Sling > Issue Type: Task > Components: Build and Source Control >Reporter: Robert Munteanu >Priority: Major > > We have two new repositories > * https://github.com/apache/sling-org-apache-sling-committer-cli > * http://github.com/apache/sling-project-archetype > These need to be activated in SonarCloud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[RESULT] [VOTE] Apache Sling Journal based Content Distribution first release
Hi, The vote has passed with the following result : +1 (binding): Radu Cotescu, Robert Munteanu, Nicolas Peltier +1 (non binding): Christian Schneider Could a member of the PMC please push the release to the Sling dist directory ? Regards, Timothee
[jira] [Closed] (SLING-8317) Update to newest sling-maven-plugin
[ https://issues.apache.org/jira/browse/SLING-8317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8317. -- > Update to newest sling-maven-plugin > --- > > Key: SLING-8317 > URL: https://issues.apache.org/jira/browse/SLING-8317 > Project: Sling > Issue Type: Improvement > Components: General >Affects Versions: Parent 34 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Bundle Parent 35 > > > We should upgrade to the newest sling-maven-plugin (with the modified > artifact id, SLING-8204). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SLING-8094) Add OSGi sling servlet annotations to dependencyMgmt
[ https://issues.apache.org/jira/browse/SLING-8094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8094. -- > Add OSGi sling servlet annotations to dependencyMgmt > > > Key: SLING-8094 > URL: https://issues.apache.org/jira/browse/SLING-8094 > Project: Sling > Issue Type: Improvement > Components: General >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Bundle Parent 35 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SLING-8318) Update to bnd 4.2.0
[ https://issues.apache.org/jira/browse/SLING-8318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8318. -- > Update to bnd 4.2.0 > --- > > Key: SLING-8318 > URL: https://issues.apache.org/jira/browse/SLING-8318 > Project: Sling > Issue Type: Improvement > Components: General >Affects Versions: Parent 34 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Bundle Parent 35 > > > Some interesting changes are implemented with 4.2: > https://github.com/bndtools/bnd/wiki/Changes-in-4.2.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SLING-8201) Ban Felix SCR annotations dependency
[ https://issues.apache.org/jira/browse/SLING-8201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8201. -- > Ban Felix SCR annotations dependency > > > Key: SLING-8201 > URL: https://issues.apache.org/jira/browse/SLING-8201 > Project: Sling > Issue Type: Improvement > Components: General >Affects Versions: Parent 34 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Bundle Parent 35 > > > As we already banned maven-scr-plugin in SLING-6746 and using the scr bnd > plugin was discussed but disregarded in > https://issues.apache.org/jira/browse/SLING-6746?focusedCommentId=15947047&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15947047 > we should also ban the dependency to the old Felix SCR annotations to > prevent issues like SLING-8197. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SLING-8093) Raise OSGi annotations and DS, metatype and configuration admin versions to R7
[ https://issues.apache.org/jira/browse/SLING-8093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8093. -- > Raise OSGi annotations and DS, metatype and configuration admin versions to R7 > -- > > Key: SLING-8093 > URL: https://issues.apache.org/jira/browse/SLING-8093 > Project: Sling > Issue Type: Improvement >Affects Versions: Parent 34 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Bundle Parent 35 > > > Compare with SLING-8090. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SLING-8199) Allow building for Java 10, 11 and 12
[
https://issues.apache.org/jira/browse/SLING-8199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-8199.
--
> Allow building for Java 10, 11 and 12
> -
>
> Key: SLING-8199
> URL: https://issues.apache.org/jira/browse/SLING-8199
> Project: Sling
> Issue Type: Improvement
> Components: General
>Affects Versions: Parent 34
>Reporter: Konrad Windszus
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Parent 35
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently the property {{sling.java.version}} only allows values from 6-9.
> This should be extended to at least also support Java 10, 11 and 12 but
> rather also Java versions above.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (SLING-8285) Update plugins to work with Java11+
[ https://issues.apache.org/jira/browse/SLING-8285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8285. -- > Update plugins to work with Java11+ > --- > > Key: SLING-8285 > URL: https://issues.apache.org/jira/browse/SLING-8285 > Project: Sling > Issue Type: Improvement > Components: General >Affects Versions: Parent 34 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Parent 35 > > > The current surefire plugin we use in the parent pom does not work with Java > 11, I guesss in general it makes sense to update all plugins to the latest. > THis is the list: > [INFO] maven-compiler-plugin .. 3.7.0 -> 3.8.0 > [INFO] maven-dependency-plugin 3.0.2 -> 3.1.1 > [INFO] maven-deploy-plugin . 2.8.2 -> 3.0.0-M1 > [INFO] maven-enforcer-plugin 3.0.0-M1 -> 3.0.0-M2 > [INFO] maven-failsafe-plugin .. 2.20.1 -> 3.0.0-M3 > [INFO] maven-jar-plugin ... 3.0.2 -> 3.1.1 > [INFO] maven-javadoc-plugin ... 3.0.0 -> 3.0.1 > [INFO] maven-surefire-plugin .. 2.20.1 -> 3.0.0-M3 > [INFO] maven-surefire-report-plugin ... 2.20.1 -> 3.0.0-M3 > [INFO] maven-war-plugin ... 3.2.0 -> 3.2.2 > [INFO] org.apache.sling:slingstart-maven-plugin .. 1.7.16 -> 1.8.2 > [INFO] org.codehaus.cargo:cargo-maven2-plugin . 1.6.6 -> 1.7.2 > [INFO] org.codehaus.mojo:animal-sniffer-maven-plugin 1.16 -> 1.17 > [INFO] org.jacoco:jacoco-maven-plugin . 0.7.9 -> 0.8.3 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SLING-8008) Create dedicated parent for bundle projects
[ https://issues.apache.org/jira/browse/SLING-8008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8008. -- > Create dedicated parent for bundle projects > --- > > Key: SLING-8008 > URL: https://issues.apache.org/jira/browse/SLING-8008 > Project: Sling > Issue Type: Improvement > Components: General >Affects Versions: Parent 34 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Parent 35, Bundle Parent 35 > > Time Spent: 20m > Remaining Estimate: 0h > > As followup to the Sling Hackathon in Berlin in September (compare with > [https://www.mail-archive.com/dev@sling.apache.org/msg79953.html > |https://www.mail-archive.com/dev@sling.apache.org/msg79953.html).]there is > the proposal to split up the current parent pom into two pieces: one for > JARs/general aspect, another one for bundles (covering only those aspects). > > The reasons for this switch are: > - we would like to switch completely to bnd-maven-plugin, but without the > need for a separate bnd file > - we currently have only one parent pom for bundle modules and non-bundle > modules, making it difficult to configure the bnd-maven-plugin globally so it > gets up picked only for bundles, not for simple jar files. > - using maven profiles would be an option, but there is no nice way to > trigger the profile without ugly hacks like having an empty bnd file present. > - https://issues.apache.org/jira/browse/MJAR-193 would be another solution > (haven the bnd plugin handing over the manifest extensions to the maven jar > plugin), but this feature is not available yet > > The proposed solutions looks like this > - create an additional "sling-bundle-parent" inheriting from the existing > "sling-parent" > - all bundle-related stuff goes there and will be removed from "sling-parent" > - old maven-bundle-plugin and bnd-maven-plugin should be removed from > sling-parent > - maven-bundle-plugin should be banned from sling-bundle-parent > - one repo for both, always released together > - start with next version 36 > - make a wiki page with migration steps > - bundle modules will use "sling-bundle-parent", jar modules "sling-parent" > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SLING-8212) Parent: Replace maven-sling-plugin with sling-maven-plugin and ban old artifact id
[ https://issues.apache.org/jira/browse/SLING-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8212. -- > Parent: Replace maven-sling-plugin with sling-maven-plugin and ban old > artifact id > -- > > Key: SLING-8212 > URL: https://issues.apache.org/jira/browse/SLING-8212 > Project: Sling > Issue Type: Improvement > Components: Tooling >Affects Versions: Parent 34 >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Major > Fix For: Parent 35, Bundle Parent 35 > > > follow-up of SLING-8204 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[RESULT] [VOTE] Release Apache Sling Parent 35, Apache Sling Bundle Parent 35
Hi, The vote has passed with the following result: +1 (binding): Radu Cotescu, Carsten Ziegeler, Robert Munteanu, Nicolas Peltier +1 (non-binding): none I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Regards, Robert Munteanu
[jira] [Commented] (SLING-8370) SonarCloud: enlist committer cli and project archetype repositories
[ https://issues.apache.org/jira/browse/SLING-8370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822979#comment-16822979 ] Robert Munteanu commented on SLING-8370: [~bellingard] - can you help us with activating the two mentioned projects? Thanks! > SonarCloud: enlist committer cli and project archetype repositories > --- > > Key: SLING-8370 > URL: https://issues.apache.org/jira/browse/SLING-8370 > Project: Sling > Issue Type: Task > Components: Build and Source Control >Reporter: Robert Munteanu >Priority: Major > > We have two new repositories > * https://github.com/apache/sling-org-apache-sling-committer-cli > * http://github.com/apache/sling-project-archetype > These need to be activated in SonarCloud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SLING-8370) SonarCloud: enlist committer cli and project archetype repositories
Robert Munteanu created SLING-8370: -- Summary: SonarCloud: enlist committer cli and project archetype repositories Key: SLING-8370 URL: https://issues.apache.org/jira/browse/SLING-8370 Project: Sling Issue Type: Task Components: Build and Source Control Reporter: Robert Munteanu We have two new repositories * https://github.com/apache/sling-org-apache-sling-committer-cli * http://github.com/apache/sling-project-archetype These need to be activated in SonarCloud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Feature Model Based Sling Launchpad
Hi Andy, On Fri, 2019-04-19 at 18:26 -0700, Andreas Schaefer wrote: > Hi > > I found a solution for the OSGi dependencies issues by adding these > properties to the framework-properties: > > "felix.systempackages.substitution":"true", > "felix.systempackages.calculate.uses":"true" > > Now Sling starts up but is stuck in the never ending startup loop. It > looks like that no JCR repository is created. Looking at the README, especially the part that says The 3 non-activating bundles should be prevent Sling from starting but when I open http://localhost:8080 I get the If you start me up page and it stays there I would suggest to remove the 'starter.startup' bundle and see if that at least allows you to access the system console and see what is going on. https://github.com/schaefa/sling-featuremodel-starter/blob/92a0441e53f2e5e6591565d7527cea2f5eddeb1f/src/main/features/sling_sling.json#L264 Thanks, Robert > > - Andy > > > On Apr 19, 2019, at 1:56 PM, Andreas Schaefer < > > schaef...@me.com.INVALID> wrote: > > > > Hi > > > > This is my project where I try to convert Sling Starter to a > > Feature Model based starter: > > > > https://github.com/schaefa/sling-featuremodel-starter > > > > The Readme file contains the instruction on how to build and start > > it as well as my findings and how I converted the Sling 11 > > Provisioning Model into a Feature Model. That was not as straight > > forward as I expected it but I got it done. > > > > That said the missing bundles should not affect Sling but when > > opening the landing page (or any other page for that matter like > > Composum) leads me to the Starting Up page and it looks like Sling > > is never getting out of the starting up page. > > > > Any help is appreciated. > > > > Cheers - Andy Schaefer > > > > > On Apr 19, 2019, at 12:27 AM, Robert Munteanu > > > wrote: > > > > > > Hi Andy, > > > > > > On Thu, 2019-04-18 at 18:04 -0700, Andreas Schaefer wrote: > > > > Hi > > > > > > > > Since a few days I try to make Sling Launchpad starting from a > > > > Feature Model of the Sling Starter kit. > > > > > > > > After I converted all the provisioning files to a FM I wanted > > > > launch > > > > it but that does failed due to javax dependency issues. > > > > > > > > Eventually I found a solution by adding all the necessary > > > > packages to > > > > org.osgi.framework.system.packages.extra property and that > > > > works to > > > > most part except for exporting javax.xml.stream. > > > > > > > > When comparing the FM to the Provisioning Model bundles then I > > > > see > > > > that in the PM bundle 0: org.apache.felix.framework is > > > > exporting many > > > > javax packages but not in the FM launch. > > > > > > > > Is there a flag to make this happening? > > > > > > I don't have an answer but maybe if you put up what you have done > > > so > > > far on a repo on Github it might be easier to see what is > > > missing. > > > > > > Thanks, > > > > > > Robert
[GitHub] [sling-parent] rombert commented on issue #6: Update pom.xml
rombert commented on issue #6: Update pom.xml URL: https://github.com/apache/sling-parent/pull/6#issuecomment-485377751 Thanks for the pull request @ottlinger . We generally create Jira issues for all code changes. I created one already https://issues.apache.org/jira/browse/SLING-8369 Can you please amend your commit to include the SLING-8369 in the summary? Thanks! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (SLING-8369) Download plugins via https only
Robert Munteanu created SLING-8369: -- Summary: Download plugins via https only Key: SLING-8369 URL: https://issues.apache.org/jira/browse/SLING-8369 Project: Sling Issue Type: Improvement Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Parent 36 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
