From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: wyuenho@gmail.com, emacs-devel@gnu.org
Subject: Re: The netsec thread
Date: Fri, 20 Jul 2018 15:24:04 +0300 [thread overview]
Message-ID: <83bmb214ez.fsf@gnu.org> (raw)
In-Reply-To: <m3fu0ef8gg.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 20 Jul 2018 13:33:03 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 20 Jul 2018 13:33:03 +0200
> Cc: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
>
> I like the underlining, indentation and *bullet points, but it's looking
> like it's moving more in the direction of a TLS debugging buffer than
> something that a user has much chance of understanding or navigating.
> (The old one also has that problem, but to a lesser degree.)
>
> For instance, displaying the full x.50x/RFC4514 string is a turn-off and
> looks like line noise to most people, I think. Breaking out the three
> bits that are of interest, the CN from the issuer, the O from the
> recipient, and the host name, is more readable. (Not to mention that
> the strings are usually too long and will wrap on common
> configurations.)
Would it make sense to have a button "More details" there, which would
then display these details?
next prev parent reply other threads:[~2018-07-20 12:24 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 11:33 The netsec thread Lars Ingebrigtsen
2018-07-20 12:24 ` Eli Zaretskii [this message]
2018-07-20 12:33 ` Lars Ingebrigtsen
2018-07-20 12:36 ` Lars Ingebrigtsen
2018-07-20 12:41 ` Eli Zaretskii
2018-07-20 12:45 ` Lars Ingebrigtsen
2018-07-23 1:52 ` Jimmy Yuen Ho Wong
2018-07-23 1:55 ` Brett Gilio
2018-07-23 2:32 ` Eli Zaretskii
2018-07-23 12:46 ` Lars Ingebrigtsen
2018-07-23 13:31 ` Andy Moreton
2018-07-23 14:43 ` Jimmy Yuen Ho Wong
2018-07-23 14:46 ` Andy Moreton
2018-07-23 15:48 ` Lars Ingebrigtsen
2018-07-23 16:54 ` Andy Moreton
2018-07-23 19:34 ` Andy Moreton
2018-07-24 8:24 ` Lars Ingebrigtsen
2018-07-24 9:34 ` Andy Moreton
2018-07-24 11:54 ` Andy Moreton
2018-07-24 12:09 ` Noam Postavsky
2018-07-24 13:59 ` Jimmy Yuen Ho Wong
2018-07-24 14:11 ` Lars Ingebrigtsen
2018-07-24 18:21 ` Andy Moreton
2019-07-28 18:18 ` Lars Ingebrigtsen
2019-07-28 18:27 ` Eli Zaretskii
2019-07-28 18:33 ` Lars Ingebrigtsen
2019-07-28 18:34 ` Lars Ingebrigtsen
2019-07-28 19:08 ` Lars Ingebrigtsen
2019-07-28 19:12 ` Eli Zaretskii
2019-07-29 11:12 ` Lars Ingebrigtsen
2019-07-29 7:50 ` Robert Pluim
2019-07-29 8:11 ` Robert Pluim
2019-07-29 11:18 ` Lars Ingebrigtsen
2019-07-29 11:14 ` Lars Ingebrigtsen
2019-07-29 14:02 ` Robert Pluim
2019-07-30 11:30 ` Lars Ingebrigtsen
2019-07-30 13:12 ` Robert Pluim
2019-07-30 13:32 ` Lars Ingebrigtsen
2019-07-30 15:05 ` Robert Pluim
2019-08-07 12:27 ` Robert Pluim
2019-08-07 18:41 ` Lars Ingebrigtsen
2019-08-23 2:58 ` Lars Ingebrigtsen
2019-08-23 8:19 ` Paul Eggert
2019-08-23 8:52 ` Lars Ingebrigtsen
2019-08-23 9:01 ` Lars Ingebrigtsen
2019-08-23 19:03 ` Paul Eggert
2019-08-25 5:33 ` Lars Ingebrigtsen
2019-09-03 9:49 ` Robert Pluim
2019-09-03 13:30 ` Paul Eggert
2019-09-03 15:37 ` Robert Pluim
2019-09-03 19:20 ` Paul Eggert
2019-09-03 20:02 ` Robert Pluim
2019-09-04 13:12 ` Lars Ingebrigtsen
2019-09-04 19:34 ` Robert Pluim
2019-09-04 21:35 ` Paul Eggert
2019-09-04 21:54 ` Robert Pluim
2019-09-05 12:12 ` Robert Pluim
2019-09-05 18:50 ` Paul Eggert
2019-09-05 19:34 ` Robert Pluim
2019-09-04 13:10 ` Lars Ingebrigtsen
2019-08-23 9:09 ` Eli Zaretskii
2019-08-23 9:40 ` Robert Pluim
2019-08-23 12:18 ` Eli Zaretskii
2019-08-23 12:39 ` Robert Pluim
2019-08-23 13:03 ` Eli Zaretskii
2019-08-23 13:20 ` Robert Pluim
2019-08-23 14:15 ` Eli Zaretskii
2019-08-23 14:27 ` Robert Pluim
2019-08-23 14:40 ` Eli Zaretskii
2019-08-23 14:58 ` Robert Pluim
2019-08-23 15:04 ` Eli Zaretskii
2019-08-23 9:58 ` Lars Ingebrigtsen
2019-08-23 12:43 ` Eli Zaretskii
2019-08-25 5:32 ` Lars Ingebrigtsen
2019-08-25 22:29 ` Richard Stallman
2019-08-26 4:16 ` Lars Ingebrigtsen
2018-07-23 15:22 ` Eli Zaretskii
2018-07-22 14:48 ` Lars Ingebrigtsen
2018-07-23 0:12 ` Jimmy Yuen Ho Wong
2018-07-23 8:17 ` Robert Pluim
2018-07-23 14:58 ` Jimmy Yuen Ho Wong
2018-07-23 15:06 ` Robert Pluim
2018-07-23 15:37 ` Lars Ingebrigtsen
2018-07-23 15:51 ` Jimmy Yuen Ho Wong
2018-07-23 16:06 ` Noam Postavsky
2018-07-23 16:11 ` Lars Ingebrigtsen
2018-07-23 15:04 ` Eli Zaretskii
2018-07-23 15:24 ` Jimmy Yuen Ho Wong
2018-07-23 15:34 ` Robert Pluim
2018-07-23 16:38 ` Jimmy Yuen Ho Wong
2018-07-23 17:25 ` Robert Pluim
2018-07-23 17:54 ` Eli Zaretskii
2018-07-23 20:51 ` Robert Pluim
2018-07-23 9:55 ` Lars Ingebrigtsen
2018-07-23 15:22 ` Jimmy Yuen Ho Wong
2018-07-23 15:46 ` Lars Ingebrigtsen
2018-07-23 15:48 ` Jimmy Yuen Ho Wong
2018-07-23 15:49 ` Noam Postavsky
2018-07-23 16:13 ` Lars Ingebrigtsen
2018-07-23 10:23 ` Andreas Schwab
2018-07-20 12:55 ` Jimmy Yuen Ho Wong
2018-07-20 12:59 ` Jimmy Yuen Ho Wong
2018-07-20 13:00 ` Lars Ingebrigtsen
2018-07-20 13:11 ` Jimmy Yuen Ho Wong
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=83bmb214ez.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=wyuenho@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.
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).