SSH security improvements: Difference between revisions

SSH security improvements (view source)

21 bytes removed , 5 years ago

remove double negative

Bureaucrats, cc_docs_admin, cc_staff

2,879

edits

@@ Line 7: / Line 7: @@
 <!--T:2-->
 With constant increase in computing power over time, some encryption algorithms
-and protocols which were reasonably secure ten or fifteen years ago can no longer be used without an unacceptable risk of the connection being compromised by a third party. For this reason, Compute Canada is modifying its policies and practices regarding [[SSH]], the tool used to verify the identity of clusters and users to one another. Some users may have to update their SSH client software, some may have to generate a new public/private key-pair, and everyone will have to update the local copy of the "host key" which is used to identify each Compute Canada cluster.
+and protocols which were reasonably secure ten or fifteen years ago now pose an unacceptable risk of the connection being compromised by a third party. For this reason, Compute Canada is modifying its policies and practices regarding [[SSH]], the tool used to verify the identity of clusters and users to one another. Some users may have to update their SSH client software, some may have to generate a new public/private key-pair, and everyone will have to update the local copy of the "host key" which is used to identify each Compute Canada cluster.
 == What is changing? == <!--T:3-->