Merged to
[master](https://git-wip-us.apache.org/repos/asf?p=jclouds-site.git;a=commit;h=795753d69eaef5f5a97171c5377c9de993c0736b)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60532934
[jclouds-site-pull-requests
#429](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/429/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60490331
Go to
http://b1c90eabded8a2ca754d-abce231dea82c6db563d944416e4fa3b.r79.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60490367
[jclouds-site-pull-requests
#430](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/430/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60503925
Go to
http://adda73bfd30802a06c77-7ab43419ec96fec9828dcbacd72d1deb.r35.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60503961
[jclouds-site-pull-requests
#431](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/431/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60505574
Go to
http://a078da31cc53787ae9c9-84efa30bcec2ace12d6bd3dec65f9975.r5.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60505594
[jclouds-site-pull-requests
#424](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/424/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60349761
Go to
http://f864ab384a031a3a42ff-7621ac03bcc980806fdaede83f69cfa7.r71.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60349836
+1 I like that POODLE is simply a link and doesn't dominate the content on
the release.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60395907
[jclouds-site-pull-requests
#422](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/422/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60199058
Go to
http://37ab8e9990534a255e08-36b111363a513e7d2159e338dd56a3fc.r80.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60199127
Go to
http://ae7d8f7be770a72cb0f5-6ef7438193a84a7227bfd1177f7af9b2.r54.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60200065
[jclouds-site-pull-requests
#423](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/423/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-60200012
+jclouds only changes the SSL connection settings (rather than inheriting
them from the JVM) in two cases:
+
+1) If you are setting `jclouds.trust-all-certs=true`, i.e. are configuring
jclouds to trust **all** certificates
+
+If you are concerned about secure connections, it is almost
+jclouds only changes the SSL connection settings (rather than inheriting
them from the JVM) in two cases:
+
+1) If you are setting `jclouds.trust-all-certs=true`, i.e. are configuring
jclouds to trust **all** certificates
+
+If you are concerned about secure connections, it is almost
@@ -0,0 +1,73 @@
+---
+author: a href=http://blog.xebialabs.com/author/aphillips/;Andrew
Phillips/a
+comments: true
+date: 2014-10-22 23:30:00+00:00
+layout: post
+slug: poole-jclouds
+title: What POODLE means for jclouds
+---
+
+layout: post
+slug: poole-jclouds
+title: What POODLE means for jclouds
+---
+
+[POODLE](http://googleonlinesecurity.blogspot.com.au/2014/10/this-poodle-bites-exploiting-ssl-30.html)
is a recently discovered [man-in-the-middle
+layout: post
+slug: poole-jclouds
+title: What POODLE means for jclouds
+---
+
+[POODLE](http://googleonlinesecurity.blogspot.com.au/2014/10/this-poodle-bites-exploiting-ssl-30.html)
is a recently discovered [man-in-the-middle
+ What can I do to avoid being affected by POODLE?
+
+If you are concerned about POODLE, there are two main ways to avoid being
affected:
+
+* ensure that your provider no longer supports SSLv3
+
+Many cloud providers are disabling support for SSLv3 - the protocol version
exploited
+Many cloud providers are disabling support for SSLv3 - the protocol version
exploited by POODLE - on the server-side. Checking whether the cloud
providers you are talking to using jclouds have removed support for SSLv3 is
the easiest possible fix for you as a user, since it requires no
+// Example only! Choose the appropriate SSLContext settings for your
scenario!
+SSLContext sc = SSLContext.getInstance(TLS);
+sc.init(null, null, null);
+sc.getDefaultSSLParameters().setProtocols(new String[] { TLSv1, TLSv1.1,
TLSv1.2 });
+// use jclouds to make HTTPS connections to your cloud providers
+```
+
+ When does jclouds configure SSL connections itself?
+
+jclouds only changes the SSL connection settings (rather than inheriting
them from the JVM) in two cases:
+
+1) If you are setting
+
+jclouds only changes the SSL connection settings (rather than inheriting
them from the JVM) in two cases:
+
+1) If you are setting `jclouds.trust-all-certs=true`, i.e. are configuring
jclouds to trust **all** certificates
+
+If you are concerned about secure connections, it is almost
+If you are concerned about secure connections, it is almost never a good
idea to use this option in the first place. If you absolutely need to trust
all certificates _and_ disable SSLv3, you can:
+
+ * create an SSLContext with the appropriate settings (see
@@ -0,0 +1,73 @@
+---
+author: a href=http://blog.xebialabs.com/author/aphillips/;Andrew
Phillips/a
+comments: true
+date: 2014-10-22 23:30:00+00:00
+layout: post
+slug: poole-jclouds
+title: What POODLE means for jclouds
+---
General commentary is that we go into way too much detail
+1. [Highlights](#highlights)
+1. [API Changes](#api)
+1. [Known Issues](#issues)
+1. [Reminder](#reminder)
+1. [Credits](#credits)
+1. [Test Results](#test)
+
+## a id=intro/aIntroduction
+
+You can read the official announcement at [Apache jclouds 1.8.1
released](TODO). You can read
+ groupIdorg.apache.jclouds.apis/groupId
+ artifactIdopenstack-swift/artifactId
+ version1.8.1/version
+/dependency
+{% endhighlight %}
+
+
+## a id=api/aAPI Changes
+
+* [openstack-swift API changes from 1.8.0 to
1.8.1](api-changes/openstack-swift/)
+
+## a id=issues/aKnown
+If you are concerned about secure connections, it is almost never a good
idea to use this option in the first place. If you absolutely need to trust
all certificates _and_ disable SSLv3, you can:
+
+ * create an SSLContext with the appropriate settings (see
+If you are concerned about secure connections, it is almost never a good
idea to use this option in the first place. If you absolutely need to trust
all certificates _and_ disable SSLv3, you can:
+
+ * create an SSLContext with the appropriate settings (see
[jclouds-site-pull-requests
#420](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/420/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-59992828
[jclouds-site-pull-requests
#421](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/421/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-59994398
Go to
http://a989b96f8a7e6c6dc3c9-98845488d1067462a457fd6a2981b7bc.r44.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-59994569
I took a stab at providing detailed API changes in the release notes for
OpenStack Swift. Go to
$BASE_URL/releasenotes/1.8.1/api-changes/openstack-swift/ to see them.
Also fixed the error we were seeing earlier. Liquid didn't like the xx in the
date field.
---
Reply to this email directly or
You can merge this Pull Request by running:
git pull https://github.com/jclouds/jclouds-site 1.8.1-release-notes
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/138
-- Commit Summary --
* Initial strawman
-- File Changes --
M
+
+## a id=highlights/aHighlights
+
+* TODO
+* Graduation of OpenStack Swift
+* Lots of API cleanup
+
+## a id=api/aAPI Changes
+
+* TODO
+
+## a id=issues/aKnown Issues
+
+* TODO
+* TODO: A note on POODLE and jclouds 1.8.1
+* 1.8.0 includes an [incomplete
[jclouds-site-pull-requests
#416](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/416/)
FAILURE
Looks like there's a problem with this pull request
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/138#issuecomment-59678683
jclouds-site-pull-requests #416 FAILURE
Interesting error:
```
Configuration file:
/scratch/jenkins/workspace/jclouds-site-pull-requests/_config.yml
Source: /scratch/jenkins/workspace/jclouds-site-pull-requests
Destination:
38 matches
Mail list logo
