From: Christopher.Vance@adfa.oz.au Christopher.Vance@adfa.oz.au
Subject: encrypt/decrypt not thread safe
Date: Wed, 16 Oct 1996 17:03:24 +1000 [thread overview]
Message-ID: <19961016070324.tQLq1qoUOlozt9C0THiEroyQlfvNAO0iMGTv6q3xt0Y@z> (raw)
forsyth@plan9.cs.york.ac.uk wrote:
| the version of the routine you've picked (looks like the old unix one,
| also non-exportable, but people slip up) isn't safe. i'm fairly sure
| the binary version shipped as crypt.*.save is fine.
| boyd might be able to offer a safe replacement that's not subject to pointless controls.
The previous CD-ROM did include source and I'm sure Beto can get hold
of it. Is the source on that CD-ROM identical to the currently
invisible source?
-- Christopher
next reply other threads:[~1996-10-16 7:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-16 7:03 Christopher.Vance [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-10-17 9:07 Boyd
1996-10-16 7:49 forsyth
1996-10-16 6:09 forsyth
1996-10-16 6:07 forsyth
1996-10-15 23:02 beto
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=19961016070324.tQLq1qoUOlozt9C0THiEroyQlfvNAO0iMGTv6q3xt0Y@z \
--to=christopher.vance@adfa.oz.au \
/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).