From: "Satyaki Das" <satyakid@stanford.edu>
Subject: uses of pgg-truncate-key-identifier
Date: Sun, 09 Nov 2003 20:42:26 -0800 [thread overview]
Message-ID: <25979.1068439346@chicory.stanford.edu> (raw)
I noticed that the macro `pgg-truncate-key-identifier' is used in
the `pgg-read-passphrase' and `pgg-add-passphrase-cache'
functions. Since those functions could take a user name of length
greater than eight as the key, this could lead to problems.
From my reading of the code it seems that we can eliminate the
(setq key (pgg-truncate-key-identifier key))
expr from both functions.
Satyaki
reply other threads:[~2003-11-10 4:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=25979.1068439346@chicory.stanford.edu \
--to=satyakid@stanford.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).