|
|
| Author |
Message |
| 25 new of 467 responses total. |
bhoward
|
|
response 50 of 467:
| 
Feb 4 22:35 UTC 2004 |
Yes, making them case sensitive creates an opportunity
for abuse and confusion with no benefit that I can see.
|
davel
|
|
response 51 of 467:
|
Feb 5 00:21 UTC 2004 |
And IIRC internet mail standards specify case-insensitivity. If so,
case-sensitive usernames could really be a problem.
|
gelinas
|
|
response 52 of 467:
|
Feb 5 00:25 UTC 2004 |
Last I heard, only for the right-hand side of the address, Dave. Way back
when, I saw a system that did, indeed, distinguish between people by
case-sensitivity.
|
sholmes
|
|
response 53 of 467:
|
Feb 5 03:23 UTC 2004 |
On yahoo though sending a mail to XYZ@yahoo.com and xyz@yahoo.com is the same.
|
remmers
|
|
response 54 of 467:
|
Feb 5 12:15 UTC 2004 |
From RFC 821: Simple Mail Transfer Protocol (Postel, 1982):
Commands and replies are not case sensitive. That is, a command or
reply word may be upper case, lower case, or any mixture of upper and
lower case. Note that this is not true of mailbox user names. For
some hosts the user name is case sensitive, and SMTP implementations
must take case to preserve the case of user names as they appear in
mailbox arguments. Host names are not case sensitive.
That said, I agree that case-sensitive usernames on NextGrex would be a
bad idea. (Are upper case characters in login id's even allowed on
Unixy systems? I don't think I've ever seen a login id with an upper
case character in it.)
|
jhudson
|
|
response 55 of 467:
|
Feb 5 18:08 UTC 2004 |
Yes, uppercase logins are allowed, but there is some warning about
it. Basically, from Unix System Administrator's Handbook, "Uppercase
characters are fine as long as the user won't be reciving any e-mail."
I wonder what would happen if somebody tried. You will have to
experiment.
|
ryan
|
|
response 56 of 467:
|
Feb 5 19:04 UTC 2004 |
This response has been erased.
|
naftee
|
|
response 57 of 467:
|
Feb 6 00:02 UTC 2004 |
Why? They'd probably improve your overall impression.
|
jared
|
|
response 58 of 467:
|
Feb 6 02:08 UTC 2004 |
re #54
Please don't quote obsoleted rfcs. rfc822 was obsoleted by rfc2822.
rfc 821 was obsoleted by rfc2821.
(warning, don't look at this url on dialup,
http://www.rfc-editor.org/rfc-index2.html)
As far as case sensitive usernames, don't allow.
|
naftee
|
|
response 59 of 467:
|
Feb 6 02:16 UTC 2004 |
I wonder if postel is still alive.
|
gelinas
|
|
response 60 of 467:
|
Feb 6 02:19 UTC 2004 |
No, he is not. :(
|
boltwitz
|
|
response 61 of 467:
|
Feb 6 04:33 UTC 2004 |
Is there anyone who's willing to do textual analysis of the world-wide corpus
of s-emetic writing, and then write a filter to keep jews off nextgrex?
|
gull
|
|
response 62 of 467:
|
Feb 6 15:37 UTC 2004 |
On some older UNIX systems, logging in with your username in all
uppercase would cause it to assume you had a terminal that could not
handle lowercase letters, with somewhat unpleasant results.
|
aruba
|
|
response 63 of 467:
|
Feb 6 23:24 UTC 2004 |
That's true on the present Grex.
|
remmers
|
|
response 64 of 467:
|
Feb 7 13:18 UTC 2004 |
Re #58: Oops, sorry about the obsolete quote. However, rfc2821 says
essentially the same thing about case-sensitivity that rfc821 did.
I think it would be reasonable on NextGrex not to allow uppercase
characters in login id's, and for the login program to map upper to
lower case at the "login:" prompt. The behavior that gull refers
to in #62 should probably go away. This is the twenty-first century,
after all.
|
twenex
|
|
response 65 of 467:
|
Feb 17 17:06 UTC 2004 |
Utterly bizarrely, it seems to be true on Debian 3.0, too, although some
proggies seem to disregard this rule.
|
eprom
|
|
response 66 of 467:
|
Mar 22 04:18 UTC 2004 |
What's the dilly yo?
|
janc
|
|
response 67 of 467:
|
Jul 23 19:45 UTC 2004 |
My plan is to resume work on NextGrex next week. I think the first step is
going to be to install OpenBSD 3.5
Well, there are a few other firster steps, like getting the machine turned
back on and checking to see if I remember the root password or not.
|
twenex
|
|
response 68 of 467:
|
Jul 23 21:22 UTC 2004 |
Er, what's on it now?
|
gelinas
|
|
response 69 of 467:
|
Jul 23 23:43 UTC 2004 |
OpenBSD 3.4, IIRC.
I don't know what is up with grease; I'll plan to visit the pumpkin after
supper, unless someone else gets there first.
|
gelinas
|
|
response 70 of 467:
|
Jul 24 01:23 UTC 2004 |
Yes, the machine was turned off. I don't know why. It's coming up now.
|
twenex
|
|
response 71 of 467:
|
Jul 25 00:59 UTC 2004 |
Re: #69. Ah.
|
naftee
|
|
response 72 of 467:
|
Jul 25 04:21 UTC 2004 |
Good point, twenex.
|
janc
|
|
response 73 of 467:
|
Aug 6 16:24 UTC 2004 |
I've upgraded Next Grex to OpenBSD 3.5, and reapplied all the
customizations that we'd worked out on previous rounds (except for
quotas which I've delayed reapplying because they make boots slower).
The rebuild process went pretty smoothly. Biggest problem was that
doing ftp installs is very slow over Grex's ethernet (and probably
contributed to some slow connections to Grex over the last couple days).
In the future we should probably burn all the files we need onto a CD
and walk them over to the pumpkin. I want us to be able to rebuild Grex
in under 24 hours.
I haven't actually tested that everything works as it is supposed to.
I'm going to turn now to fresh work. My list:
- port "robocop". It's unclear if we'll have the fork bomb kernal
mods that Marcus did on the current Grex. Without that, having
robocop becomes even more important.
- modify "newuser" to initialize disk quotas for new users.
- port "zapuser" and "lockuser" - these are the admin tools used to
delete/lock user accounts.
Kip is going to work on mail - main issue is mailbox quotas.
Heirarchical mail directories would be nice, but that doesn't
necessarily need to be in place before moving over to the new system.
As much spam filtering as we can afford without eating up the CPU would
be nice too.
If we go to hierarchical mail directories, we need to ensure that all
the mail clients understand them.
I think we need to port over Mic's menu shell, and possibly some of the
change/help scripts that Valerie mostly wrote.
I think that's all. Not really much.
|
aruba
|
|
response 74 of 467:
|
Aug 6 16:27 UTC 2004 |
Woo hoo!
|
