recently I came across something which I can't quite understand and I'd be grateful for any help.
In our company we use GitLab and I've my own key in ~/.ssh/id_rsa. It all worked until I installed openssh-server in order to connect to my workstation via ssh from home. It seems that while typing git pull in the console my GitLab's key is not available (?) and it want me to give a password for a git user. The message is like:
git#gitlab.mycompany.pl password:
I think that after installing openssh-server something must have changed, however I'm not quite sure why. After uninstallation - everything started working again.
Related
I installed docker machine, and then created a new docker-machine on Windows 10.
Now I run ls to see the list of docker machines.
Now I run the following command
docker-machine start hypervdockermachine
Now I am stuck at this
Waiting for SSH to be available...
Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded
I have seen the git hub issue here, but not clear what to do.
Is there a way to solve this problem? I am not good at ssh
UPDATE
I just found a workaround.
You can run the above commands with git bash.
Most important, you must run git bash as admin. Else you will end up scratching your head.
Even the basic
docker-machine ls
will not show up anything without being an admin.
Finally if you are seeing the following error
Unable to query docker version: Get https://192.168.0.105:2376/v1.15/version: x509: certificate signed by unknown authority
Then you have to look at this issue.
docker-machine regenerate-certs yourdockermachinename
If needed user --force option
I got into the same problem after I moved .docker to partition D: and created a symlink to C:\Users\username\.docker, following this SO answer. I removed the old machines and configured new ones, and tried to regenerate the certs as suggested in the OP workaround but the problem was not solved.
After googling, I found this OpenSSH wiki page
and suspected that the cause of the problem was related to permissions.
So I could solve the problem by trying two different things:
Delete .ssh (source)
fix permissions to D:\path\to\.docker, allowing only SYSTEM, Administrators and my user to have full control access (source). These permissions were the same defined for .docker when it was under C:\Users\username\, but moving the folder to another partition made it inherit different permissions. To avoid dealing to much with it, I keep inheritance enabled changed the permissions directly in D: rather than in .docker folder.
I switched from svn to svn+ssh protocoll for a subversion server and configured TortoiseSVN (v1.95) accordingly. This works fine for "update" and "show log" and even repository browser, but when I try to do a commit I get an "authentication failed" error.
Naturally you would think it is a server issue, but it works fine on other computers. Computers where I made a fresh install and also computers that already had the repositories checked out prior to the switch to svn+ssh. It works fine everywhere except on one computer. Same putty version, same Tortoise version, same ssh key. I tried deleting the cached data in Tortoise settings, I made a complete new checkout of the projects, I even deinstalled TortoiseSVN and installed it again...nothing workes. Does anyone have an idea?
EDIT: I found the problem, I use pageant to store my ssh keys. I have 2 and that causes the problem. When I remove 1 it works. But this is merely a workaround. Is there a solution to make it work with 2 keys stored in pageant?
Quick summary:
Can I use cloud9 as an online shell terminal to connect to my own workspace (ec2 instance) WITHOUT having nodejs installed on that instance?
More details
I love the cloud9 online ide and am keen to use it for everything as I just have a chromebook. I just read about the new Ubuntu Snappy version of Ubuntu and wanted to launch an instance of it on amazon's ec2, ssh in, and play with it.
I can ssh in from my chromebook ok, but I'd like to know if there's a way to do this from cloud9? i.e. to use it is an online shell terminal, without first installing nodejs on the ec2 instance (which cloud9 as I understand it needs for the fancier ide features I could make do without for this use case.)
Thanks for the help in advance - first post on stackoverflow :)
Note: I'm a newish linux user. I've successfuly got cloud9's ide to work with a fresh ec2 regular ubuntu instace by connecting via ssh using my chromebook's crosh terminal and installing nodejs first, then switching to connect from cloud9 using the 'own ssh workspace' option. However I'm keen to see if I could have done this totally using cloud9 - ie used cloud9 like an online terminal to connect to the fresh ec2, then installed nodejs to turn on cloud9's fancy ide features. (or perhaps not install nodejs, and just use it as an online terminal e.g. to play with an image of ubuntu snappy quickly)
Unfortunately Cloud9 needs NodeJS on your server to work correctly. When you connect it to your workspace it should pop up with a prompt which after clicking next will automatically install all the dependencies Cloud9 needs to work.
(this is in response to your comment of 12/24)
You don't need Node installed on your Amazon server to make an ordinary ssh connnection. Perhaps you're copying the wrong key over: it's the one ending in .pub in ~/.ssh (e.g. id_rsa.pub).
Amazon has a help page for this process - basically you're adding the content of the public key on C9 to the file ~/.ssh/authorized_keys on your server:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/managing-users.html
Then, you'd ssh from C9 to your server like so:
ssh -i .ssh/<my public key> <myusername on amazon>#<amazon server IP>
We use Vagrant boxes for development. For every project or small snippet we simply start a new box and provision it with Ansible. This is working fantastic; however, we do get into trouble when connecting to a private Bitbucket repository within a bower install run.
The solution we have now is to generate a new key (ssh-keygen), accept all defaults (pressing <return>, <return>, <return>) and then grab the public key (cat ~/.ssh/id_rsa.pub). Copy it, go to Bitbucket, view your account and add this new ssh key. And repeat for every new box you instantiate.
We have to do this because of some closed source packages (hosted on Bitbucket) we install via Bower. We do have another experience, which is much better: composer (php's package manager) and private Github repositories. With that setup, you have to enter your username/password/2fa token via the command line and an OAuth token is generated for you. This works great.
So, is there a way we can mitigate this bower/bitbucket/ssh issue? For obvious reasons I don't want to provision the boxes with a standard private key, but there has to be another solution?
While I'm not sure that my situation is as complex as yours (I'm not using Ansible or Bower), I solved this problem by using the Vagrant ssh forward agent. This blog post gives you the details on how to get it working:
Cloning from GitHub in Vagrant using SSH agent forwarding
So as long as each of the developers has access on their local machines to the bitbucket repos, it should work.
Today I've restarted my computer (running Windows Vista) and when it went up again, it showed a Windows log-in screen. This screen has never appeared before (for almost 4 years now. Windows is original, came with the laptop.
On the screen I had 2 options to enter with: PC-Name (let's call it Johnny) and "Privileged Server". Both of them are asking for password.
Now I don't think that I had ever set a password for my account, nor did it ever ask me to use one, in order to start Windows.
A few tries of my frequently used password, including some "easy" / default passwords such as 1234, admin, 1-9, and so on, were futile.
I am not able to enter my Windows at the moment.
What I suspect happened, is that Cygwin is somehow the cause for it.
Last week I tried to install Hadoop on my Windows, and I followed the Apache tutorial, which instructed to start sshd service on the computer (which is done with Cygwin). during the process of starting that service, there have been some steps that could have messed up the windows account. (setting RSA password / phraseless RSA thingie / whatever)
It also said in the middle, something about problems with the "accounts in the system".
I am sorry I can't be more informative about it, but these commands, among others, were used:
$ ssh-keygen -t dsa -P '' -f ~/.ssh/id_dsa
$ cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys
I can't find the exact tutorial(s) I've been working according to, but this one has some stuff I did: oracle docs
the relevant steps are under the headline "Configuring SSH After Installing Cygwin", steps 1-4
Any help will be appreciated
Look for cyg_server in your registry and get rid of it. You will need it, however, if you're doing sshd with cygwin.