Well, the third and only correct solution would be xrdp getting its own
mechanism for dropping prvileges, so it could read the key as root and
then drop to the xrdp user.
You have a point. Running daemon under user privilege is a good practice
if root privilege is actually unnecessary. xrdp sh
Hi,
On Tue, 2017-03-07 at 11:55 +0100, Dominik George wrote:
> For now, I think the local administrator should add xrdp to the ssl-cert
> group if they want to use TLS. This is IMHO not a bug in the package,
> because by default, xrdp also uses RDP security and adding daemon users
> to ssl-cert is
Hi,
> In Debian, xrdp daemon is executed by xrdp user privilege. However,
> certificate's
> private key is not accessible by xrdp user.
>
> Possible solutions are:
> - Adjust permission/owner of private key file to be accessible from xrdp
> user
> - Add xrdp user to ssl-cert group
Well, the thir
Hi Jacco, Dominik, and other maintainers,
I am an upstream xrdp developer. I also encountered this issue.
If my issue and your issue is same, probably the reason you can't connect is
certificate's private key is not accessible byxrdp daemon. Please check your
private key permission.
In Debian, xr
Package: xrdp
Version: 0.9.1-7
Severity: normal
Dear Maintainer,
If in xrdp.ini the option security_layer=tls is configured, a client is not
able to connect.
E.g. on the client-side using rdesktop the following error is displayed:
140464326739656:error:1408F10B:SSL routines:SSL3_GET_RECORD:wron
5 matches
Mail list logo
