From: presotto@closedmind.org
To: 9fans@cse.psu.edu
Subject: [9fans] authentication protocol question
Date: Thu, 1 Nov 2001 14:01:05 -0500 [thread overview]
Message-ID: <20011101190106.6A9D8199DD@mail.cse.psu.edu> (raw)
The race is on the client side. There can be a number
of simultaneous attaches through the same communications
channel. Nothing synchronizes them so the authentications
can come out of order. The important part is that the
id's aren't reused.
next reply other threads:[~2001-11-01 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-01 19:01 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-01 18:57 Mike Haertel
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=20011101190106.6A9D8199DD@mail.cse.psu.edu \
--to=presotto@closedmind.org \
--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).