Bug 348501
Summary: | Port xen to use NSS library for cryptography | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Vrabec <pvrabec> |
Component: | xen | Assignee: | Xen Maintainance List <xen-maint> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | tmraz |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-23 14:42:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 348661 | ||
Bug Blocks: | 333741 |
Description
Peter Vrabec
2007-10-23 10:24:14 UTC
Is there a Python binding for NSS ? Without one this bug can't be addressed. Having considered this ticket. XenD only uses SSL for the XenAPI service. We don't use this in Fedora, since libvirt provides the management service. So I've no interest in wasting time porting XenAPI. The Xen device model uses QEMU which has SSL. We are trying to get Xen to use upstream QEMU codebase rather than its own private fork. Porting Xen's QEMU to NSS will just make it an even worse fork compared to upstream QEMU which is not a sustainable approach. |