From: Boyd Roberts boyd@france3.fr
Subject: encrypt/decrypt not thread safe
Date: Thu, 17 Oct 1996 11:07:17 +0200 [thread overview]
Message-ID: <19961017090717.lLRHkeqDxa62UVb4--TtSifHg5G90gWdirxicEPJnt8@z> (raw)
From: forsyth@plan9.cs.york.ac.uk
boyd might be able to offer a safe replacement that's not subject
to pointless controls.
you can certainly take my des from ftp://www.plan9.cs.su.oz.au/~boyd/des.msg
but it's not thread safe. it assumes it's being called by a single
threaded program. to fix it you need to have a per thread expanded
key. all you need to do is to change deskey() to accept a parameter
for where to store the expanded key , rather than storing it in a
global static. not real hard.
next reply other threads:[~1996-10-17 9:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-17 9:07 Boyd [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-10-16 7:49 forsyth
1996-10-16 7:03 Christopher.Vance
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=19961017090717.lLRHkeqDxa62UVb4--TtSifHg5G90gWdirxicEPJnt8@z \
--to=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).