I would like to allow to first remote login via ssh using password for a new users. After that authentication should be restricted to public key. How to deal with that? I mean how to restrict second and next login to ssh-keys, but allow first with password.
Krzysztof Bzowski's questions
HP LaserJet 1005 is connected to Windows 7 (x86) workstation and we cannot change that (it needs to be Windows 7 and needs to be connected there). Windows XP 32 bits drivers are used because HP does not support Windows 7 x86_64 with this printer. Printer is shared across a local network (SMB), but only users with 32 bits systems can use that printer (driver issue).
The idea was to delegate one Linux workstation to work as a proxy between all 64 bits Windows systems and that one particular Windows workstation where printer is connected. Is it possible at all? How to achieve that?
My hosting provider had enabled Trusted Path Execution (Grsec), so all my subversion hooks (for example post-commit) stopped working. Any attempt to commit something ends with warning:
post-commit hook failed (exit code 255) with no output.
I checked, that scripts can be run manually using following syntax:
bash post-commit [PATH] [REV]
but not by:
./post-commit [PATH] [REV]
I think Subversion uses the last one, which cause the problem. So is it possible to change the way which subversion handle hooks?