From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: Date/Time?
Date: Wed, 23 May 2018 10:15:48 -0400 [thread overview]
Message-ID: <bccf72cb-f6c2-bb20-4724-aefdafd6d9bb@redhat.com> (raw)
In-Reply-To: <20180522092606.GA2440@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1602 bytes --]
On 05/22/2018 05:26 AM, speck for Greg KH wrote:
> On Tue, May 22, 2018 at 10:00:35AM +0200, speck for Peter Zijlstra wrote:
>> On Mon, May 21, 2018 at 04:30:27PM -0400, speck for Jon Masters wrote:
>>> Let's skip the FUD tho. It's not a "website". It's an open source
>>> end-to-end encrypted chat application.
>>
>> But it is not packaged by any distro afaik, so you basically have to
>> trust their webshite to fetch a binary, which is pretty dodgy if you ask
>> me.
>
> You mean you don't trust the "run a random binary from the internet as
> root?" instructions they provide you:
> https://keybase.io/docs/the_app/install_linux
Conversely, encrypted GPG email is so secure. Just last week, I recall
reading about how great it is that there are totally no problems.
Do I like the "run this binary" instructions? No. But you can also
download the source from github and build it. Which of course is totally
secure because we're all going to audit every line of the source before
we build it, just like people who rebuild Android because that's way
more secure than trusting the images they download. Just like how we all
audited our email and GPG implementations, as well as IRC clients, and
all of the other software we're running, completely.
So anyway, the above aside, I get it. The companies involved were
willing to use Keybase (which they suggested), so it was better than the
alternative of having no communications channel. There's a lot we can
learn collectively as an industry :)
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2018-05-23 14:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 17:26 [MODERATED] Date/Time? Greg KH
2018-05-19 17:51 ` [MODERATED] Date/Time? Borislav Petkov
2018-05-19 18:45 ` Linus Torvalds
2018-05-19 19:07 ` [MODERATED] " Borislav Petkov
2018-05-19 19:48 ` Linus Torvalds
2018-05-19 20:22 ` [MODERATED] " Borislav Petkov
2018-05-20 20:58 ` Jon Masters
2018-05-19 18:21 ` David Woodhouse
2018-05-19 19:05 ` Greg KH
2018-05-20 19:23 ` David Woodhouse
2018-05-20 23:01 ` David Woodhouse
2018-05-21 8:35 ` Greg KH
2018-05-20 17:45 ` Jiri Kosina
2018-05-20 18:19 ` Greg KH
2018-05-20 18:35 ` Borislav Petkov
2018-05-20 19:57 ` Greg KH
2018-05-20 18:36 ` Linus Torvalds
2018-05-20 18:48 ` Jiri Kosina
2018-05-20 20:59 ` Jon Masters
2018-05-20 21:09 ` Jiri Kosina
2018-05-21 6:11 ` Greg KH
2018-05-20 21:48 ` Linus Torvalds
2018-05-20 21:56 ` David Woodhouse
2018-05-21 6:16 ` Greg KH
2018-05-21 7:18 ` David Woodhouse
2018-05-21 15:23 ` Date/Time? Thomas Gleixner
2018-05-21 16:46 ` [MODERATED] Date/Time? Greg KH
2018-05-21 17:12 ` Konrad Rzeszutek Wilk
2018-05-21 19:42 ` Greg KH
2018-05-21 19:48 ` Jiri Kosina
2018-05-21 20:30 ` Jon Masters
2018-05-22 8:00 ` Peter Zijlstra
2018-05-22 9:26 ` Greg KH
2018-05-22 16:32 ` Andi Kleen
2018-05-23 14:15 ` Jon Masters [this message]
2018-05-21 17:22 ` Jon Masters
2018-05-21 18:56 ` Date/Time? Thomas Gleixner
2018-05-21 19:16 ` [MODERATED] Date/Time? Jon Masters
2018-05-21 20:43 ` Greg KH
2018-05-21 17:31 ` Jon Masters
2018-05-21 18:53 ` Date/Time? Thomas Gleixner
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=bccf72cb-f6c2-bb20-4724-aefdafd6d9bb@redhat.com \
--to=jcm@redhat.com \
--cc=speck@linutronix.de \
/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).