6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Courier auth appl...
FromSent OnAttachments
Lindsay HaisleyJul 5, 2006 3:33 pm 
Alessandro VeselyJul 6, 2006 2:08 am 
AndrewJul 14, 2006 6:29 pm 
Sam VarshavchikJul 14, 2006 7:01 pm 
Charles FryJul 14, 2006 9:15 pm 
Sam VarshavchikJul 15, 2006 4:50 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Courier auth application ??Actions...
From:Andrew (and@arda.homeunix.net)
Date:Jul 14, 2006 6:29:16 pm
List:net.sourceforge.lists.courier-users

Alessandro Vesely wrote:

Lindsay Haisley writes:

I can always query the database (authmysql) directly, but since I'm going to publish this I'd rather at least use a method which will work with courier across any auth mechanism supported by the current courier configuration.

I have a script doing that using authtest (it works with ancient versions also) For more than sporadic use, I would hack authtest to produce a suid executable that does directly what you're after.

AFAIK you need to be root to access authdaemond's socket.

AFAIK this is only because of permissions set on the socket or the directory it is in.

Can anyone tell me what the permissions are when you install courier-authlib straight from it's tarball or from an rpm? I run courier-authlib on FreeBSD and I've installed it from the FreeBSD port. In that scenario the socket is created with permissions set to 777 and is owned by root:courier but the directory it's in has permissions 750 and is owned by courier:courier.

Andrew