Update SSH Target Requirements: Remove Deprecated Mono Mentions (#2611)

Author: kevjt

src/pages/docs/infrastructure/deployment-targets/linux/ssh-requirements.md

@@ -27,10 +27,9 @@ See the Bash Reference Manual, section [6.2 Bash Startup Files](http://www.gnu.o
 
 ## .NET {#dotnet}
 
-[Calamari](/docs/octopus-rest-api/calamari) is the command-line tool that is invoked to perform the deployment steps on the deployment target. Calamari runs on .NET.  SSH targets can be configured to use either:
+[Calamari](/docs/octopus-rest-api/calamari) is the command-line tool that is invoked to perform the deployment steps on the deployment target. It runs on .NET and is built as a [.NET Core self-contained distributable](https://docs.microsoft.com/en-us/dotnet/core/deploying/#self-contained-deployments-scd).
 
-- [Self-contained Calamari](#self-contained-calamari) built against .NET Core (recommended).
-- [Calamari on Mono](#mono-calamari) built against the full .NET framework.
+Since it is self-contained, .NET Core does not need to be installed on the target server. However, there are still some [pre-requisite dependencies](https://learn.microsoft.com/en-us/dotnet/core/install/linux-scripted-manual#dependencies) required for .NET Core itself that must be installed.
 
 ## Python
 Octopus can execute Python scripts on SSH targets provided the following criteria are met:
@@ -39,81 +38,6 @@ Octopus can execute Python scripts on SSH targets provided the following criteri
 - Python3 is on the path for the SSH user executing the deployment
 - pip is installed or the pycryptodome python package is installed
 
-## ScriptCS and F#
-
-Support for ScriptCS and F# scripts are only available with **Mono 4** and above. While they require mono installed, they will still execute with the self-contained Calamari.
-
-ScriptCS has not been ported for .NET Core ([GitHub issue](https://github.com/scriptcs/scriptcs/issues/1183)).
-
-Similarly, the F# interpreter has also not yet been ported for .NET Core ([GitHub issue](https://github.com/Microsoft/visualfsharp/issues/2407)).
-
-:::div{.warning}
- 
-ScriptCS does not work on Mono **5.16** and higher. We recommend using Mono **5.14.x**.
-:::
-
-## Self-contained Calamari {#self-contained-calamari}
-
-When using the self-contained option, neither .NET Core nor Mono need to be installed on the target server (there are still some [pre-requisite dependencies](#self-contained-net-core-dependencies)).
-
-Self-contained Calamari is built as a [.NET Core self-contained distributable](https://docs.microsoft.com/en-us/dotnet/core/deploying/#self-contained-deployments-scd).
-
-### Self-Contained .NET Core dependencies {#self-contained-net-core-dependencies}
-
-[.NET Core has some dependencies](https://learn.microsoft.com/en-us/dotnet/core/install/linux-scripted-manual#dependencies) which must be installed on the target server.
-
-## Calamari on Mono {#mono-calamari}
-
-:::div{.warning}
- 
-Mono is [being deprecated](https://octopus.com/blog/deprecating-mono) and may no longer be available in future versions of Octopus Server. We recommend upgrading your SSH Target to make use of [Self-contained Calamari](#self-contained-calamari)
-
-:::
-
-[Calamari](/docs/octopus-rest-api/calamari/) can execute on the [Mono framework](http://www.mono-project.com).
-
-Version **5.14.0** or greater of Mono is supported, however **5.18.0** is the latest version that we currently test against. Version **3.10** or greater may work, however we strongly recommend using a supported version.
-
-You can find instructions for installing Mono in the [Mono documentation](http://www.mono-project.com/docs/getting-started/install/linux/).
-
-### Calamari on Mono limitations
-
-#### TLSv1.2 support available in Mono >= 4.8.0
-[TLSv1.2 support](http://www.mono-project.com/docs/about-mono/releases/4.8.0/#tls-12-support) was only included from Mono version **4.8.0**. Due to the weak cryptographic nature of older encryption algorithms, many websites are no longer providing support for TLSv1 TLSv1.1 and as such clients must ensure that they are able to use TLSv1.2 in order to communicate.
-
-Although previous versions of Mono should work in most deployment scenarios, any deployments that involve the target accessing endpoints that require TLSv1.2 (for example downloading from [Maven](/docs/packaging-applications/package-repositories/maven-feeds/) or [GitHub](/docs/packaging-applications/package-repositories/github-feeds) feeds) may fail.
-
-#### .NET Configuration transformations only available in Mono >= 4.2.3  
-
-The [.NET configuration transforms](/docs/projects/steps/configuration-features/xml-configuration-variables-feature) feature will only work on Mono **4.2.3** and above.
-
-This was due to a [bug with XML Transformations](https://bugzilla.xamarin.com/show_bug.cgi?id=19426).
-
-Note that [substitute variables in templates](/docs/projects/steps/configuration-features/substitute-variables-in-templates) can still be used without issue on earlier Mono versions.
-
-#### Package repository SSL certificates
-
-If you configure your deployment such that the target pulls down the package itself directly from the NuGet repository, the correct SSL certificates need to also be available to Mono. By default, Mono pre **3.12** didn't trust any certificates and the root certs in question would need to be either manually imported, or synced with Mozilla's list by invoking `mozroots` or `cert-sync`. Thankfully Mono's latest builds perform this step during installation so it should “just work”.
-
-See [Mono's security FAQ](http://www.mono-project.com/docs/faq/security/) for more details.
-
-#### Mono on OSX
-
-If you are using a Mac with OSX as an SSH deployment target, you may see the following error message:
-
-`Required command 'mono' is not available`
-
-This can occur even if Mono is installed and can be executed from a local shell. This is because the environment exposed to an SSH session can differ from the environment used by a local shell.
-
-To fix this:
-
-1. If it doesn't already exist, create a file called `.bashrc` in the home folder of the user that is connecting to the Mac OSX instance. If the remote user is called `octopus`, then this file will be located at `/Users/octopus/.bashrc`.
-2. Add the path environment variable to the `.bashrc` file to include the location of the mono executable e.g.
-
-```
-export PATH=/Library/Frameworks/Mono.framework/Versions/Current/bin/:${PATH}
-```
-
 ## Learn more
 
 - Configure your [SSH deployment targets](/docs/infrastructure/deployment-targets/linux/ssh-target)

src/shared-content/tentacle/configure-ssh-connection-target.include.md

@@ -31,9 +31,6 @@ For Octopus Server prior to **2024.2.6856** use the following:
 ssh-keygen -E md5 -lf /etc/ssh/ssh_host_ed25519_key.pub | awk '{ print $2 }' | cut -d':' -f2-
 ```
 
-10. Specify whether Mono is installed on the SSH target or not to determine which version of [Calamari](/docs/octopus-rest-api/calamari) will be installed.
-
-  - [Calamari on Mono](#mono-calamari) built against the full .NET framework.
-  - [Self-contained version of Calamari](#self-contained-calamari) built against .NET Core.
+10. Select the **Platform** (OS and architecture) of the target server.
 
 11. Click **Save**.