help with mod_auth_ntsec apache module

Hello, I've done a fair bit of searching using google to find smoe examples of how to use this module but I haven't come up with anything that has helped me get things fully working yet. As per the included mod_auth_ntsec-1.7-1.README I have added the following lines where appropriate into my htt

scponly or some equivalent shell?

Hello. I posted a message at the scponly mailing list requesting help getting scponly to work under cygwin. After a bit of mucking around I was unable to get it to work. Scponly is shell that only allows scp commands (ie: no general shell access to execute commands). scponly is found here http://

Re: scponly or some equivalent shell?

anyone got any other ideas as to how to achieve the same results as scponly provides? Thanks again. PJ --- Igor Pechtchanski <[EMAIL PROTECTED]> wrote: > On Fri, 19 Mar 2004, Paul Jansen wrote: > > > Hello. > > > > I posted a message at the scponly mailing list

scponly shell - compilation issues - more info

Thanks Igor for the replies later last week. I've tracked down a post I made to the scponly mailing list a little while back. It explains in - I hope enough - detail where I was running into problems getting this to compile. The post can be found here: https://lists.ccs.neu.edu/pipermail/scponly/20

sshd problems - won't accept my password

Hi. I've set up cygwin's sshd on a couple of boxes and it's working fine. All boxes are using local password database to authenticate users. Today I installed sshd on a 2000 server that is a member server in an active directory. I followed all the same steps as I did when I installed and succes

sshd - illegal user, /bin/bash not executable?

I've installed the latest sshd under 2000 server SP2 and I can't get any userId's to authenticate. sshd is installed as a service When I run the service with '-d' instead of '-D' to enable debugging to the logfile I see the following error. "user fztm49 is not allowed because shell /bin/bash is

sshd problem - fixed

Just a quick note to say I managed to fix my sshd problem. The original message is below. The problem was actually an NTFS file permission issue. The volume had 'authenticated users' as a file permission. When I added 'everyone' with 'read/execute' access to the cygwin directory sshd was able