Tag Info

New answers tagged

0

I was finally able to find a solution for this annoying problem (Ubuntu server 14.04) in Atlassian support - step #4. It appears like the ssh-agent was running by default. Open a terminal window and enter the following command to see if the agent is running: ps -e | grep [s]sh-agent If the agent isn't running, start it manually with the following ...


0

You might try Caffeine. You can either use the 'caffeinate' command to prevent your server from sleeping during a given commmand (see http://www.webupd8.org/2015/01/caffeine-app-gets-its-indicator-back.html for syntax) or just set it to prevent idle all the time.


2

The Original poster found an answer: I've found the issue: My "Virtualbox host interface" was set with the same IP of the server (don't know why, don't know how, trust me). Switching it to DHCP gave me back all connectivity!!!


0

I think this is almost the same question as here: How to create a restricted SSH user for port forwarding? The solution there is very comprehensive and should be also applicable for your problem.


2

You need to install sshfs before you go further. sudo apt-get install sshfs Now, you should test that everything is working correctly. You should try mounting your server with. sshfs -o idmap=user $me@server:/ /mnt/review/dori If that works, unmount the directory with fusermount -u /mnt/review/dori The use the second line you posted about from ...


0

Since you said sshfs wasn't installed yet, have you tried installing it? sudo apt-get update sudo apt-get install sshfs


3

You can generate random art of any file with this little C program made by nirejan: #include <stdio.h> #include <stdint.h> #include <stdlib.h> #define XLIM 17 #define YLIM 9 #define ARSZ (XLIM * YLIM) #define DEBUG 0 static uint16_t array[ARSZ]; const char symbols[] = { ' ', '.', 'o', '+', '=', '*', 'B', 'O', 'X', '@', '%', ...


2

The page OpenSSH Keys and The Drunken Bishop gives a good introduction to how the algorthm works. The details of it can be found in The drunken bishop: An analysis of the OpenSSH fingerprint visualization algorithm . The topic is discussed in a more general form in the paper "Hash Visualization: a New Technique to improve Real-World Security", Perrig A. ...


0

Finally solved it! I don't know why but Nautilus 3.10 treats in an odd way the ~/.ssh/config file, or at least this is what I've experienced. This is how my ~/.ssh/config file looks like: Host aws_host HostName [host ip addres] User ubuntu IdentityFile ~/.ssh/your_key.pem DO NOT use your DNS name on your "Host" OR "HostName" variables or you may ...


1

unable to initialize libusb could be because there is no USB controllers present on the Server. You can check it out by executing the following command: lspci | grep USB In your case, there would be no output, indicating the absence of USB controllers. If so, then add one. I have not worked much on VMs, so I can't tell anything about that, but upon ...


0

Instead of repeatedly invoking the ssh command, you could run ssh to repeatedly execute the command on the remote system and then parse and use the output locally. Then you wouldn't have to keep running the ssh connection and putting up with the initial lag. For example: ssh remotehost "while [ "1" ] ; do iwconfig wlan0 ; sleep 1 ; done" Or, you could ...


0

We had a similar problem, but it occurred only when logging from Ubuntu to Solaris. Making sure all these lines are present in /etc/ssh/ssh_config on the Ubuntu host fixed the problem (you should find some of these lines are already present): Host * SendEnv LANG LC_* HashKnownHosts yes GSSAPIAuthentication yes GSSAPIDelegateCredentials no Ciphers ...


0

I don't know anything about mac, but in your ubuntu server you can enable forward X session. Afterwards you can run a graphical application on your server and relay the application window directly to your ssh client. I can describe the procedure for ubuntu serer AND client. Server: /etc/ssh/sshd_config *find line X11Forwarding and set it to yes* NOTE ...


1

The guide assumes that you are using /mirror as your home directory on all cluster nodes (as well as on the master node, which is ub0 for the guide and pythagoras for you). If you are not using /mirror as your home directory (or, more precisely, if your home directory is not shared among all nodes), the following line: mpiu@ub0:~/.ssh$ cat id_rsa.pub ...


0

For use the pip install $ mkdir my_project_folder $ cd my_project_folder $ curl -L -o virtualenv.py https://raw.github.com/pypa/virtualenv/master/virtualenv.py $ python virtualenv.py venv $ source venv/bin/activate In this point, you have you virtualenv ready, if you want install more packages, you can this: $ pip install YOUR_PACKAGE --user So, you ...


1

It is a typo (seriously!!) in the documentation. What it really meant is to copy the rsa public key to the authorized_keys file so that you can ssh using keys (no password). So the command should be: cat id_rsa.pub >> authorized_keys After digging found that the mistake was introduced in revision 15 while changing the key type to use from dsa to ...


0

That's not the way to do it. First of all, to set up passwordless access, you need a target machine. It is not something you set up locally, you must set up passwordless access to somewhere. Anyway, the way to do it is: ssh-keygen -t rsa -P '' That will generate your key. Now, you need to copy it to the target machine: ssh-copy-id -i ~/.ssh/id_rsa.pub ...


1

Files under /usr/share/polkit-1/actions are not meant to be modified. Create a file named /etc/polkit-1/localauthority/50-local.d/allow_all_ssh-users_to_upower.pkla [Allow all ssh-users to upower] Identity=unix-group:ssh-users Action=org.freedesktop.upower.policy ResultInactive=no ResultActive=yes AllowAny=yes


1

The issue is due to the permission of the ~/.ssh/authorized_keys file. Its permission should not be such that others can write into the file. For example, if the permission is set as octal 666 (it is devil indeed !!), as you can all others have the write permission in the file ~/.ssh/authorized_keys, then the file will be ignored by ssh and you will ...


15

Not possible. There is no way since permissions on a symlink are meaningless (a symlink is not a file; it only points to a file). The way to do this with Linux is through ACL though. symlink are explained as... The values of the file mode bits for the created symbolic link are unspecified. All interfaces specified by POSIX.1-2008 shall behave as if the ...


9

You can't. The underlying chmod system call simply doesn't support this in Linux, and for that matter, Linux doesn't care about the link's permissions either. From man chmod: chmod never changes the permissions of symbolic links; the chmod system call cannot change their permissions. This is not a problem since the permissions of symbolic links are ...


2

You can recover the instance data by deploying your SSH key to a new copy of the instance, see e.g. http://stackoverflow.com/questions/3260739/add-keypair-to-existing-ec2-instance


0

The sftp protocol does have a keep alive features but they are not exposed in the filezilla client. Still I don't believe such a setting should be necessary. I'm failing to reproduce your problem. I have had a Filezilla connection open to my Ubuntu ssh server for over 20 hours without any disconnects. So I believe that problem is network related. Do you ...


0

Let's start Create user ubuntu sudo useradd ubuntu Make password sudo passwd ubuntu Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully Create for SFTP only group xxx@xxx:~$ sudo groupadd sftp_users Add to a user "ubuntu" for SFTP only group xxx@xxx:~$ sudo usermod -G sftp_users ubuntu Make dir for sftp ...


0

Without knowing much about your aprtment's Internet Service Provider (ISP), as well as how your apartment's network (AN) is managed, it is hard to give a solution. Dynamic Vs Static IP addresses Three levels of difficulties First: IP address assigned by ISP For most home users ISPs provide a single dynamic IP address. This means the IP address can change ...


1

To investigate, add one or more -v options to the rsync command. Also, try to use plain ssh: ssh -v 192.168.1.21 /bin/true to find out whether it is rsync or the underlying ssh connection that is causing the trouble.


0

Does your login script at the remote end produce garbage on stdout? Check this with ssh -p YY me@XXXXX /bin/true > out.txt If out.txt contains data, identify the offending statements in your .profile or .bashrc and wrap them in if [ ! -t 1 ]; then echo garbage fi


0

You may need to put in the full path to the ssh binary, ie rsync -v -v -e '/usr/bin/ssh -p YY' ./testfile me@XXXXX:/home Though there are other possible causes.


0

I'm really not sure what the problem was; I tried using a different known-working dropbear id_rsa key and that still didn't work. I ended up completely reinstalling a fresh 15.04, and following all the steps again and was able to remote unlock without issue.


1

The SSH key uploaded to the remote server is the public key, which is one of two parts of the actual "SSH Key". It is designed to be 'publicly' disclosed to remote servers, as you need the corresponding private key which is stored on your computer to work with the connection. (An analogous example is PGP encryption which works in a similar way - the PGP ...


0

If SSH on the server side allows key authentication only and the private key on the client (your) side it lost, you need to contact the system administrators, connect a monitor to the machine (depending on your possibilities to access the server). If you get a password: prompt when you run ssh root@[ip], then you should try a password you might have set on ...


1

You are using the wrong commands, Try one of below:- sudo shutdown -h now sudo poweroff sudo halt -p sudo init 0 sudo shutdown -p now For forced poweroff (not shutdown):- sudo poweroff -f


2

When you are connected via ssh there are many commands you can use. You could use grep searchString /var/www/file.css/ to display all occurrences of searchString. Or you could display the file with less /var/www/file.css then press / and type the word you are searching for. Press enter to jump to the first occurrence of the word and n to cycle through the ...


2

This has no matter with scp. This is an issue of file system and the used block size. In simple word and as an example if you use a block size of 512 KB and you have a file 2.5MB size then this file will reserve 5 blocks. Here when filesystem reads the size it will calculate 5*512KB=2.5MB Now if you have the block size of 1MB then the same file of 2.5MB ...


2

On a base install of Ubuntu 14.04.2 LTS, simply drop the message you want in: /etc/motd By default, the MOTD will appear at the end of the other dynamic MOTD content. For example, here's the output from a Vagrant ubuntu/trusty64 (v20150506.0.0) box with a /etc/motd file added: $ vagrant ssh Welcome to Ubuntu 14.04.2 LTS (GNU/Linux 3.13.0-52-generic ...


0

So after a few days of no luck I decided to have the server admin reboot the virtual server. I waited another day before giving things another try and luckily it looks like things are working now. Best of luck to you if you have a similar problem as mine.


1

You should be able to scroll in screen using the key combination Ctrl-A Esc (so first Ctrl-A, release, press Escape). This enables copy mode. After you completed scrolling, you can cancel copy mode with another Esc.


0

I was able to solve the issue by adding the following lines in my "~/.bashrc" eval `gnome-keyring-daemon --start` USERNAME="reynold" export SSH_AUTH_SOCK="$(ls /run/user/$(id -u $USERNAME)/keyring*/ssh|head -1)" export SSH_AGENT_PID="$(pgrep gnome-keyring)"


0

With this commande, you don't choose a directory for you key, so normaly, your key has been created where you are when you make the command input. I personnaly use this and that work well: openssl req -out CSR.csr -new -newkey rsa:2048 -nodes -keyout privateKey.key You don't see it with an ls -l command ? Or try to make a find or locate with the name you ...


0

Search for the file in your system with: sudo find / -name "[server name].csr"


0

This issue because i was using wrong .pem file, then i connected successfully as default users "ubuntu" on the amazon instance.


0

I would consider using NitroShare. NitroShare is a simple file sharing GUI program. It can be installed using sudo add-apt-repository ppa:george-edison55/nitroshare sudo apt-get update sudo apt-get install nitroshare You can launch it from your Desktop's menu (Dash, in the case of Unity), and the program will open in the system tray. It will need to be ...


3

You have removed your private keys. The private key is kept on the computer you log in from, while the public key is stored on the .ssh/authorized_keys file on all the computers you want to log in to. Source If you have no backup, you have to generate a new key pair and copy the public key to the server again.


0

Make sure you install the openssh server in the main PC (where you are trying to ssh into) sudo apt-get install openssh-server then check if the Ubuntu firewall is turne on? sudo ufw status if yes or no still issue the following command sudo ufw allow ssh and sudo ufw reload Now try to ssh using ssh user@ip-address-of-the-machine if ...


1

Your question is not making much sense as the user in question has sudo access. So ... Yes a use can change the password on the ssh keys. and A user with root access can change the password of any other user on the system or lock an account without knowing the password of the target account. I am not sure how you are giving them root access or if ...


1

Unless you provided a custom list of users upon creation, the default 'ubuntu' user should still exist, and the EC2 key was put on that user, as a typical configuration would get. To make it work on other users, you need to take the lines from /home/ubuntu/.ssh/authorized_keys and put them into the file /home/$USER/.ssh/authorized_keys (where $USER is the ...


1

When you want to login from outside over the Internet, you need to be sure that you forward the port 22 in your router to the ssh server. And when you use the AllowUsers parameter is better to login with: ssh username@ip.address.from.isp


0

It was my fail in configuration steps of MaaS. I've resolved that.


1

I think you can't access an IP of your LAN when using its global FQDN. You need to use its private IP adress.


4

You can get the file from the OpenSSH client package: apt-get download openssh-client dpkg-deb --fsys-tarfile openssh-client_*.deb | sudo tar -xC / ./etc/ssh/ssh_config This will extract the ssh_config from that package directly to its destined location /etc/ssh/.



Top 50 recent answers are included