|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: pop3
From: spoon spoon (sp00n
GMX.DE)Date: Thu Apr 20 2000 - 11:23:28 CDT
- Next message: Gwendolynn ferch Elydyr: "Re: DOS attack against HP JetDirect Printers (fwd)"
- Previous message: dynamo: "Re: Network Security and Privacy"
- Next in thread: Christopher P. Lindsey: "Re: pop3"
- Reply: Christopher P. Lindsey: "Re: pop3"
- Reply: Jason Godsey: "Re: pop3"
- Reply: Kris Kennaway: "Re: pop3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>I noticed the following behavior in the pop3 server as shipped with
>Redhat 6.1 (still don't see
Qualcomms POP servers have this problem as well, on linux, solaris, etc.
Except the lock file gets stored where ever your users mail is stored.
/var/mail(on a sun) or where ever. I guess a nice solution would be to have a
subdirectory with mode 700 permissions under /var/mail/locks or something like
that where only the popper can write to. Or just ignore the lock if the owner
of the lock file is diffrent thant the userid of the person popping their
mail.
$ > .jqpublic.pop
$ id
uid=1001(testacct) gid=1(other)
$ pwd
/var/mail
$ ls -la | more
total 465698
drwxrwxrwt 3 root mail 6656 Apr 20 12:03 .
<cut>
-rw-r--r-- 1 testacct other 0 Apr 20 12:03 .jqpublic.pop
<cut>
+OK QPOP (version: 2.53) on solaris
jqpublic ant pop his mail
-- Sent through Global Message Exchange - http://www.gmx.net
- Next message: Gwendolynn ferch Elydyr: "Re: DOS attack against HP JetDirect Printers (fwd)"
- Previous message: dynamo: "Re: Network Security and Privacy"
- Next in thread: Christopher P. Lindsey: "Re: pop3"
- Reply: Christopher P. Lindsey: "Re: pop3"
- Reply: Jason Godsey: "Re: pop3"
- Reply: Kris Kennaway: "Re: pop3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]