New answers tagged

1

Another way is to comment out these lines in /etc/pam.d/login: #session optional pam_motd.so motd=/run/motd.dynamic #session optional pam_motd.so noupdate


1

There is configuration option in sshd_config, called PrintMotd. Setting it to no does the job.


0

I have just found a faster (quick and dirty) way (Attention: it is not secure!): 1) Install the terminal app and open it 2) switch to root sudo su (enter you screen lock password) 2) Enter the following commands: echo "PasswordAuthentication yes" >> /etc/ssh/sshd_config echo "AllowUsers phablet" >> /etc/ssh/sshd_config /usr/sbin/sshd Now ...


1

The script files in /etc/update-motd.d generate the file /var/run/motd.dynamic which you've identified as containing your MOTD. A simplistic way to stop generating this file would be to make all of the scripts non-executable with: chmod -x /etc/update-motd.d/* Note: Information taken from this answer by heemayl.


0

Because the while loop is in a pipeline, it is being executed in a subshell. If you log out and log in, you will see that a local session will be affected too (not just SSH). This can be fixed by moving the list into a variable and switching to a for loop: # Find functions in this script based on a grep search, and export them. functions="$( grep ^'[[:alnum:...


2

Both files should be placed in the directory /home/{user}/.ssh, if you find this directory doesn't exist, you can make it with the correct permission with the command: mkdir -m700 ~/.ssh Move both the public and private keyfiles into that directory (using the directory /home/keys that you wrote in your question): mv /home/keys/id_rsa* ~/.ssh Make sure ...


0

The usual location for your RSA private key is ~/.ssh/id_rsa. Neither the key nor the containing directory should be group or world readable.


0

You should know: to access remote systems rsync uses SSH protocol by default SSH protocol implementations (by default) verify the identify of both: the server and the client to verify server, client uses Trust On First Use trust model and by default it remembers the servers it connected to in -/.ssh/known_hosts file if you replace the server with another ...


0

I could solve this problem using -T option "Disable pseudo-terminal allocation." and by using the scriptfiles without the #!/bin/bash line so just started with echo "check" reboot


2

ssh -Q cipher reports the ciphers supported by the ssh client, not the server. One way to verify that you have successfully removed the cipher foo from the server configuration is to explicitly use it for your connection: ssh -oCiphers=foo localhost relevant excerpt from ssh.c option processing: case 'Q': cp = NULL; ...


3

While ssh is not the same as Samba, and therefore it was likely that you failed, you can do a cifs-mount for a Samba-shared directory: create a folder in your (Johnny's) home dir e.g. mkdir univerity_space then connect via sudo /bin/mount -t cifs -o user=UNIVERSITY_USERNAME,uid=1000,gid=1000 //foo.bar.com/user /home/johnny_johnson/university_space check ...


2

If the server provides you with Samba shares, that doesn't mean that it is allowing console SSH connections, or provides any other service and/or functionality. Samba server has its own user database (it might be synchronized with system). Samba network protocol doesn't carry the Linux file permissions. You should ask your server administrators about ...


0

After some investigation, I figured out that the network device was simply deactivated. Weird that it deactivated upon reboot but after I could ssh I rebooted to see if the problem would occur again and it didn't.


1

Add entries to ~/.ssh/config (for a specific user) or /etc/ssh/ssh_config (for all users) as Host prodService Hostname prodService.xyz.pdr.abc.com ... other options for this host...


1

A similar question was asked that might answer your question: Consider using a ForceCommand directive in sshd_config. For example, I use these to force groups of users to a set of servers: Match Group group1 ForceCommand ssh -t group1.fqdn Match Group="*,!local,!group2,!root" ForceCommand ssh -t group3.fqdn You could use: Match ...


0

Just an addition: while ifconfig provides you with the current ip address it needs root/sudo ip addr would work without this need and returns an address too


1

According to Google's site, here are the steps to install gcloud on Debian based systems You may need to install curl sudo apt-get install curl Create an environment variable for the correct distribution export CLOUD_SDK_REPO="cloud-sdk-$(lsb_release -c -s)" Add the Cloud SDK distribution URI as a package source echo "deb http://packages.cloud....


0

The tone of your question is not very pleasant. If you want us to help, you at least need to tell us exactly what you did. It is necessary for you to tell us 3 things. What command did you use to launch your ssh session. Did you run $ ssh -Y whatever.com or $ ssh -X whatever.com If you had neither -X nor -Y, X11 forwarding won't work Have you ...


3

Most probably you are using key stored in some non-standard location and added to your gnome-keyring. Using ssh -A santhosh@localhost will forward the connection to your agent and you will be able to use the same identity withing ssh session. Other way would be to specify the identity file in your ~/.ssh/config: Host github.com IdentityFile path/to/key


2

In this case, it seem that spawn refers to the spawn extension to the hosts.allow syntax, as described in the RUNNING OTHER COMMANDS section of the hosts_options (5) man page (man hosts_options): RUNNING OTHER COMMANDS aclexec shell_command Execute, in a child process, the specified shell command, after performing the %<...


2

spawn is expect specific command i.e. you need to interpret spawn using expect. Most of the time you would use a expect script and use spawn inside it to start a new process. For example: #!/usr/bin/expect -f spawn ssh host expect .... From terminal directly: % expect -c 'spawn whoami' spawn whoami By default spawn echoes the command hence the output ...


0

Easy-peasy: Hike up to the remote observatory and turn on the Wake-On-Lan in the BIOS or on the NIC card if needed. write down the MAC address. SSH into any other machine and type: sudo apt-get install wakeonlan wol MA:CA:DD:RE:SS where MA:CA:DD:RE:SS is the MAC address of your server. Done! ;-)


