I stand corrected: Lucid has indeed all the correct patches applied.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/854946
Title:
Rampart's configuration on Ubuntu's package
I stand corrected: Lucid has indeed all the correct patches applied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854946
Title:
Rampart's configuration on Ubuntu's package doesn't define a default
** Changed in: eucalyptus (Ubuntu Oneiric)
Assignee: (unassigned) = James Page (james-page)
** Changed in: eucalyptus (Ubuntu Oneiric)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Branch linked: lp:~james-page/ubuntu/oneiric/eucalyptus/fix-
sslv3-compat
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/854946
Title:
Rampart's configuration on Ubuntu's
Graziano
Will this effect eucalyptus 1.6 in lucid as well? or is it constrained
to = 2.0?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/854946
Title:
Rampart's configuration
This bug was fixed in the package eucalyptus - 2.0.1+bzr1256-0ubuntu8
---
eucalyptus (2.0.1+bzr1256-0ubuntu8) oneiric; urgency=low
* Fix compatibility issues with SSLv3 (LP: #851611):
- d/patches/29-euca_conf-sslv3.patch: Use --secure-protocol=SSLv3
with wget when
** Branch linked: lp:ubuntu/eucalyptus
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/854946
Title:
Rampart's configuration on Ubuntu's package doesn't define a default
James,
for 1.6.2 (lucid) a similar set of patches were sent I think at about
the same time, but I can be mistaken here. A cursory look seems to imply
that they were not applied to Lucid. I am digging through my email
graveyard to find them: I will forward them to you as soon as I find
them.
** Changed in: eucalyptus (Ubuntu Oneiric)
Assignee: (unassigned) = James Page (james-page)
** Changed in: eucalyptus (Ubuntu Oneiric)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~james-page/ubuntu/oneiric/eucalyptus/fix-
sslv3-compat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854946
Title:
Rampart's configuration on Ubuntu's package doesn't define a
Graziano
Will this effect eucalyptus 1.6 in lucid as well? or is it constrained
to = 2.0?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854946
Title:
Rampart's configuration on Ubuntu's package
This bug was fixed in the package eucalyptus - 2.0.1+bzr1256-0ubuntu8
---
eucalyptus (2.0.1+bzr1256-0ubuntu8) oneiric; urgency=low
* Fix compatibility issues with SSLv3 (LP: #851611):
- d/patches/29-euca_conf-sslv3.patch: Use --secure-protocol=SSLv3
with wget when
** Branch linked: lp:ubuntu/eucalyptus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854946
Title:
Rampart's configuration on Ubuntu's package doesn't define a default
ClockSkewBuffer
To manage
James,
for 1.6.2 (lucid) a similar set of patches were sent I think at about
the same time, but I can be mistaken here. A cursory look seems to imply
that they were not applied to Lucid. I am digging through my email
graveyard to find them: I will forward them to you as soon as I find
them.
This issue was solved in Eucalyptus 2.0.3 (upstream) with the attached
patch. It's just a 2 liners that ensure rampartC policy to be more
lenient on the time difference.
** Patch added: clock_drift.patch
Thanks for raising this graziano, and attaching a patch.. Am i correct
in saying this should have been part of the security update?
Thanks.
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
** Changed in: eucalyptus (Ubuntu)
Status: New = Confirmed
** Changed in:
Thanks for the quick answer! Yes it was part of our 2.0.3 release, which
was a security release only. My understanding (which I can confirm if
you want) is that with the addition of more stringent rules for
rampartC, this second patch was needed to allow communication between
components when the
This issue was solved in Eucalyptus 2.0.3 (upstream) with the attached
patch. It's just a 2 liners that ensure rampartC policy to be more
lenient on the time difference.
** Patch added: clock_drift.patch
Thanks for raising this graziano, and attaching a patch.. Am i correct
in saying this should have been part of the security update?
Thanks.
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
** Changed in: eucalyptus (Ubuntu)
Status: New = Confirmed
** Changed in:
Thanks for the quick answer! Yes it was part of our 2.0.3 release, which
was a security release only. My understanding (which I can confirm if
you want) is that with the addition of more stringent rules for
rampartC, this second patch was needed to allow communication between
components when the
20 matches
Mail list logo
