[GitHub] [jclouds] dependabot[bot] opened a new pull request, #140: Bump bcprov-ext-jdk15on from 1.60 to 1.67 in /drivers/bouncycastle
dependabot[bot] opened a new pull request, #140: URL: https://github.com/apache/jclouds/pull/140 Bumps [bcprov-ext-jdk15on](https://github.com/bcgit/bc-java) from 1.60 to 1.67. Changelog Sourced from https://github.com/bcgit/bc-java/blob/master/docs/releasenotes.html";>bcprov-ext-jdk15on's changelog. 2.1.1 Version Release: 1.71 Date: 2022, March 31st. ... (truncated) Commits See full diff in https://github.com/bcgit/bc-java/commits";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/jclouds/network/alerts). -- 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. To unsubscribe, e-mail: notifications-unsubscr...@jclouds.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [jclouds] dependabot[bot] opened a new pull request, #138: Bump logback-classic from 1.1.2 to 1.2.0 in /project
dependabot[bot] opened a new pull request, #138: URL: https://github.com/apache/jclouds/pull/138 Bumps logback-classic from 1.1.2 to 1.2.0. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/jclouds/network/alerts). -- 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. To unsubscribe, e-mail: notifications-unsubscr...@jclouds.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [jclouds] dependabot[bot] opened a new pull request, #139: Bump logback-core from 1.1.2 to 1.2.9 in /project
dependabot[bot] opened a new pull request, #139: URL: https://github.com/apache/jclouds/pull/139 Bumps logback-core from 1.1.2 to 1.2.9. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/jclouds/network/alerts). -- 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. To unsubscribe, e-mail: notifications-unsubscr...@jclouds.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [jclouds] dependabot[bot] opened a new pull request, #137: Bump httpclient from 4.3.6 to 4.5.13 in /drivers/apachehc
dependabot[bot] opened a new pull request, #137: URL: https://github.com/apache/jclouds/pull/137 Bumps httpclient from 4.3.6 to 4.5.13. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/jclouds/network/alerts). -- 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. To unsubscribe, e-mail: notifications-unsubscr...@jclouds.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (JCLOUDS-1601) upgrade log4j due to security issue
[ https://issues.apache.org/jira/browse/JCLOUDS-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated JCLOUDS-1601: - Affects Version/s: 2.5.0 > upgrade log4j due to security issue > --- > > Key: JCLOUDS-1601 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1601 > Project: jclouds > Issue Type: Bug >Affects Versions: 2.5.0 >Reporter: PJ Fanning >Assignee: Andrew Gaul >Priority: Major > Fix For: 2.6.0 > > > There is a CVE against v2.17.0 > https://github.com/apache/jclouds/blob/master/project/pom.xml#L239 > https://logging.apache.org/log4j/2.x/security.html > Also, logback version is old (next line in pom) > https://mvnrepository.com/artifact/ch.qos.logback/logback-core -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JCLOUDS-1604) use non-beta/rc versions of auto-factory
[ https://issues.apache.org/jira/browse/JCLOUDS-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated JCLOUDS-1604: - Affects Version/s: 2.5.0 > use non-beta/rc versions of auto-factory > > > Key: JCLOUDS-1604 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1604 > Project: jclouds > Issue Type: Improvement >Affects Versions: 2.5.0 >Reporter: PJ Fanning >Assignee: Andrew Gaul >Priority: Major > Fix For: 2.6.0 > > > auto-factory and auto-service appear to have official releases now > see https://github.com/apache/jclouds/blob/master/project/pom.xml#L229 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JCLOUDS-1604) use non-beta/rc versions of auto-factory
[ https://issues.apache.org/jira/browse/JCLOUDS-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated JCLOUDS-1604: - Fix Version/s: 2.6.0 > use non-beta/rc versions of auto-factory > > > Key: JCLOUDS-1604 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1604 > Project: jclouds > Issue Type: Improvement >Reporter: PJ Fanning >Assignee: Andrew Gaul >Priority: Major > Fix For: 2.6.0 > > > auto-factory and auto-service appear to have official releases now > see https://github.com/apache/jclouds/blob/master/project/pom.xml#L229 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (JCLOUDS-1601) upgrade log4j due to security issue
[ https://issues.apache.org/jira/browse/JCLOUDS-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul resolved JCLOUDS-1601. -- Resolution: Fixed > upgrade log4j due to security issue > --- > > Key: JCLOUDS-1601 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1601 > Project: jclouds > Issue Type: Bug > Components: jclouds-core >Affects Versions: 2.5.0 >Reporter: PJ Fanning >Assignee: Andrew Gaul >Priority: Major > Fix For: 2.6.0 > > > There is a CVE against v2.17.0 > https://github.com/apache/jclouds/blob/master/project/pom.xml#L239 > https://logging.apache.org/log4j/2.x/security.html > Also, logback version is old (next line in pom) > https://mvnrepository.com/artifact/ch.qos.logback/logback-core -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JCLOUDS-1601) upgrade log4j due to security issue
[ https://issues.apache.org/jira/browse/JCLOUDS-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated JCLOUDS-1601: - Component/s: jclouds-core > upgrade log4j due to security issue > --- > > Key: JCLOUDS-1601 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1601 > Project: jclouds > Issue Type: Bug > Components: jclouds-core >Affects Versions: 2.5.0 >Reporter: PJ Fanning >Assignee: Andrew Gaul >Priority: Major > Fix For: 2.6.0 > > > There is a CVE against v2.17.0 > https://github.com/apache/jclouds/blob/master/project/pom.xml#L239 > https://logging.apache.org/log4j/2.x/security.html > Also, logback version is old (next line in pom) > https://mvnrepository.com/artifact/ch.qos.logback/logback-core -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JCLOUDS-1604) use non-beta/rc versions of auto-factory
[ https://issues.apache.org/jira/browse/JCLOUDS-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated JCLOUDS-1604: - Component/s: jclouds-core > use non-beta/rc versions of auto-factory > > > Key: JCLOUDS-1604 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1604 > Project: jclouds > Issue Type: Improvement > Components: jclouds-core >Affects Versions: 2.5.0 >Reporter: PJ Fanning >Assignee: Andrew Gaul >Priority: Major > Fix For: 2.6.0 > > > auto-factory and auto-service appear to have official releases now > see https://github.com/apache/jclouds/blob/master/project/pom.xml#L229 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (JCLOUDS-1604) use non-beta/rc versions of auto-factory
[ https://issues.apache.org/jira/browse/JCLOUDS-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul resolved JCLOUDS-1604. -- Resolution: Fixed > use non-beta/rc versions of auto-factory > > > Key: JCLOUDS-1604 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1604 > Project: jclouds > Issue Type: Improvement > Components: jclouds-core >Affects Versions: 2.5.0 >Reporter: PJ Fanning >Assignee: Andrew Gaul >Priority: Major > Fix For: 2.6.0 > > > auto-factory and auto-service appear to have official releases now > see https://github.com/apache/jclouds/blob/master/project/pom.xml#L229 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (JCLOUDS-1601) upgrade log4j due to security issue
[ https://issues.apache.org/jira/browse/JCLOUDS-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Gaul updated JCLOUDS-1601: - Fix Version/s: 2.6.0 > upgrade log4j due to security issue > --- > > Key: JCLOUDS-1601 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1601 > Project: jclouds > Issue Type: Bug >Reporter: PJ Fanning >Assignee: Andrew Gaul >Priority: Major > Fix For: 2.6.0 > > > There is a CVE against v2.17.0 > https://github.com/apache/jclouds/blob/master/project/pom.xml#L239 > https://logging.apache.org/log4j/2.x/security.html > Also, logback version is old (next line in pom) > https://mvnrepository.com/artifact/ch.qos.logback/logback-core -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JCLOUDS-1604) use non-beta/rc versions of auto-factory
[ https://issues.apache.org/jira/browse/JCLOUDS-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523687#comment-17523687 ] ASF subversion and git services commented on JCLOUDS-1604: -- Commit 27274d40a946b8d52e06757e3a18076cb73ab3b5 in jclouds's branch refs/heads/master from Andrew Gaul [ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=27274d40a9 ] JCLOUDS-1604: Upgrade to AutoFactory 1.0.1 > use non-beta/rc versions of auto-factory > > > Key: JCLOUDS-1604 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1604 > Project: jclouds > Issue Type: Improvement >Reporter: PJ Fanning >Assignee: Andrew Gaul >Priority: Major > > auto-factory and auto-service appear to have official releases now > see https://github.com/apache/jclouds/blob/master/project/pom.xml#L229 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JCLOUDS-1601) upgrade log4j due to security issue
[ https://issues.apache.org/jira/browse/JCLOUDS-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523688#comment-17523688 ] ASF subversion and git services commented on JCLOUDS-1601: -- Commit 659951bc63368bb1eed8d2e25b2ae5ed79476e56 in jclouds's branch refs/heads/master from Andrew Gaul [ https://gitbox.apache.org/repos/asf?p=jclouds.git;h=659951bc63 ] JCLOUDS-1601: Upgrade to log4j 2.17.2 Release notes: https://logging.apache.org/log4j/2.x/changes-report.html#a2.17.2 > upgrade log4j due to security issue > --- > > Key: JCLOUDS-1601 > URL: https://issues.apache.org/jira/browse/JCLOUDS-1601 > Project: jclouds > Issue Type: Bug >Reporter: PJ Fanning >Assignee: Andrew Gaul >Priority: Major > > There is a CVE against v2.17.0 > https://github.com/apache/jclouds/blob/master/project/pom.xml#L239 > https://logging.apache.org/log4j/2.x/security.html > Also, logback version is old (next line in pom) > https://mvnrepository.com/artifact/ch.qos.logback/logback-core -- This message was sent by Atlassian Jira (v8.20.1#820001)
