unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <lmi@gnus.org>
To: nljlistbox2@gmail.com (N. Jackson)
Cc: help-gnu-emacs@gnu.org
Subject: Re: User interface to bad certificate warning -- how to use?
Date: Mon, 01 Feb 2016 06:02:25 +0100	[thread overview]
Message-ID: <8760y9qazi.fsf@gnus.org> (raw)
In-Reply-To: <mailman.3266.1454274013.843.help-gnu-emacs@gnu.org> (N. Jackson's message of "Sun, 31 Jan 2016 16:53:45 -0400")

nljlistbox2@gmail.com (N. Jackson) writes:

> The warning is shown in a help window while simultaneously there is a
> prompt displayed in the minibuffer:
>
>     Continue connecting? (No, Session only, Always)
>
> Is the user intended to type in the full text of their choice or the
> first letter or what? If the first letter, must it be capitalised as
> shown?

I think the standard in Emacs is to use capitalisation to say what
characters you're supposed to hit.

> The prompt seems to disappear when _any_ key is pressed; for
> example I tried to copy the prompt to the clipboard and it disappeared
> when I started to select it -- I've no idea which of the three choices
> it decided I had entered. This seems rather surprising behaviour for the
> minibuffer.

I don't think that's what happened.  When you tried selecting the text,
you probably ended up aborting the function, just as if you'd hit `C-g'.

> After the prompt is gone, the help window remains but the buffer itself
> is gone. This seems to be rather the opposite of what would be useful.
> Wouldn't it be better if the buffer with the details about the
> problematic certificate persisted and the help window was closed?

The help window should have gone away.  Please report this as a bug with
`M-x report-emacs-bug'.

> Furthermore, the information in the help buffer is in a confusing order:
>
>     Certificate information
>     Issued by:          imap.example.com
>     Issued to:          IMAP server
>     Hostname:           imap.example.com
>     Public key:         RSA, signature: RSA-SHA1
>     Protocol:           TLS1.2, key: ECDHE-RSA, cipher: AES-128-GCM, mac: AEAD
>     Security level:     Low
>     Valid:              From 2013-09-07 to 2014-09-07
>
>     The TLS connection to localhost:993 is insecure for the following
>     reasons:
>
>     certificate signer was not found (self-signed)
>     certificate host does not match hostname
>     certificate has expired
>     the certificate was signed by an unknown and therefore untrusted authority
>     certificate could not be verified
>
> Would it not be better if the statement of the problem "The TLS
> connection ... is insecure" came first, and the detailed certificate
> information came at the end.

Yeah, that might be better...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



       reply	other threads:[~2016-02-01  5:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3266.1454274013.843.help-gnu-emacs@gnu.org>
2016-02-01  5:02 ` Lars Magne Ingebrigtsen [this message]
2016-02-02  2:17   ` User interface to bad certificate warning -- how to use? N. Jackson
     [not found]   ` <mailman.3380.1454379463.843.help-gnu-emacs@gnu.org>
2016-02-02  3:57     ` Lars Magne Ingebrigtsen
2016-02-02 20:38       ` N. Jackson
2016-01-31 20:53 N. Jackson

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=8760y9qazi.fsf@gnus.org \
    --to=lmi@gnus.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=nljlistbox2@gmail.com \
    /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.
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).