3

Most likely to identify who created the key. It is just a comment. But as said at 1: probably so you know you created it. Useful when more than 1 administrator is administrating the system. Yes, you can add anything in place of your e-mail. And since it is the last part of it you do not have to use anything special for spaces etc. Extra: ssh-keygen -c to ...


0

With 0 intersection also Client is able to remotely establish ssh connection, how is it possible ? No, it is not possible. Post the verbose log of the connection (ssh -vvv host) to see that there is some intersection.


0

you can use below command for install ssh2 sudo pecl channel-update pecl.php.net sudo apt-get install libssh2-1-dev sudo pecl install -a ssh2-0.12 echo 'extension=ssh2.so' | sudo tee /etc/php5/mods-available/ssh2.ini > /dev/null sudo php5enmod ssh2


-1

Finally i solved my problem by fixing security issues on Ubuntu 14.04 LTS. By running these commands: lsb_release -a Download old version of nss libraries wget http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3_3.19.2-1ubuntu1_i386.deb wget http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d_3.19.2-1ubuntu1_i386.deb Install downloaded ...


0

I found my mistake. I was trying to make a copy for the file from inside the file not from outside and this was t


2

When you try to copy /src it shows that the file does not exist because if a path starts with a slash, it is treated as absolute path. That means it is treated as relative to the file system root /. Simply omit the / at the beginning of the local path and don't forget to specify a path on the target computer, like this (running from inside your home ...


4

Making many changes all at once Take the original file and save it as sshd_config.orig. Edit sshd_config to your heart's content. Run diff sshd_config.orig sshd_config >config.patch Keep the config.patch file somewhere safe. Now, anytime that you have a new and unedited version of sshd_config and you want to apply the same edits, run: patch ...


1

OpenSSH ssh have a switch -b, which allows you to specify to which local IP address it should bind when connecting to the remote host. There is also respective BindAddress option which you can store in your ssh_config. Let's say your wireless IP address is 192.168.0.5 and remote host is remote, then you can ssh -b 192.168.0.5 remote or store a record in ~...


0

A mounted file system should stay mounted. If you want to keep your mounted fs after a reboot/power failure, etc, you can make an entry for the fs in /etc/fstab. https://help.ubuntu.com/community/Fstab regards


0

You have used command incorrectly. ssh username@ip The error also may occur if you have enabled password less authentication and disabled password authentication in ssh_config file. As mentioned in the comments it may be because of error in config file.


2

Spaces in directories or filenames are the natural enemy of a Linux system but can of course be escaped with due diligence. There are 3 possibilities that you could try: scp [remote username]@192.168.1.X:"'/media/remote_username/photos 4/file.jpg'" . scp [remote username]@192.168.1.X:"/media/remote_username/photos\ 4/file.jpg" . scp [remote username]@192....


0

