From: nyc4bos@aol.com
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 11205@debbugs.gnu.org
Subject: bug#11205: 24.0.95; starttls-use-gnutls no longer being honored
Date: Fri, 20 Apr 2012 16:07:39 -0400 [thread overview]
Message-ID: <84fwby88vo.fsf@aol.com> (raw)
In-Reply-To: <m3lim379ri.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 10 Apr 2012 19:54:25 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Glenn Morris <rgm@gnu.org> writes:
>
>> You could always try redefining gnutls-available-p to return nil, eg:
>>
>> (defalias 'gnutls-available-p 'ignore)
>
> Yes. In any case, this is neither a regression, nor a bug. The
> variable in question controls what external program is used; not whether
> to use an external program or not. So I'm closing this bug report.
The variable, `starttls-use-gnutls' docstring says:
"*Whether to use GnuTLS instead of the `starttls' command."
So if I'm understanding the docstring right, if it is nil, whatever is
the `starttls' command should be used, NOT GnuTLS.
[The defcustom really says:
(defcustom starttls-use-gnutls (not (executable-find starttls-program)))]
This appears to me to be a regression since setting `starttls-use-gnustls'
to nil still uses GnuTLS (when `starttls-program' is accessible), unlike
Emacs 23.4.
At a minimum, this is a documentation bug with regard to Emacs 24.
Can you explain to me why should a user now jump through more hoops
to use another program such as OpenSSL, in order to use TLS?
Setting `starttls-use-gnutls' to nil works just fine in Emacs 23.4
Thanks.
next prev parent reply other threads:[~2012-04-20 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 0:54 bug#11205: 24.0.95; starttls-use-gnutls no longer being honored nyc4bos
2012-04-09 1:04 ` Glenn Morris
2012-04-10 3:03 ` nyc4bos
2012-04-10 17:43 ` Glenn Morris
2012-04-10 17:54 ` Lars Magne Ingebrigtsen
2012-04-20 20:07 ` nyc4bos [this message]
2012-05-13 19:21 ` Lars Magne Ingebrigtsen
2012-06-10 1:05 ` nyc4bos
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84fwby88vo.fsf@aol.com \
--to=nyc4bos@aol.com \
--cc=11205@debbugs.gnu.org \
--cc=larsi@gnus.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).