You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG
+7-1Lines changed: 7 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,10 @@
1
-
2021-03-07 Version 2.9.2
1
+
2021-07-22 Version 2.9.3
2
+
pre-requisites PLEASE READ! Myrtille requires a Windows Server edition (2012 R2 or greater) for itself (remote servers can be whatever OS with RDP enabled). Windows client editions (7, 8, 10 - whatever the version: pro, enterprise, ultimate, etc.) are not suitable for Myrtille due to the limitation to a maximum of 10 simultaneous connections on IIS!
3
+
a client is now identified by an unique id instead of a cookie based key; this fixes a problem of sharing a session by url within the same browser
4
+
disabled the share session by url feature (web.config), because it bypasses the share session by guest logic and make it difficult to track the active clients
5
+
redesigned the adaptive display tweaking logic, based on bandwidth usage
6
+
7
+
2021-03-07 Version 2.9.2
2
8
FreeRDP is now built as a dll instead of an executable for better modularity and to reduce the risk of false positive detection of wfreerdp.exe by some antiviruses (mostly cloud based)
3
9
embedded interact.js and simple-keyboard (nodejs modules) into myrtille in order to remove dependencies on external CDNs (ans thus allow myrtille to be used standalone and not subject to external changes)
4
10
fixed a problem with the creation of the self-signed certificate that prevented Myrtille from installing correctly on Windows Server 2012 R2 (thanks camjcorley)
Copy file name to clipboardExpand all lines: DOCUMENTATION.md
+1-5Lines changed: 1 addition & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -41,18 +41,14 @@ I hope you will enjoy Myrtille! :)
41
41
Special thanks to Catalin Trifanescu for its support.
42
42
43
43
## Installation
44
-
Starting from version 2.8.0, the Myrtille requirements change: Windows 8.1 or Windows Server 2012 R2 or greater. This is partly because of the automated installation of the roles and features required by myrtille (which requires a modern powershell) and partly to deliver the best user experience possible (fast display and audio support), as HTML5 websockets (supported by all browsers nowadays) are only available in IIS 8.0+ (Windows 8.1 or Windows Server 2012 R2 or greater).
45
-
46
-
That said, Myrtille will continue to fallback to HTML4 (xhr and long-polling) if websockets are not enabled into IIS (it's optional) or if the websocket traffic is blocked by any network equipment.
44
+
Windows Server OS (2012 R2 or greater, with IIS 8.0+, .NET 4.5+ and WCF/HTTP activation enabled). CAUTION! IIS on Windows client OSes (7, 8, 10 - all versions) is limited to 10 simultaneous connections only - across all http sessions - and will hang after that!
47
45
48
46
The .NET 4.5+ framework can be installed automatically by the myrtille installer, enabled as a feature of IIS (Web Server role > Applications Development > ASP.NET 4.5 on Windows Server 2012) or installed separately (https://www.microsoft.com/en-us/download/details.aspx?id=30653).
49
47
50
48
Into the roles and features management, ensure you have enabled **HTTP Activation** under ".NET Framework 4.5+ Features" > "WCF Services" (required by the Myrtille services and REST API).
51
49
52
50
The installer does install myrtille under the IIS default website and creates a custom application pool ("MyrtilleAppPool"). If you want to use another website or application pool, you can change it manually afterward (with the IIS manager).
53
51
54
-
CAUTION! IIS on Windows client OSes (7, 8, 10) is limited to 10 simultaneous connections only - across all http sessions - and will hang after that! (https://forums.asp.net/t/2062118.aspx?+limit+of+10+simultaneous+connections+imposed+). Use Windows Server editions for production environments.
55
-
56
52
All releases here: https://github.com/cedrozor/myrtille/releases
Copy file name to clipboardExpand all lines: Myrtille.Web/Web.Base.config
+2-3Lines changed: 2 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -181,13 +181,12 @@
181
181
<!-- allow audio plaback -->
182
182
<addkey="AllowAudioPlayback"value="true"/>
183
183
<!-- share a session by url, with owner rights. set to false to disable and provide a session url spoofing protection. requires cookieless="UseUri" session state (system.web/sessionState section above) -->
184
-
<!-- if a session is shared by url between different clients, each client is identified by a unique key instead of the http session id -->
185
-
<addkey="AllowShareSessionUrl"value="true"/>
184
+
<addkey="AllowShareSessionUrl"value="false"/>
186
185
<!-- client ip protection -->
187
186
<addkey="ClientIPTracking"value="false"/>
188
187
<!-- if the browser window/tab of the remote session owner is closed without disconnecting first, or if the connection is lost, delay (ms) before the remote session is disconnected by the gateway. value must be greater than "browserPulseInterval" defined into config.js (default 10 secs). 0 to disable -->
189
188
<!-- this comes in addition but does not replace the session idle timeout, defined at the RDS level, which will disconnect the session after no user inputs are received for a given time, independently of Myrtille -->
190
-
<addkey="ClientIdleTimeout"value="0"/>
189
+
<addkey="OwnerIdleTimeout"value="0"/>
191
190
<!-- audio buffer. improves the audio quality at the expense of a slight latency -->
192
191
<addkey="AudioBuffering"value="true"/>
193
192
<!-- show or hide the toolbar (you can hide it if using your own UI) -->
varimageQuality=75;// image quality (%) higher = better; not applicable for PNG (lossless); tweaked dynamically to fit the available bandwidth if using JPEG, AUTO or WEBP encoding.
128
128
varimageQuantity=100;// image quantity (%) less images = lower cpu and bandwidth usage / faster; more = smoother display (skipping images may result in some display inconsistencies). tweaked dynamically to fit the available bandwidth; possible values: 5, 10, 20, 25, 50, 100 (lower = higher consolidation rate)
129
-
varimageTweakBandwidthLowerThreshold=50;// tweak the image quality & quantity depending on the available bandwidth (%): lower threshold. see network.js
130
-
varimageTweakBandwidthHigherThreshold=75;// tweak the image quality & quantity depending on the available bandwidth (%): higher threshold. see network.js
129
+
varimageTweakBandwidthThreshold=50;// tweak the image quality depending on the available bandwidth (%): threshold. see network.js
131
130
varimageCountOk=100;// reasonable number of images to display at once; for HTML4 (divs), used to clean the DOM (by requesting a fullscreen update) as too many divs may slow down the browser; not applicable for HTML5 (canvas)
132
131
varimageCountMax=300;// maximal number of images to display at once; for HTML4 (divs), used to clean the DOM (by reloading the page) as too many divs may slow down the browser; not applicable for HTML5 (canvas)
133
132
varimageMode=imageModeEnum.AUTO;// image mode
@@ -145,15 +144,15 @@ function Config(
145
144
varroundtripDurationMax=0;// roundtrip duration (ms) above which the connection is considered having issues, displaying a warning message to the user. 0 to disable
146
145
varbandwidthCheckInterval=300000;// periodical bandwidth check; used to tweak down the images (quality & quantity) if the available bandwidth gets too low. it relies on a 5MB dummy file download, so this param shouldn't be set on a too short timer (or it will eat the bandwidth it's supposed to test...)
varwebsocketCount=5;// number of concurrent websockets to send the user inputs and receive the display updates (RDP host only, max 100). splitting the load across multiple websockets can help to mitigate network lag. 1 for duplex websocket. CAUTION! IIS on Windows client OSes (7, 8, 10) is limited to 10 simultaneous connections only - across all http sessions - and will hang after that! use Windows Server editions for production environments
147
+
varwebsocketCount=2;// number of concurrent websockets to send the user inputs and receive the display updates (RDP host only, max 100). splitting the load across multiple websockets can help to mitigate network lag. 1 for duplex websocket. CAUTION! IIS on Windows client OSes (7, 8, 10) is limited to 10 simultaneous connections only - across all http sessions - and will hang after that! use Windows Server editions for production environments
149
148
varhttpSessionKeepAliveInterval=30000;// periodical dummy xhr calls (ms) when using websocket, in order to keep the http session alive
varbufferDelayEmpty=10;// buffering duration (ms) when sending empty buffer
155
154
varbufferSize=128;// max number of buffered items (not size in bytes)
156
-
varbrowserPulseInterval=10000;// periodical browser pulse (ms); used server side to detect if the browser window/tab was closed (and possibly disconnect the remote session before the RDS idle timeout occurs; see "ClientIdleTimeout" into web.config)
155
+
varbrowserPulseInterval=10000;// periodical browser pulse (ms); used server side to detect if the browser window/tab was closed (and possibly disconnect the remote session before the RDS idle timeout occurs; see "OwnerIdleTimeout" into web.config)
157
156
158
157
// user
159
158
varmouseMoveSamplingRate=100;// sampling the mouse moves (%) may help to reduce the server load in applications that trigger a lot of updates (i.e.: imaging applications); possible values: 5, 10, 20, 25, 50, 100 (lower = higher drop rate)
0 commit comments