This bug was last touched in 2008.
Current CUPS 1.5.0 connects via http://127.0.0.1:631 just fine
Administration page prompts for user and pass.
Closing since this is an ancient bug.
** Changed in: cupsys (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you a
I am getting this issue with my ipmonitor server as well, it self signs
the certificate itself, but not my PABX (switchvox) and as far as i know
its signing by itself too.
--
default ssl certificate is invalid
https://bugs.launchpad.net/bugs/187341
You received this bug notification because you a
It would be fine if the error is sec_error_untrusted_issuer for me, but
I got sec_error_inadequate_key_usage for all the servers using self
signed certs. Firefox 3 Beta 4 lets me add an exception, but Beta 5 just
gives me a flat out error. I had to use a different browser just to use
the sites I ne
Umm, that's not true. Self-signed certs can be be over-ridden.
Furthermore, the error is "The certificate is not trusted because it is
self signed. (Error code: sec_error_untrusted_issuer)" and not
"Certificate key usage inadequate for attempted operation. (Error code:
sec_error_inadequate_key_us
As of Firefox 3 Beta 5, and possibly new updates to Firefox 2, all self-
signed certs are considered invalid, and is done in such a way that you
can never bypass them. I encountered this when I recently updated Hardy.
I hope that the firefox developers are looking into this, as when I
search around
Not sure. I believe it is missing one of the Certificate Key Usage
attributes which firefox feels is required. The list of all certificate
key usage values is here:
http://www.mozilla.org/projects/security/pki/nss/tech-notes/tn3.html
However, I'm not sure which usage values firefox wants.
You ca
Alex: specifically which attribute?
I'm trying to troubleshoot a similar issue with a the self-signed cert
in Sage ( http://sagemath.org ) generated by gnutls:
http://trac.sagemath.org/sage_trac/ticket/1754
Perhaps Mozilla people could provide a document about how to make self-
signed certs work
No it's not. Firefox (correctly) gives the error "The certificate is
not trusted because it is self signed." for a self-signed cert, and
allows you to add an exception (the last as of beta 3)
The problem is with one of the other attributes of the certificate which
cupsys uses by default.
** Chan
I can reproduce this when trying to access an IBM Hardware Management
Console (an appliance to manage POWER-based machines).
Env.: Firefox 3 beta 3, up-to-date Hardy Haron.
Looks like Firefox 3 isn't accepting self-signed certificates anymore -
a workaround (button to add to exception list) would
This is a Firefox3 issue with self-signed certificates
** Changed in: firefox-3.0 (Ubuntu)
Sourcepackagename: cupsys => firefox-3.0
Status: Incomplete => Confirmed
--
default ssl certificate is invalid
https://bugs.launchpad.net/bugs/187341
You received this bug notification because you a
I am using firefox 3 on a hardy machine to connect to a cups server
running dapper. The printer is a network printer.
--
default ssl certificate is invalid
https://bugs.launchpad.net/bugs/187341
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Could you give more details as I'm not sure what you are trying.
You are using firefox 3 (on a dapper machine?) to connect to a printer
remotely? What machine is the printer connected to?
** Changed in: cupsys (Ubuntu)
Status: New => Incomplete
--
default ssl certificate is invalid
https
Lame Workaround:
In order to open a website that would give this error I downloaded the latest
2.* version from a binary (2.0.0.12 tar.gz), extracted and started Firefox
2.0.0.12. From there I was able to accept the certificate and open the website.
The certificate was automatically transfer to
13 matches
Mail list logo
