RHSA-2024:3166

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security. Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation: https://access.redhat.com/node/7053909 More details about supported alternatives available at: https://access.redhat.com/articles/5284081