I am thinking about installing ebox and have a few questions, I wonder if anyone can help?
I see, from the documentation, I can use data stored in ldap to authenticate windows clients. Most of my machines are linux - can they authenticate via ebox or must this be set up separately? Can the shares, set up by ebox, be served to linux machines by nfs rather than samba using ebox or must I manually export them? If I set up http to authorize and filter and my windows or linux boxes authenticate via ebox, will this cover http access or do they get asked to authenticate explicitly for http access? I hope they are not separately asked but the documentation did not make it clear what happens. If I understood the documentation correctly I assume I could define a group with any internet access (filtered http content if required) and another with just, for example, access to pop3/smtp only and one with no access at all to the wide and worrysome world in any shape or form. Is this a correct interpretation? - I do hope so. Lastly, could I start off with a gateway box (dns, dhcp, http proxy, ldap etc) so users could safely access the net and authenticate. Later add another ebox to do groupware or web server perhaps. Could I, using ebox, also have a second ldap server and sync it to the original one so users could still authenticate on the network even if we lost the gateway temporarily? Many thanks for you help - from what I have read, so far, ebox looks like it might be just the thing I need but I'm not yet sure.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ ebox-user mailing list [email protected] http://lists.ebox-platform.com/cgi-bin/mailman/listinfo/ebox-user
