secure way to allow users create logbook, posted by Szu-Ching Peckner on Tue Aug 28 23:02:07 2012
|
I don't think there is a good secure way so far, but would like to have your opinion.
If I want user to create logbook for themselves, what's the best way to do it? I guess Execute $attribute = <command> may work, have it write |
Re: secure way to allow users create logbook, posted by Szu-Ching Peckner on Wed Aug 29 14:35:45 2012
|
Stefan Ritt wrote:
|
Re: secure way to allow users create logbook, posted by Szu-Ching Peckner on Wed Aug 29 18:16:37 2012
|
Stefan Ritt wrote:
|
|
Re: secure way to allow users create logbook, posted by Szu-Ching Peckner on Thu Aug 30 22:47:50 2012
|
Stefan Ritt wrote:
|
|
admin user access admin page, not config page, posted by Szu-Ching Peckner on Tue Sep 18 17:57:47 2012
|
We have multiple logbooks. Each user is admin user for his/her own logbook.
I want user be able to modify config file, but no access to user setting, such as see user list, change password, new user, remove user. |
|
hosts allow, posted by Susan James on Fri Nov 17 18:58:52 2017
|
I'm trying to wrap our elog instance to our company domain which is lbl.gov
I add this entry below (without quotes) to elogd.cfg and it's not working. the world can see our logbooks
" Hosts Allow = *.lbl.gov ". |
|
Re: hosts allow, posted by Susan James on Tue Nov 21 01:27:06 2017
|
thanks for your quick reply.
the configuration is still not working. See my entry below which denies everyone.
I've tried many different combinations of 'hosts allow and hosts deny' |
|
Re: hosts allow, posted by Susan James on Thu Dec 7 21:54:58 2017
|
Hi All,
We're still having trouble with hosts.allow and hosts.deny.
We're trying to allow all of our domain lbl.gov to the access list |