From: Lars Ingebrigtsen <larsi@gnus.org>
To: Roland Winkler <winkler@gnu.org>
Cc: 9017@debbugs.gnu.org
Subject: bug#9017: 24.0.50; gnutls.c: [0] (Emacs) fatal error: Key usage violation in certificate has been detected.
Date: Wed, 25 Jan 2012 23:35:35 +0100 [thread overview]
Message-ID: <87mx9bh0lk.fsf@gnus.org> (raw)
In-Reply-To: <87wr8fbegb.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 25 Jan 2012 16:32:52 -0600")
Ted Zlatanov <tzz@lifelogs.com> writes:
> "This certificate restricts its usage to key encipherment. For TLS this
> is restricted to only the RSA key exchange. By misconfiguration however
> the server allows you to connect with a ciphersuite that violates this
> usage and that's why gnutls-cli fails to connect."
I'm afraid I don't understand what this is saying at all. :-)
> I may be misunderstanding the intent, but I thought globally you're
> saying you'll allow restricted certificates. I'm not sure that's ideal
> and I think it is insecure, but I'm not so sure anymore after thinking
> about it more carefully.
>
> Either way it seems that `gnutls-algorithm-priority' will have to be one
> of those string-or-alist-or-function variables, so you can disable
> security altogether for specific hosts that need it. I can add that
> support if you think it's reasonable.
I think the nice way to handle this would be to prompt the user here.
With something like "The server provides buggy dhe-rsa credentials;
connect anyway?" or something, which would result in "-dhe-rsa" being
added to the variable.
But as you point out, it should be on a per-host basis, probably...
--
(domestic pets only, the antidote for overdose, milk.)
http://lars.ingebrigtsen.no * Sent from my Rome
next prev parent reply other threads:[~2012-01-25 22:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 13:36 bug#9017: 24.0.50; gnutls.c: [0] (Emacs) fatal error: Key usage violation in certificate has been detected Roland Winkler
2011-07-07 14:42 ` Lars Magne Ingebrigtsen
2011-07-07 14:45 ` Lars Magne Ingebrigtsen
2011-07-07 14:56 ` Lars Magne Ingebrigtsen
2011-07-07 15:15 ` Lars Magne Ingebrigtsen
2011-07-08 0:49 ` Roland Winkler
2011-07-10 13:39 ` Lars Magne Ingebrigtsen
2011-07-11 13:59 ` Roland Winkler
2011-07-11 14:12 ` Lars Magne Ingebrigtsen
2011-07-11 14:29 ` Roland Winkler
2011-07-11 14:38 ` Lars Magne Ingebrigtsen
2011-07-11 14:54 ` Roland Winkler
2011-07-11 15:13 ` Lars Magne Ingebrigtsen
2011-07-11 15:41 ` Roland Winkler
2011-07-11 15:48 ` Lars Magne Ingebrigtsen
2011-07-13 15:02 ` Roland Winkler
2011-07-13 15:27 ` Lars Magne Ingebrigtsen
2011-07-13 16:06 ` Roland Winkler
2011-07-15 11:16 ` Roland Winkler
2011-07-15 19:56 ` Ted Zlatanov
2011-07-15 16:04 ` Lars Magne Ingebrigtsen
2011-07-15 16:04 ` Lars Magne Ingebrigtsen
2011-07-15 16:45 ` Ted Zlatanov
2011-07-15 17:13 ` Lars Magne Ingebrigtsen
2011-07-15 19:50 ` Ted Zlatanov
2011-07-15 17:26 ` Lars Magne Ingebrigtsen
2011-07-17 0:37 ` Roland Winkler
2011-07-17 0:44 ` Lars Magne Ingebrigtsen
2011-07-17 12:20 ` Roland Winkler
2011-07-17 16:15 ` Lars Magne Ingebrigtsen
2011-07-18 2:46 ` Roland Winkler
2012-01-25 20:29 ` Ted Zlatanov
2012-01-25 19:39 ` Lars Ingebrigtsen
2012-01-25 22:32 ` Ted Zlatanov
2012-01-25 22:35 ` Lars Ingebrigtsen [this message]
2012-01-26 15:40 ` Ted Zlatanov
2012-01-26 16:53 ` Lars Ingebrigtsen
2014-12-08 19:51 ` Lars Magne Ingebrigtsen
2011-07-16 17:57 ` Stefan Monnier
2011-07-17 2:19 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mx9bh0lk.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=9017@debbugs.gnu.org \
--cc=winkler@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.