This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When creating a Bodhi update request, please use the bodhi submission link noted in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the Bodhi notes field when available. Please note: this issue affects multiple supported versions of Fedora. Only one tracking bug has been filed; please ensure that it is only closed when all affected versions are fixed. [bug automatically created by: add-tracking-bugs]
Please use the following update submission link to create the Bodhi request for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. Please also ensure that the "Close bugs when update is stable" option remains checked. Bodhi update submission link: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=917084,917086
According to my knowledge about Maven and Maven Wagon, Maven 3.0.5 release notes [1] and Maven security information [2] this vulnerability does not affect the combinations of Maven and Maven Wagon we have in Fedora: Fedora 17: Maven 3.0.4, Maven Wagon 1.0 Fedora 18: Maven 3.0.4, Maven Wagon 1.0 Fedora 19: Maven 3.0.5, Maven Wagon 1.0 Because of the above I am closing this bug as WORKSFORME. If you have a working reproducer feel free to repoen. [1] http://maven.apache.org/docs/3.0.5/release-notes.html [2] http://maven.apache.org/security.html
Please see my comment here: https://bugzilla.redhat.com/show_bug.cgi?id=917084#c3 Unless Maven 3.0.5 introduces a dependency on 2.x (which doesn't seem to be the case based on the versions in Fedora 19), then it should be sufficient to bump Maven to 3.0.5 and leave Maven Wagon at 1.0. Please schedule the update to Maven (and leave Maven Wagon as-is). Thanks.
Works for me. Reproducer: $ rpm -q maven maven-wagon maven-3.0.4-28.fc19.noarch maven-wagon-1.0-6.fc18.noarch $ cat pom.xml <project> <artifactId>test</artifactId> <parent> <groupId>test</groupId> <artifactId>test2</artifactId> <version>test</version> </parent> <repositories> <repository> <id>test</id> <url>https://209.132.183.69/test</url> </repository> </repositories> </project> $ mvn [INFO] Scanning for projects... Downloading: https://209.132.183.69/test/test/test2/test/test2-test.pom [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project test:test:test (/tmp/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Could not transfer artifact test:test2:pom:test from/to test (https://209.132.183.69/test): Error transferring file: java.security.cert.CertificateException: No subject alternative names matching IP address 209.132.183.69 found and 'parent.relativePath' points at wrong local POM @ line 3, column 11 -> [Help 2] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException SSL certificates are checked by default, which I have shown above. Please don't reopen this bug unless you can prove otherwise.