| Summary: | urpmi should not use curl with https mirrors | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Manuel Hiebel <manuel.mageia> |
| Component: | RPM Packages | Assignee: | Guillaume Rousse <guillomovitch> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | urpmi | CVE: | |
| Status comment: | |||
|
Description
Manuel Hiebel
2012-05-03 19:30:06 CEST
If you want to trust an insecure sites that is your problem. What's need to be fixed is for this site to have either a real certificate or not to offer https (hint Guillaume...). Status:
NEW =>
RESOLVED Thanks for the gift, but why am I the assignee here :) ? Anyway, I disagree with Thierry: this is not really a server issue, but a client one. If you want to use https for secure connection, you're supposed to either give your client a way to check server certificate (meaning its certification authority certificate), or to disallow server certificate checking. The fact than the server doesn't use a certificate issued by a commercial provider just make it a bit more complex for the clients, but it's not a bug in itself. urpmi.cfg has a curl-options directive for this kind of issues. |