From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "bad authentication domain"
Date: Thu, 24 Apr 2003 13:15:27 -0400 [thread overview]
Message-ID: <1e2aeb795d8487e0700bf8449aaffcf0@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304240908060.3019-100000@maxroach.lanl.gov>
As the C compiler counts it, sizeof(Nvrsafe) is 112,
so your file is definitely too short. Maybe you set
nvrlen= something in your plan9.ini? That would be bad
if it were less than the safe size.
I see
struct Nvrsafe
{
char machkey[DESKEYLEN];
uchar machsum;
char authkey[DESKEYLEN];
uchar authsum;
char config[CONFIGLEN];
uchar configsum;
char authid[ANAMELEN];
uchar authidsum;
char authdom[DOMLEN];
uchar authdomsum;
};
g% hoc
7+1+7+1+14+1+28+1+48+1
109
g%
so I think if you have only 108 bytes,
that would explain why the authdom isn't
checksumming properly.
next prev parent reply other threads:[~2003-04-24 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 21:13 ron minnich
2003-04-24 12:20 ` Russ Cox
2003-04-24 15:08 ` ron minnich
2003-04-24 17:15 ` Russ Cox [this message]
2003-04-24 17:45 ` ron minnich
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=1e2aeb795d8487e0700bf8449aaffcf0@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).