Have you installed ssh server and client on your Ubuntu? Try: sudo apt-get install sshd Have you opened proper ports? ufw allow 22/udp Or maybe the problem lies on your interface having it NAT from your network. Double check if from your Ubuntu, can you ping any devices from your network (router, computers). Have your ping result here and let's ...


1

It turns out that the problem was with A's ssh_config file. It had PasswordAuthentication set to "no", with all other authentication methods commented out (which I believe means they are set to default?)


0

How are you connecting to your ubuntu machine using putty ? Can you please share the steps or command if its via cmd. Anyways putty uses .ppk key. So make sure you have your pem converted to ppk and also no security/network blockage on machine access. To login using cmd : C:\Users\dmittal\Downloads\Keys>putty.exe user@hostip -i key eg: C:\Users\...


0

This may be more than you want/need, but the landscape-common package automatically adds system information, including IP addresses to the MOTD. Welcome to Ubuntu 16.04 LTS (GNU/Linux 4.4.0-28-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support: https://ubuntu.com/advantage ...


3

ssh does not support address:port syntax; instead the port is specified using the -p option. So what you want is ssh -p 2080 192.168.40.250 see also man ssh.


1

This link may help answer your question in regards to the error message of "Too many authentication failures" superuser.com: Too many authentication failures for username Per the manpage for ssh-keygen, the ssh-keygen -R command: Removes all keys belonging to hostname from a known_hosts file So keys are removed are those from ssh-servers that are ...


0

I my case, the client is ubuntu 14.04lts, the server was win 2012 server running cygwin. I was using 'ssh administrator@x.x.x.x', when the 2012 server directory in cygwin was /home/Administrator. So it was case sensitive, when I tried 'ssh Administrator@x.x.x.x' (note the capital A on Administrator) then it worked fine. An error message like 'user not ...


-1

sudo ufw default deny incoming will block all incoming ports. If your profile is different, then change default to your profile name.


0

for SSH : put your text in a file, eg: ***************************************************************** * Private SSH service. * * Please leave immediately. * ***************************************************************** In the sshd_conf file, find the line: #Banner /etc/...


1

This problem may occur when: 1. Port 22 is closed. 2. Ssh is not installed on the machine. Check whether ssh service is running or not on the machine to which you want to connect.


0

Create the RSA Key Pair The first step is to create the key pair on the client machine (In your case it is your computer outside virtual box): ssh-keygen -t rsa Store the Keys and Passphrase Once you have entered the ssh-keygen command, you will get a few more questions: Enter file in which to save the key (/home/demo/.ssh/id_rsa): You can press enter ...


14

After connecting to a remote machine through ssh, press Return and then ~ Shift+C to get this prompt. See the "Escape characters" section of the ssh manpage for some more special keys.


0

I don't mean to insult you by telling you the obvious. I seem to do that a lot. I suspect you are not using the correct IP to talk to the SSH server from your computer. Remember, inside the router area, the server will have an IP number that is meaningful only inside the router's subnet, usually 192.168.xxx.xxx. That works fine for everybody within the ...


1

I had the same problem. I ran strace with meld and gedit and it indicated that for some reason there was problem finding libGLX_indirect.so.0 library. I attempted a fix by placing relevant symbolic link inside /usr/lib/x86_64-linux-gnu folder: sudo ln -s /usr/lib/nvidia-361/libGLX_indirect.so.0 and it works now. Would like to know what is the preferred ...


0

I seem to have resolved the problem by running pax11publish -r Now, xprop -root | grep PULSE shows: PULSE_SERVER(STRING) = "{9899a0f46bdae6bbc8e6e8b200000005}unix:/home/user1/.pulse/9899a0f46bdae6bbc8e6e8b200000005-runtime/native" Apparently pulseaudio --check should normally go to the command prompt. Apparently this indicates it is running.


-1

Ordinarally Raja would have the reason. If it is on amazon cloud, you could set up another server, and attach the other server storage and change the config by hand. You have to know the provider features. Perhaps there are ways. Many "dedicated servers" aren't trully that. Ask for your host support. Or hire a whitehat pentester to try to do so if it is ...


2

According to this serverfault.com answer Allow SCP but not actual login using SSH, one currently supported way is by using rssh, which is available from the universe repository: sudo apt-add-repository universe sudo apt-get install rssh To allow SCP, you must uncomment the corresponding line in the /etc/rssh.conf file (plus any other protocols you wish ...



Top 50 recent answers are included