Many thanks, that clarifies several things for me :-) would I be right to assume version 1.3 would be timed to come out with the next LTS version of Ubuntu next year or is there no connection in the release cycles? If I install 1.2 now is it a simple matter to upgrade newer versions later (apt-get) or is it more tricky than that? (assuming 1.3 will still be on 8.04)
On Wednesday 23 September 2009 15:28:03 Isaac Clerencia wrote: > On Wed, Sep 23, 2009 at 1:14 PM, Peter Roots <[email protected]> wrote: > > I am thinking about installing ebox and have a few questions, I wonder if > > anyone can help? > > Sure :) > > > 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? > > They can authenticate against the eBox LDAP too. You'll have to set it > up in the linux clients manually. There is an experimental package for > Ubuntu to automate this but it does more things that you probably > don't want: > http://trac.ebox-platform.com/wiki/Document/Documentation/EboxDesktop > > Ask if you have any problem with the set up in the clients. > > > 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? > > Not by eBox, you'll have to do it manually. > > > 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. > > They will be asked twice. Sorry about this, we'll try to work on it :) > > > 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. > > Yes, you can do that. > > > 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? > > Starting with the alpha-series 1.3.X you can configure an eBox as > slave of another one. At the moment, that basically means that they > basically share the users and groups. They are automatically > replicated so if the master is down the slave can indeed be used for > authentication. You can configure the clients so they use both LDAPs > for auth, so if the master fails they automatically use the slave > without any manual operation. > > > 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. > > You are welcome, feel free to ask again if you have any doubts :) >
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
