mRemoteNG

Repository on GitHub, which provides public git repositories with URLs.

Repository on GitHub, which uses git. git can track the changes, who made them, and when they were made.

https://github.com/mRemoteNG/mRemoteNG/releases We publish public alpha, beta, and release candidate (RC) versions prior to final release.

Repository on GitHub, which uses git. git is distributed.

https://github.com/mRemoteNG/mRemoteNG/releases All versions follow Major.Minor.CodedBuildDate.CodedBuildTime. This guarantees unique version numbers for every build.

The current dev team is following the version numbering convention used by the previous maintainers. Modifying the versioning scheme to follow SemVer has not been seriously discussed yet. Modifying the versioning scheme must be carefully considered before implementing.

We utilize git tags for every publicly released version (alpha, beta, RC, final)

Non-trivial release notes file in repository: https://github.com/mRemoteNG/mRemoteNG/blob/develop/CHANGELOG.TXT.

Every known issue is documented in a ticket (previously Jira, now Github Issues) and every resolved ticket is included in the release notes along with a brief description.

https://github.com/mRemoteNG/mRemoteNG/issues GitHub Issues

https://github.com/mRemoteNG/mRemoteNG/issues GitHub Issues

We try to answer/acknowledge most new issues the same day we receive them. https://github.com/mRemoteNG/mRemoteNG/issues

We try to answer/acknowledge most new requests the same day we receive them, or at least within the week. https://github.com/mRemoteNG/mRemoteNG/issues

GitHub Issues has a search feature that includes closed issues. https://github.com/mRemoteNG/mRemoteNG/issues

https://mremoteng.org/security

No specific vulnerability reports have been made known to us within that time frame.

As the project is in C# (with project files) users can build within Visual Studio, or directly using msbuild.

Msbuild is common for our chosen language (C#)

The primary build engine MSBuild is open source under the MIT license https://github.com/Microsoft/msbuild

Our tests are released in the same project/repo as the primary application and is licensed under GPL v2

Tests can be run via any NUnit compatible test runner. The requirement for the NUnit test runner is documented in our wiki: https://github.com/mRemoteNG/mRemoteNG/wiki/Development%20Environment

The code base was at ~30,000 lines before the test suite was created. In some cases the code is not designed with testing in mind. All new features or improvements receive tests were feasible, though we are currently only at ~10% coverage overall.

http://jenkins.mremoteng.org:8080/

We have an informal policy of creating test for all new functionality where possible. Some of the code base is very difficult to test, though when possible it is refactored to make it possible. The majority of recent new features have tests.

Recent major changes: - Encryption update and its tests: ---- https://github.com/mRemoteNG/mRemoteNG/issues/157. ---- https://github.com/mRemoteNG/mRemoteNG/tree/develop/mRemoteNGTests/Security - Connection tree update and its tests: ---- https://github.com/mRemoteNG/mRemoteNG/issues/143 ---- https://github.com/mRemoteNG/mRemoteNG/tree/develop/mRemoteNGTests/Tree

We request that PRs include added/updated tests when possible https://github.com/mRemoteNG/mRemoteNG/blob/develop/.github/CONTRIBUTING.md#pull-requests

We fix the majority of warnings presented by the compiler.

We currently use the recommended warning setting (not maximum).

We are utilizing the BouncyCastle library for all future cryptographic functions. https://github.com/bcgit/bc-csharp

We are utilizing the BouncyCastle library for all future cryptographic functions. https://github.com/bcgit/bc-csharp

We are utilizing the BouncyCastle library for all future cryptographic functions. https://github.com/bcgit/bc-csharp

Key size used: 256

As of version 1.75 beta 1, we currently support AES256, Twofish, and Serpent running in GCM, CCM, or EAX modes. The default encryption method is AES256 in GCM mode.

We do not utilize asymmetric encryption.

The program must keep username/password pairs in an encrypted state as the plain text is later used for authentication with external systems. However, authentication used during decryption of those values does use iterated key stretching (PBKDF2) with a variable number of iterations (set by the user). Technical guards are in place to prevent the iteration count from being set below the minimally safe value of 1000 iterations.

We utilize the Org.BouncyCastle.Security.SecureRandom class for all number generation.

We utilize Https

We utilize Https

The core dev team utilizes ReSharper for static code analysis. All refactors/updates/new code is always subjected to analysis.

C# is a memory-safe language.