Displaying 4 results from an estimated 4 matches for "whateverkey".
Did you mean:
whatevere
2015 Jul 29
2
Updating from 6.6 - 6.9 SSH
My apologies Darren,
The error i get is a "PUBLICKEY" error as noted previously.
Nicks-MacBook-Pro:Downloads$ ssh -i WHATEVERKEY.pem ubuntu at IPADDRESS
Permission denied (publickey).
Nicks-MacBook-Pro:Downloads$
I followed the directions as noted in the previous email to a T. Just
copied and pasted---and used v6.9 ssh (which is the latest). What other
info do you need?
Thanks
Nick
On Tue, Jul 28, 2015 at 7:19 P...
2015 Jul 29
3
Updating from 6.6 - 6.9 SSH
...Nick Stanoszek wrote:
>> Please see below :). Just a note---this is the EXACT command
>> that I use to log into the server BEFORE i try to update SSH. I
>> continue to use this same command for other servers.
>>
>> Nicks-MacBook-Pro:Downloads$ ssh -i WHATEVERKEY.pem
>> ubuntu at 54.200.249.185 <mailto:ubuntu at 54.200.249.185> -v -v -v -v
>>
>> OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
>>
>> debug1: Reading configuration data /etc/ssh_config
>>
>> debug1: /etc/ssh_config line 20: Applying opti...
2015 Jul 29
2
Updating from 6.6 - 6.9 SSH
And Server?
- Ben
Nick Stanoszek wrote:
> Please see below :). Just a note---this is the EXACT command that I
> use to log into the server BEFORE i try to update SSH. I continue to
> use this same command for other servers.
>
> Nicks-MacBook-Pro:Downloads$ ssh -i WHATEVERKEY.pem
> ubuntu at 54.200.249.185 <mailto:ubuntu at 54.200.249.185> -v -v -v -v
>
> OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
>
> debug1: Reading configuration data /etc/ssh_config
>
> debug1: /etc/ssh_config line 20: Applying options for *
>
> debug2: ssh_connect: ne...
2015 Jul 28
2
Updating from 6.6 - 6.9 SSH
Hi again,
I ran the commands exactly. I see that some keys are not overwritten and
skipped---but some are still created.
I just tried again...and still get an error.
Thoughts to prevent it from overwriting my keys?
On Tue, Jul 28, 2015 at 12:53 AM, Darren Tucker <dtucker at zip.com.au> wrote:
> On Tue, Jul 28, 2015 at 1:19 PM, Nick Stanoszek <nstanoszek at gmail.com>
>