xrdp-proprietary

Author	SHA1	Message	Date
daixj	b3a1889200	Support Cache Glyph Revison 2, issue #367	6 years ago
Idan Freiberg	28d1fa7620	Merge pull request #1192 from hate-m-dollarsign/devel xrdp: Use configured values instead of hardcoded ones in login_wnd inputs.	6 years ago
Koichiro IWAO	171f8e79ed	xrdp: deprecate TLSv1 and TLSv1.1 Most websites disabled TLSv1 (1.0) and TLSv1.1 since March 2018 [1][2][3]. It is HTTPS context but there's few differences between HTTPS and other TLS connections. Users can whenever re-enable these deprecated TLS versions by editing xrdp.ini but not enabled by default. [1] https://www.globalsign.com/en/blog/disable-tls-10-and-all-ssl-versions/ [2] https://www.thesslstore.com/blog/deprecation-tls-1-0-1-1-underway/ [3] https://www.digicert.com/blog/depreciating-tls-1-0-and-1-1/	6 years ago
Koichiro IWAO	1ad8cbb2a0	Document TLSv1.3 support	6 years ago
jsane	fadbd20baf	xrdp: Use configured values instead of hardcoded ones in login_wnd inputs. Configured ls_label_width and ls_input_width currently only apply to the combo l abel and dropdown. Other labels and inputs (username, password, port, ...) use hardcoded defaults. Also had to change the default label width; for the previous value of 60, "username" ends up just a few pixels too wide.	6 years ago
Vraiment	9ed5243de9	Make xrdp.ini to be dynamic for each operating system	7 years ago