9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] I prefer cropping images in Plan 9
Date: Tue, 24 Jul 2018 01:25:26 +0100	[thread overview]
Message-ID: <405a16677cff006ab0f91c2a588a12b9@quintile.net> (raw)
In-Reply-To: <CAFSF3XPOxi=c+YCL2YceN3SXSyb6cCXEMTddpEEh4043PSHnRw@mail.gmail.com>

Intriguing.

how is p9sk1 completely unsafe?

I didn't believe the key exchange contained enough cleartext to make it
realisticly breakable, however I may be fooling myself.

I am not saying it cannot be improved upon, but I didn't think it was insecure.

-Steve			[sent from my plan9 using p9sk1]



  reply	other threads:[~2018-07-24  0:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-21 13:19 Ethan A. Gardener
2018-07-21 15:20 ` Ryan Gonzalez
2018-07-21 16:17   ` hiro
2018-07-22  9:42     ` Ethan A. Gardener
2018-07-22  9:27   ` Ethan A. Gardener
2018-07-22 11:24   ` Ethan A. Gardener
2018-07-23  3:55   ` Lucio De Re
2018-07-23  7:19     ` hiro
2018-07-24  0:25       ` Steve Simon [this message]
2018-07-24  7:46         ` hiro

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=405a16677cff006ab0f91c2a588a12b9@quintile.net \
    --to=steve@quintile.net \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).