Skip to content

Commit 1c7a2cf

Browse files
authored
Remove text that specifies OS
1 parent 101411a commit 1c7a2cf

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed
Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: include file
33
description: include file
4-
services: virtual-machines-linux
4+
services: virtual-machines
55
author: cynthn
66
ms.service: virtual-machines
77
ms.topic: include
@@ -11,14 +11,14 @@
1111
---
1212
## Overview of SSH and keys
1313

14-
[SSH](https://www.ssh.com/ssh/) is an encrypted connection protocol that provides secure sign-ins over unsecured connections. SSH is the default connection protocol for Linux VMs hosted in Azure. Although SSH provides an encrypted connection, using passwords with SSH connections still leaves the VM vulnerable to brute-force attacks. We recommend connecting to a VM over SSH using a public-private key pair, also known as *SSH keys*.
14+
[SSH](https://www.ssh.com/ssh/) is an encrypted connection protocol that provides secure sign-ins over unsecured connections. Although SSH provides an encrypted connection, using passwords with SSH connections still leaves the VM vulnerable to brute-force attacks. We recommend connecting to a VM over SSH using a public-private key pair, also known as *SSH keys*.
1515

16-
- The *public key* is placed on your Linux VM.
16+
- The *public key* is placed on your VM.
1717

1818
- The *private key* remains on your local system. Protect this private key. Do not share it.
1919

20-
When you use an SSH client to connect to your Linux VM (which has the public key), the remote VM tests the client to make sure it has the correct private key. If the client has the private key, it's granted access to the VM.
20+
When you use an SSH client to connect to your VM (which has the public key), the remote VM tests the client to make sure it has the correct private key. If the client has the private key, it's granted access to the VM.
2121

2222
Depending on your organization's security policies, you can reuse a single public-private key pair to access multiple Azure VMs and services. You do not need a separate pair of keys for each VM or service you wish to access.
2323

24-
Your public key can be shared with anyone, but only you (or your local security infrastructure) should have access to your private key.
24+
Your public key can be shared with anyone, but only you (or your local security infrastructure) should have access to your private key.

0 commit comments

Comments
 (0)