search for: relitivli

I am considering allowing (relitivly) untrusted local users onto my fileserver, so they can use SFTP to access their home directories. I have a custom shell, (a taint-mode enabled perl script) that allows users to change their password, which I have modifed to only allow a '-c' command for the sftp-server. I have also disabled TCP port forwarding. However, some reading of the OpenSSH

As I have mentioned earlier on this list, I want to allow (relitivly) untrusted local users to SFTP to my server, as a secure method of remote file access. What I would like to do is to keep users within their home directory. I don't mind that it follows symlinks (if fact its probably a requirement), but some basic restriction on what users can see/access would be handy. The check I

I have been searching for information about implementing Logon Hours with a Samba 2.2.5 PDC (or for that matter any version of SAMBA) but haven't yet noticed any postings or correspondence. I have set up a a Samba PDC and have mapped shares, authenticated users, blah blah blah, .... everything seems to work fine. I checked with 'rpcclient' to see what sort of information is

Hi, Is there any way to use an external program to validate users' passwords? It would be something like an exec command that would return the authentication result. What I'm willing is to be able to authenticate a samba user against a radius server. Why? Because I get to use tokens (one life time password) against different realms. Has anybody an idea? Thank you -------------- next

Skipped content of type multipart/alternative

I've poured through the FAQ and HowTo for setting up my Linux 7.0 system to act as a PDC for my Windows 2000 SP1 clients; however, I continue to get the "Cannot join domain, the credentials supplied conflict with an existing set.." error. Yep, I followed the FAQ for this error, followed it and I still get this error. I'm logging onto the Win2K system as administrator and when I

being from a telecoms background, the thought of a single asterisk box solution (even in a low production environment of say <10 phones) worries me slightly! starting from say a base of asterisk@home, you would have several MySQL databases, in addition to numerous config files. I have looked at high availiblity solutions, and from a hardware monitoring point of view, its relitivly straight