similar to: SSH command when uploading files

Hi everyone. I'm looking for a way to identify my SSH's users according to their public key; I mean I would like to have their name logged in my bash session (in a shared unix account). I put this in my .profile: export HISTTIMEFORMAT="[%Y-%m-%d %H:%M:%S - $SSH_USER] " So now I'm trying to make OpenSSH fill the "SSH_USER" variable. First I have to exclude the

Is it true that when running rsync via ssh (i.e. rsync -e ssh ...) the rsyncd.conf file is not applicable on the remote since rsync is launched via the ssh exec call once connected rather than from rsyncd as in a direct connect. If so, I am trying to find the best way to restrict rsync -e ssh on the remote machine. Prepending the authorized_keys entry with command='rsync ...' 1024...

I'm having trouble with the rsync wrapper's I've found online: rsync_wrapper[8458]: SSH_ORIGINAL_COMMAND environment variable apparently not set rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) I'm not sure if this is a problem of incompatibility between my RHES3 and the wrappers I've found or

Hello all, in order to connect to my SSH servers from untrusted devices like company computers or my smartphone, I set up 2FA with google-authenticator hooked into PAM. However, this is not really 2FA at least for the smartphone, since I use the same device for generating the TANs and it is also at least inconvenient to always require a new TAN for each connection. I do not want to solely rely

Hi Using SSH_ORIGINAL_COMMAND in AuthorizedKeys is so helpful, I'd like to know if it might be possible to access it in the AuthorizedKeysCommand context (via env ?). Is this possible ? can anybody give me advice on going into this ? If possible, I'll use this SSH_ORIGINAL_COMMAND to send client specifics information to the AuthorizedKeysCommand script. Currently, the only alternative

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I just set up a PDF printer via Samba 2.2.5 according to the article given in the German magazine iX of March. Now I have the problem that at the first time I done this a file appeared in the resulting pdfshare (the file created by Word which I test with) but afterwards I cannot get it running again (although I restarted smbd and nmbd). No

I'm trying to mount a share from an NT machine which has an space inside, i.e doing something like that: mount -t smbfs -o username=nardmann,password=xxx "//machine/for internal use" internal_use I always get the message Could not resolve mount point internal How do I mount such shares with whitespace inside the share name? -- Heiko Nardmann (Dipl.-Ing.), h.nardmann@secunet.de,

This is a new branch of an old thread, made necessary because the email system here purges sent messages after a period of time so I can't reply to the last message in the thread. The operative portion of that last message (retrieved from the archives and dated July 3, 2023) follows: /*****/ So I set up a fresh key to use for this test, and gave it similar parameters. I wasn't aware of

Hello, I'm trying to setup Rsync over SSH with openSSH running port 2222 with a remote RSA public key authentification and a restricted shell to avoid the user to browse my server via SSH, only be able to run rsync server. 1) i've built a regular rsync server over TCP/873 Worked fine, check my conf : motd file = /etc/rsyncd.motd log file = /var/log/rsyncd.log pid

I have problems mounting a share from our NT server. Connecting to the share via smbclient '//snsrv051/public' -W ... -U ... and typing my password works nicely but smbmount '//snsrv051/public' /mnt/snsrv051/public -W secunet-si -U nardmann just gives me the following error message: Added interface ip=10.151.4.59 bcast=10.151.7.255 nmask=255.255.252.0 Server time is Fri Jan 29

> I have problems mounting a share from our NT server. > Connecting to the share via > smbclient '//snsrv051/public' -W ... -U ... > and typing my password works nicely but > smbmount '//snsrv051/public' /mnt/snsrv051/public -W secunet-si -U > nardmann > just gives me the following error message: > > Added interface ip=10.151.4.59 bcast=10.151.7.255

I am running Samba 2.0.6 successfully on a Linux machine. Currently I try to add the two printers in our net to Samba. Now I wonder which printer names in the printcap are shown when I do a 'smbclient -L <linux machine>'. The printcap contains something like remote22|HPL4kSC|HP Laserjet floor 4 ... remote21|HPLaser4|HP Laserjet floor 3 Now the first printer shows up as

Hi, On 18.10.24 13:50, Chris Green wrote: > chris$ ps -fe | grep ssh-agent > chris 2463 1530 0 12:33 ? 00:00:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh > > but:- > > chris$ env | grep SSH > SSH_AUTH_SOCK=/run/user/1000/keyring/ssh > > So SSH_AUTH_SOCK doesn't appear to be the socket that ssh-agent thinks > it

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am looking for a good and new book for Samba which includes descriptions for the new features (maybe using Samba and Win2K), too. Any proposals? - -- Heiko Nardmann (Dipl.-Ing.), h.nardmann@secunet.de, Software Development secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de), Weidenauer Str. 223-225, D-57076 Siegen Tel. : +49

Hello everyone, I know this is not correct place to ask this question but please help if you know As mentioned some tutorial, i install git version 1.7.3.4 in home directory (/var/chroot/home/content/xx/xxxxxxx/git). then I initialize git repository by git init --bare in my samplerepo.git then i add code in .bashrc file as follow export GIT_BIN=${HOME}/git export

Hi, I am using rsync to keep two directores on two servers in sync. Machine A, the "client" is the one where the rsync process is invoked, which then logs into Machine B, the "server" as root with ssh and a key. The key is restricted in /root/.ssh/authorized_keys to a script that checks wither $SSH_ORIGINAL_COMMAND matches the rsync --server command that I expect, such as, for

>From the testing that I've done so far, using the command= restriction essentially ignores any and all attempts by the client to send different remote filenames, directory commands, etc... using scp -i some_key localfile remotehost:../../../../../../../../../../tmp/file places a copy of the file named "localfile" in the directory specified in the command= line of the

What is the best way to give a remote user the ability to use rsync via ssh without also giving them shell access? I want the rsync user to authenticate via ssh. I want to protect their rsync session with ssh. However, I do not want to give them access to a shell on the Linux server where rsyncd is running. Any recommendations would be appreciated. chongo (Landon Curt Noll) /\oo/\

samba@samba.anu.edu.au wrote: > > SAMBA Digest 1853 > > For information on unsubscribing see http://samba.anu.edu.au/listproc > Topics covered in this issue include: > > 1) Re: long winded printing LARGE files soloution > by Heiko Nardmann <h.nardmann@secunet.de> > 2) Samba replacing NFS > by Jonathan Peterson

Hello List, I'am using the ForceCommand in my sshd configuration to log all the user actions on my device. ForceCommand /usr/bin/log-session.sh The Log Session Script itself is working fine for logging. But now I want also use SCP to copy files and this won't work together with the ForceCommand above. The copied file is created but its zero byte on the target. scp file.tar.gz