From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15866@debbugs.gnu.org, Lars Magne Ingebrigtsen <larsi@gnus.org>,
emacs@kosowsky.org
Subject: bug#15866: Gnutls elisp code doesn't properly check for file existence
Date: Mon, 08 Dec 2014 08:40:40 +0100 [thread overview]
Message-ID: <87iohma8sn.fsf@gmx.de> (raw)
In-Reply-To: <8361dmzuif.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 08 Dec 2014 05:32:24 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
>> Cc: monnier@iro.umontreal.ca, michael.albinus@gmx.de,
>> 15866@debbugs.gnu.org, emacs@kosowsky.org
>> Date: Sun, 07 Dec 2014 22:15:23 +0100
>>
>> perhaps just binding that variable to nil unconditionally would be
>> the right thing here?
>
> AFAIR, that was the conclusion.
Likely, yes.
I don't know whether there will be a certificate file ca.gpg, which is
protected by GPG, and which would not be accessible then. But due to the
nature of certificates they shall be readable, so maybe we can ignore
such a case.
Best regards, Michael.
next prev parent reply other threads:[~2014-12-08 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 0:20 bug#15866: Gnutls elisp code doesn't properly check for file existence emacs
2013-11-12 17:48 ` Eli Zaretskii
2013-11-12 18:12 ` emacs
2013-11-12 19:41 ` Ted Zlatanov
2013-11-12 19:52 ` Michael Albinus
2013-11-12 20:27 ` Stefan Monnier
2014-12-07 20:17 ` Lars Magne Ingebrigtsen
2014-12-07 21:08 ` Eli Zaretskii
2014-12-07 21:15 ` Lars Magne Ingebrigtsen
2014-12-08 3:32 ` Eli Zaretskii
2014-12-08 7:40 ` Michael Albinus [this message]
2014-12-08 18:14 ` Lars Magne Ingebrigtsen
2014-12-08 7:34 ` Michael Albinus
2013-11-12 20:02 ` Stefan Monnier
2013-11-16 23:34 ` Ted Zlatanov
2013-11-17 1:51 ` Stefan Monnier
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=87iohma8sn.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=15866@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacs@kosowsky.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).