Skip to content

Commit 7f8552f

Browse files
authored
Merge pull request #267942 from mikewill4/patch-62
Update host key rotation time estimate
2 parents 07d269a + fd1cf67 commit 7f8552f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/storage/blobs/secure-file-transfer-protocol-host-keys.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -111,7 +111,7 @@ Are you sure you want to continue connecting (yes/no/[fingerprint])?
111111
Verification would involve comparing the fingerprint from the client output with the one stored in the table below. If they match, then type `yes` to continue and the client will then automatically store the new key in the `known_hosts` for the future.
112112

113113
### How long does the rotation take?
114-
Rotations are gradual and may take multiple days. Either the old or new host key may be presented by the Azure service during this time.
114+
Rotations are gradual and may take multiple weeks. Either the old or new host key may be presented by the Azure service during this time.
115115

116116
### Why do the host keys expire?
117117
Periodically rotating secrets is a standard security practice and can help reduce attack vectors.

0 commit comments

Comments
 (0)