Displaying 3 results from an estimated 3 matches for "secret2".
Did you mean:
secret
2013 Sep 30
1
multiple secrets file
...to work :
(...)
secrets file = /etc/rsyncd/secrets1.inc
&include = /etc/rsyncd/mymodules1/
secrets file = /etc/rsyncd/secrets2.inc
&include = /etc/rsyncd/mymodules2/
(...)
ie. any modules declared in mymodules1/ will use users/passwords in
secret1.inc whereas mymodules2/ modules will use secret2.inc.
is it the right way to implement this ?
sorry if the question has been asked before
thanks
Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/rsync/attachments/20130930/970248ad/attachment.html>
2011 Mar 10
1
Access restriction on Upgrade Debian lenny -> Debian squeeze
...2/32
ACCEPT localhost
ACCEPT webinterface
ACCEPT slave
REJECT all
and in upsd.users:
[monmaster]
password = secret0
allowfrom = localhost
upsmon master
[monslave]
password = secret1
allowfrom = slave
upsmon slave
[admin]
password = secret2
actions = SET
instcmds = ALL
allowfrom = webinterface
Although upsd runs in a secured, private network, I would like to
restrict the access.
However, after upgrading from Debian lenny to Debian squeeze (version
2.4.3-1.1squeeze1) I get the messages in syslog:
ACL in...
2007 Sep 11
4
Questions about the new idmap interface
Hi,
I tried to configure the new idmap interface. Currently without much success.
I have two samba domains, trusting each other. Each PDC using it's own LDAP
server. I tried
idmap domains = DOM1, DOM2
idmap config DOM1:default = yes
idmap config DOM1:backend = ldap
idmap config DOM1:ldap_base_dn = ou=Idmap,dc=dom1,dc=mydomain,dc=de
idmap config