From: matt@proweb.co.uk
To: 9fans@cse.psu.edu
Subject: [9fans] secstore plain text dilema
Date: Tue, 17 Feb 2004 09:17:53 +0000 [thread overview]
Message-ID: <72ad4fdec0459c47a9b0e994eee2688b@juice.thebigchoice.com> (raw)
There I am on a client's network. I drawterm into home happily going about my business.
and then I'm presented with the dilema :-
%ftpfs somewhere
secstore password :
What's a guy to do?
Of course what I do is type in my secstore password because I *needed* to proceed but now I know I've just broadcast the combination to the safe that contains the crown jewels.
I feel safe enough that this time I'm safe but I'm not keen on making it a regular occurrence.
Is anyone working on encrypting drawterm's comms?
If not, what are my alternatives, except not use drawterm.
m
next reply other threads:[~2004-02-17 9:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 9:17 matt [this message]
2004-02-17 9:41 ` Matthias Teege
2004-02-17 10:01 ` Richard Miller
2004-02-17 14:04 ` David Presotto
2004-02-18 7:22 ` 9nut
2004-02-18 10:46 ` Richard Miller
2004-02-18 16:32 ` 9nut
2004-02-18 19:14 ` Richard Miller
2004-02-19 9:14 ` 9nut
2004-02-18 16:10 ` andrey mirtchovski
2004-02-20 18:15 ` Richard Miller
2004-02-21 7:06 ` 9nut
2004-02-17 15:00 ` Jim Choate
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=72ad4fdec0459c47a9b0e994eee2688b@juice.thebigchoice.com \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
/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).