On Tue, May 17, 2016 16:34, Dustin Kempter wrote:
ere.
>>
> Here is the command and output
>
>
> [test1@pgpool1 ~]$ ssh -v -i /home/test1/my-key.txt
> upload@144.167.188.62
. . .
> debug1: Authentications that can continue:
> publickey,gssapi-keyex,gssapi-with-mic
> debug1: Next authentication
On Wed, May 18, 2016 at 03:25:11AM +0100, Always Learning wrote:
> On Tue, 2016-05-17 at 20:12 -0400, Jonathan Billings wrote:
> > If you’re going to change the port, change it to something <1024. You
> > don’t want to have sshd running on a port that a non-root user can bind to.
>
> But if, as
On 2016-05-17, Always Learning wrote:
>
> (1) I would change the port from 22 to something more difficult to
> guess, perhaps 49026 (for example) and then block port 22 in the
> firewall.
>
> (2) Allow to port 49026 (for example) traffic from your IP and block
> traffic from
On Tue, 2016-05-17 at 20:12 -0400, Jonathan Billings wrote:
> On May 17, 2016, at 7:56 PM, Always Learning wrote:
> > (1) I would change the port from 22 to something more difficult to
> > guess, perhaps 49026 (for example) and then block port 22 in the
> > firewall.
>
>
On May 17, 2016, at 7:56 PM, Always Learning wrote:
> (1) I would change the port from 22 to something more difficult to
> guess, perhaps 49026 (for example) and then block port 22 in the
> firewall.
If you’re going to change the port, change it to something <1024. You
On Tue, 2016-05-17 at 14:34 -0600, Dustin Kempter wrote:
> Connecting to 104.197.158.61 [104.197.158.61] port 22.
(1) I would change the port from 22 to something more difficult to
guess, perhaps 49026 (for example) and then block port 22 in the
firewall.
(2) Allow to port 49026 (for
On 5/17/16 2:43 PM, Frank Cox wrote:
On Tue, 17 May 2016 14:34:03 -0600
Dustin Kempter wrote:
Enter passphrase for key '/home/test1/my-key.txt':
Since your private key is encrypted, have you entered the passphrase for the
private key when asked at this point in the login?
Yes I did
On Tue, 17 May 2016 14:34:03 -0600
Dustin Kempter wrote:
> Enter passphrase for key '/home/test1/my-key.txt':
Since your private key is encrypted, have you entered the passphrase for the
private key when asked at this point in the login?
--
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~
On 5/17/16 2:12 PM, Frank Cox wrote:
On Tue, 17 May 2016 13:59:18 -0600
Dustin Kempter wrote:
Is there something I missed?
ssh -v serveryouwanttoconnectto
That will tell you what the problem is.
If you don't understand the output, post it here.
Here is the command and output
On Tue, 17 May 2016 13:59:18 -0600
Dustin Kempter wrote:
> Is there something I missed?
ssh -v serveryouwanttoconnectto
That will tell you what the problem is.
If you don't understand the output, post it here.
--
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
On 5/17/16 10:47 AM, Tony Mountifield wrote:
In article <573b48c8.1070...@consistentstate.com>,
Dustin Kempter wrote:
Hi all,
I am using the google cloud compute engine and we have a client
that does not want to share their ssh keys. So I have been
In article <573b48c8.1070...@consistentstate.com>,
Dustin Kempter wrote:
> Hi all,
> I am using the google cloud compute engine and we have a client
> that does not want to share their ssh keys. So I have been attempting to
> set up a PEM file for ssh access.
Hi all,
I am using the google cloud compute engine and we have a client
that does not want to share their ssh keys. So I have been attempting to
set up a PEM file for ssh access. Both the local server I used for
testing and the cloud vm are centos 6.
I created a user on the cloud box,
13 matches
Mail list logo