On Fri, 14 Oct 2005, Hugo Monteiro wrote:
- LDAP backend
pro - Highly secure connections. (SSL/TLS, certificates, ACLs, etc)
Hmm, you can have SSL und TLS, but where comes the authentification
information from? Do you sit beside the computer to install and enter the
passphrase of the private key each time, the computer reboots?
Do you have the passphrase in the image, ready to be taken by anybody who
fortunately sit at the next computer in the lab?
I'm thinking that you overexagerate the usefulness of SSL in this
situation, unless you can secure the install process heavily.
pro - Hability for the agent to seamlessly change it's own record state
while installing. One can think of scheduling installs (boot on lan) and
provide installed/not installed state.
See above.
Also: The tag in the LDAP server is "passive"; if you want to act on it,
you have to poll it. I'd thinking about a server waiting for "DONE"
packets and update and reconfigures the DHCP menu at time.
con - At this time, that i know of, there is no code done to support
this.
con - it's "yet another backend". Some will be more familliar with LDAP
than CSV or mySQL (well, I am, too); but the other ones won't see no
advantage. I would probably prefer LDAP over CSV, too, but I'm also able
to put together a script that streams the data from LDAP into CSV.
con - At this time, that i know of, there is no LDAP schema to support
this.
Well, that's a "pro" actually in my mind. You haven't written that very
same con with mySQL.
Bye,
--
Steffen Kaiser
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
unattended-info mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unattended-info
