Hi Arto,

What you say seems understandable and reasonable to me. Thanks for the
hints about the recommendations of the LSB ;)

Just one point, certainly a tad out off topic (but as we already
discussed about the client...) : as the "push" part of the agent mode
is supposed to now happen through triggers, I think this may be a case
for adding a bcfg2 system user, this time, not for the server (like
has been suggested in another bug), but rather for the client. At
least, this is probably what I intend to do, so to avoid direct
connection to the root acount : I may then allow the "bcfg2", or
"bcfg2-client", user to passwordless-ly sudo with root rights, to run
the bcfg2 command I need it to, and only this one (it may not change
much security-wise, in respect with directly connecting to root, with
the only right to issue this commandline, but management-wise, it'll
be clearer to me - if any and all network daemon that runs as root
needed to be replaced with ssh-ing to the root account, this could
really start getting unmanageable and unsortable - "sort of trashbin"
accounts are a pain, and root certainly does not need this). Just a
thought I think it may be not so useless to throw here. Could be
something to think about, and include in the README, when you fix the
agent disappearance...

Have a good day !



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to