Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
16
Installation and Upgrades / Re: Windows 2003 AD accounts migrate to Ebox
« on: September 15, 2008, 04:22:28 pm »
The domain's SID will change anyway, and you're going to have to re-associate all the machines to the domain (unless they are Win98,NT workstations), so don't get too bored about the password thing, 'cas that will be your minor problem... 
17
Installation and Upgrades / Re: printer sharing
« on: September 15, 2008, 04:19:45 pm »
Ok, found out what the problem was... It seems that, you've got to set up the printer access for each user... Go to the users module, edit a user, and then you will be able to choose which printers the user will have access to...
PS: I think it would be better if this access was enabled by default, or if there could be a group only for access the printers...
PS: I think it would be better if this access was enabled by default, or if there could be a group only for access the printers...
18
Installation and Upgrades / Re: Joining and authenticating a linux machine to an ebox domain.
« on: August 22, 2008, 02:01:39 pm »
Hi all. A couple of questions before trying your setup:
- Can you login on the domain without a corresponding user account on the machine? And if you can, how do you define that you can use audio devices, mount drives, setup printers, do sudo, etc...? The eBox LDAP structure is prepared for Windows, users don't belong to unix groups such as audio and sudo, that's why I ask... =\
- Is there a way to have this centralized authentication without using samba? samba is mostly used for windows, since the server is linux, there must be a more native way to perform client pc's authentication agains the server's ldap db
- What happens if you tray to login without a connection to the server (like a road warrior)? Will the system use a cached password or it won't allow you to log in?
- Can you login on the domain without a corresponding user account on the machine? And if you can, how do you define that you can use audio devices, mount drives, setup printers, do sudo, etc...? The eBox LDAP structure is prepared for Windows, users don't belong to unix groups such as audio and sudo, that's why I ask... =\
- Is there a way to have this centralized authentication without using samba? samba is mostly used for windows, since the server is linux, there must be a more native way to perform client pc's authentication agains the server's ldap db
- What happens if you tray to login without a connection to the server (like a road warrior)? Will the system use a cached password or it won't allow you to log in?
19
Installation and Upgrades / Re: Install ProFTPd with LDAP User Autentication
« on: August 22, 2008, 01:40:52 pm »
Post updated! Check the last "post update" line in the first post.
PS: I don't see what more can I do to make this better, it's now doing perfectly what it was supodes to do, so if someone finds a gap, let me know!
PS: I don't see what more can I do to make this better, it's now doing perfectly what it was supodes to do, so if someone finds a gap, let me know!
20
Installation and Upgrades / Re: Mail relay
« on: August 07, 2008, 11:56:19 am »
POP3 over SSL runs on port 995 (UDP+TCP)
SMTP over SSL runs on port 465 (TCP)
PS: if you want to know the common ports, do a "cat /etc/services". you can use the grep command to filter your request (ex: "cat /etc/services | grep pop").
SMTP over SSL runs on port 465 (TCP)
PS: if you want to know the common ports, do a "cat /etc/services". you can use the grep command to filter your request (ex: "cat /etc/services | grep pop").
21
Installation and Upgrades / Re: Mail relay
« on: August 06, 2008, 05:45:18 pm »
If your ISP uses TLS or SSL, then the ports would be diferent... It's that, or you haven't opened the ports correctly on the eBox firewall... 
22
Installation and Upgrades / Re: printer sharing
« on: August 05, 2008, 04:36:02 pm »
Hi.
Same problem here, printers that I add via eBox interface not showed via Samba :/
Ubuntu Hardy (Alternate CD)
eBox 0.11.101
2 printers (brother & laserjet)
Same problem here, printers that I add via eBox interface not showed via Samba :/
Ubuntu Hardy (Alternate CD)
eBox 0.11.101
2 printers (brother & laserjet)
23
Installation and Upgrades / Re: Mail relay
« on: August 05, 2008, 01:50:52 pm »
Can you telnet the pop3 or imap port of your isp's server?
24
Installation and Upgrades / Re: Install ProFTPd with LDAP User Autentication
« on: July 11, 2008, 10:59:39 am »
Post updated: file/folder owner now is showed up 
Thanks to the creator of the module for the tip on this.
Thanks to the creator of the module for the tip on this.
25
Installation and Upgrades / Re: oki B4300
« on: July 09, 2008, 04:35:12 pm »
patcunha, if it's a network printer, then you don't need to depend on eBox to print for it, just setup your windows clients to print to a TCP Port with the printer's address. Can you ping the printer's address? Can you telnet the network tcp port (telnet PRINTER_IP 9100)?
Sure, if it's a domain it would be nice to use it with samba to allow your users to see the queue of print jobs and stuff.. If eBox doesn't show up this printer's driver, you can use the ljet4 driver, since this one works perfectly!
Sure, if it's a domain it would be nice to use it with samba to allow your users to see the queue of print jobs and stuff.. If eBox doesn't show up this printer's driver, you can use the ljet4 driver, since this one works perfectly!
26
Installation and Upgrades / Re: use ebox database for other applications
« on: July 09, 2008, 11:46:29 am »
sandermans, for the ftp server, check this: http://forum.eboxplatform.com/index.php?topic=441.0
27
Installation and Upgrades / Re: Install ProFTPd with LDAP User Autentication
« on: July 08, 2008, 09:19:19 pm »
Post updated. The following options can be interesting...
MaxClients NUMBER "Max numbers of clients connected! Try again later"
MaxClientsPerHost NUMBER "Number of connections from your IP above what I allow..."
AccessGrantMsg "Granted access for %u."
Now, I could use some help with the server not being able to retrieve the owner of files and folders... Some option to tell proftpd to read the UID number of the user...!?
MaxClients NUMBER "Max numbers of clients connected! Try again later"
MaxClientsPerHost NUMBER "Number of connections from your IP above what I allow..."
AccessGrantMsg "Granted access for %u."
Now, I could use some help with the server not being able to retrieve the owner of files and folders... Some option to tell proftpd to read the UID number of the user...!?
28
Installation and Upgrades / Re: Import dhcp fixed adresses list
« on: July 08, 2008, 06:09:44 pm »
Very usefull yes! Thank you very much
29
Installation and Upgrades / Re: eBox with FTP Server
« on: July 08, 2008, 05:51:14 pm »
Done
http://forum.eboxplatform.com/index.php?topic=441.0
Are there plans to include this in future releases?
http://forum.eboxplatform.com/index.php?topic=441.0
Are there plans to include this in future releases?
30
Installation and Upgrades / Install ProFTPd with LDAP User Authentication
« on: July 08, 2008, 05:49:26 pm »
Hi all.
This HOW-TO will explain how to setup a ProFTPd Server with user authentication against the eBox LDAP User DataBase.
1 - You'll need an Ubuntu 8.04 box with eBox installed and the Users module activated.
2 - Install the proftpd ldap package (sudo apt-get install proftpd-ldap). During the installation, you'll be prompted to choose the way you want proftp to be started (inetd or standalone). Choose Standalone.
3 - Check and write down your eBox LDAP Admin Password (sudo cat /etc/ldap.secret)
4 - Check and write down your server's FQDN (cat /etc/hosts)
5 - Rename your /etc/proftpd/ldap.conf file. Then create a new empty file (sudo touch /etc/proftpd/ldap.conf) and paste the following text in it (replace the words in CAPITAL TEXT with its correct value for your environement)
6 - Rename your /etc/proftpd/proftpd.conf file. Then create a new empty file (sudo touch /etc/proftpd/proftpd.conf) and paste the following text in it (replace the CAPITAL TEXT with its correct value for your environement)
7 - I've noticed that, disableing some unused modules in modules.conf would somehow increase the password verification. So, if you want to try it out, paste the following content in your /etc/proftpd/modules.conf, otherwise, jump to no.8
8 - Restart the ProFTPd Server (sudo /etc/init.d/proftpd restart) and you're on!!!
Some notes:
- For debuging, do "tail -f /var/log/proftpd/proftpd.log" while using the server (be it logging in, logging out, restarting, etc...). You might want to change the "DebugLevel" value in proftpd.conf to it's max (9) so that you can have a more detailed log.
- Files are created with group and others read access. Don't see a problem in this, since the files will be in your home dir.
Post you coment, please!
##########
Post Update (8/06/2008)
- Changed "DefaultRoot" value (to allow access to the group folders, but not allowing the user to get out of /home)
- Added "ServerIdent on "SOME_TEXT"" to hide ftp server's info
##########
Post Update (22/08/2008)
Stuff that wasn't working now works like a charm!
- Doing an "ls" or "dir" now shows the group that owns the object
- Root folder as /home/samba now working, instead of sending the user to it's true home, unallowing him to browse the group dir's
This HOW-TO will explain how to setup a ProFTPd Server with user authentication against the eBox LDAP User DataBase.
1 - You'll need an Ubuntu 8.04 box with eBox installed and the Users module activated.
2 - Install the proftpd ldap package (sudo apt-get install proftpd-ldap). During the installation, you'll be prompted to choose the way you want proftp to be started (inetd or standalone). Choose Standalone.
3 - Check and write down your eBox LDAP Admin Password (sudo cat /etc/ldap.secret)
4 - Check and write down your server's FQDN (cat /etc/hosts)
5 - Rename your /etc/proftpd/ldap.conf file. Then create a new empty file (sudo touch /etc/proftpd/ldap.conf) and paste the following text in it (replace the words in CAPITAL TEXT with its correct value for your environement)
Quote
# ProFTPd LDAP Module for eBox Platform
<IfModule mod_ldap.c>
LDAPServer localhost
LDAPDNInfo cn=admin,dc=ebox YOUR_EBOX_LDAP_ADMIN_PASSWORD
LDAPDoAuth on "ou=Users,dc=ebox" (&(uid=%v)(objectclass=posixAccount))
LDAPDoUIDLookups on "ou=Users,dc=ebox"
LDAPDoGIDLookups on "ou=Groups,dc=ebox"
</IfModule>
6 - Rename your /etc/proftpd/proftpd.conf file. Then create a new empty file (sudo touch /etc/proftpd/proftpd.conf) and paste the following text in it (replace the CAPITAL TEXT with its correct value for your environement)
Quote
# ProFTPd config file for eBox LDAP authentication
Include /etc/proftpd/modules.conf
UseIPv6 off
ServerName "SOME TEXT"
ServerType standalone
ServerIdent on "SOME TEXT FOR PEOPLE NOT TO SEE THIS IS PROFTP RUNNING"
DeferWelcome off
MultilineRFC2228 on
DefaultServer on
ShowSymlinks on
TimeoutNoTransfer 600
TimeoutStalled 600
TimeoutIdle 1200
#DisplayLogin welcome.msg
#DisplayChdir .message true
ListOptions "-l"
DenyFilter \*.*/
# Use this to jail all users in their homes
DefaultRoot /home/samba
DefaultChDir samba
# Required for eBox LDAP User Auth
RequireValidShell off
Port 21
# In some cases you have to specify passive ports range to by-pass
# firewall limitations. Ephemeral ports can be used for that, but
# feel free to use a more narrow range.
# PassivePorts 49152 65534
# If your host was NATted, this option is useful in order to
# allow passive tranfers to work. You have to use your public
# address and opening the passive ports used on your firewall as well.
# MasqueradeAddress 1.2.3.4
# Only for StandAlone Mode
MaxInstances 30
# Set the user and group that the server normally runs at.
User proftpd
Group nogroup
# Umask 022 is a good standard umask to prevent new files and dirs
# (second parm) from being group and world writable.
Umask 022 022
# Normally, we want files to be overwriteable.
AllowOverwrite on
# Uncomment this if you are using NIS or LDAP via NSS to retrieve passwords:
# PersistentPasswd off
# This is required to use both PAM-based authentication and local passwords
# AuthOrder *mod_auth_pam.c mod_auth_unix.c
# AuthOrder mod_ldap.c
# Be warned: use of this directive impacts CPU average load!
# Uncomment this if you like to see progress and transfer rate with ftpwho
# in downloads. That is not needed for uploads rates.
#
# UseSendFile off
#<IfModule mod_sql.c>
# SQLBackend mysql
#</IfModule>
TransferLog /var/log/proftpd/xferlog
SystemLog /var/log/proftpd/proftpd.log
#<IfModule mod_quotatab.c>
#QuotaEngine off
#</IfModule>
#<IfModule mod_ratio.c>
#Ratios off
#</IfModule>
# Delay engine reduces impact of the so-called Timing Attack described in
# http://security.lss.hr/index.php?page=details&ID=LSS-2004-10-02
# It is on by default.
#<IfModule mod_delay.c>
#DelayEngine on
#</IfModule>
#<IfModule mod_ctrls.c>
#ControlsEngine off
#ControlsMaxClients 2
#ControlsLog /var/log/proftpd/controls.log
#ControlsInterval 5
#ControlsSocket /var/run/proftpd/proftpd.sock
#</IfModule>
#<IfModule mod_ctrls_admin.c>
#AdminControlsEngine off
#</IfModule>
Include /etc/proftpd/ldap.conf
#Include /etc/proftpd/sql.conf
DebugLevel 3
7 - I've noticed that, disableing some unused modules in modules.conf would somehow increase the password verification. So, if you want to try it out, paste the following content in your /etc/proftpd/modules.conf, otherwise, jump to no.8
Quote
#
# This file is used to manage DSO modules and features.
#
# This is the directory where DSO modules reside
ModulePath /usr/lib/proftpd
# Allow only user root to load and unload modules, but allow everyone
# to see which modules have been loaded
ModuleControlsACLs insmod,rmmod allow user root
ModuleControlsACLs lsmod allow user *
#LoadModule mod_ctrls_admin.c
#LoadModule mod_tls.c
#LoadModule mod_sql.c
LoadModule mod_ldap.c
#
# 'SQLBackend mysql' or 'SQLBackend postgres' directives are required
# to have SQL authorization working. You can also comment out the
# unused module here, in alternative.
#
#LoadModule mod_sql_mysql.c
#LoadModule mod_sql_postgres.c
#LoadModule mod_radius.c
LoadModule mod_quotatab.c
LoadModule mod_quotatab_file.c
LoadModule mod_quotatab_ldap.c
#LoadModule mod_quotatab_sql.c
#LoadModule mod_quotatab_radius.c
LoadModule mod_wrap.c
LoadModule mod_rewrite.c
LoadModule mod_load.c
LoadModule mod_ban.c
LoadModule mod_wrap2.c
LoadModule mod_wrap2_file.c
#LoadModule mod_wrap2_sql.c
# keep this module the last one
LoadModule mod_ifsession.c
8 - Restart the ProFTPd Server (sudo /etc/init.d/proftpd restart) and you're on!!!
Some notes:
- For debuging, do "tail -f /var/log/proftpd/proftpd.log" while using the server (be it logging in, logging out, restarting, etc...). You might want to change the "DebugLevel" value in proftpd.conf to it's max (9) so that you can have a more detailed log.
- Files are created with group and others read access. Don't see a problem in this, since the files will be in your home dir.
Post you coment, please!
##########
Post Update (8/06/2008)
- Changed "DefaultRoot" value (to allow access to the group folders, but not allowing the user to get out of /home)
- Added "ServerIdent on "SOME_TEXT"" to hide ftp server's info
##########
Post Update (22/08/2008)
Stuff that wasn't working now works like a charm!
- Doing an "ls" or "dir" now shows the group that owns the object
- Root folder as /home/samba now working, instead of sending the user to it's true home, unallowing him to browse the group dir's