From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <0e9c57584ba73e5bf15a328b92752b93@plan9.bell-labs.com>
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Auth mess (i made it; u got a broom?)
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-pdnqqddjcbhcxesuvrntpgpbjz"
Date: Thu, 23 May 2002 09:11:07 -0400
Topicbox-Message-UUID: 9af383d4-eaca-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-pdnqqddjcbhcxesuvrntpgpbjz
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

I just tried one with the password !@#$%^&*().  It works fine.
When exactly did you find special characters not working?
I thought I'ld fixed before rsc's general announcement that
things were available.
--upas-pdnqqddjcbhcxesuvrntpgpbjz
Content-Type: message/rfc822
Content-Disposition: inline

Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Thu May 23 09:00:29 EDT 2002
Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Thu May 23 09:00:28 EDT 2002
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
	id 56C95199EE; Thu, 23 May 2002 09:00:14 -0400 (EDT)
Delivered-To: 9fans@cse.psu.edu
Received: from acl.lanl.gov (plan9.acl.lanl.gov [128.165.147.177])
	by mail.cse.psu.edu (CSE Mail Server) with SMTP id DEE4519999
	for <9fans@cse.psu.edu>; Thu, 23 May 2002 08:59:48 -0400 (EDT)
Message-ID: <393e1b701619dbe82ceb5f14628fe6b0@acl.lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Auth mess (i made it; u got a broom?)
From: andrey mirtchovski <andrey@lanl.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.11
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <https://lists.cse.psu.edu/archives/9fans/>
Date: Thu, 23 May 2002 06:58:32 -0600

> as well as ensuring proper authdom entries, you should also
> check that /lib/ndb/auth on the auth server has appropriate contents.
> initiallly the file contains only a comment explaining how to set it up.


one more thing -- make sure the password is weak (i.e.  contains no
non-alphanumeric characters).  they somehow get mangled during the
registration ( '!'  becomes %21 for example) and you will be unable to
login..


we found that out the hard way :)

--upas-pdnqqddjcbhcxesuvrntpgpbjz--