Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NLA security #28

Closed
ciberx opened this issue Apr 24, 2015 · 5 comments
Closed

NLA security #28

ciberx opened this issue Apr 24, 2015 · 5 comments

Comments

@ciberx
Copy link

ciberx commented Apr 24, 2015

Why in NLA Security level connection (with -n key), credetentials are not asks (as on attached picture) before connect and then this session are closed?
image

@citronneur
Copy link
Owner

In fact this windows is a window from credential provider of windows. We not call it. You need to provide throught command line arguments your credentials. I have to add a warning or an equivalent prompt ok.

Sylvain

@ciberx
Copy link
Author

ciberx commented Apr 24, 2015

Ok, but why in direct connection this window appear?

@citronneur
Copy link
Owner

Because nla man in the middle throught credssp is not possible. So in server side rdpy ask classic ssl connection without nla. And in client side it can use nla. In RDP it's the server which choose the protocol! RDPY choose ssl as server and nla for client. But need to provide credentials. I keep this bug open.

@obeleh
Copy link

obeleh commented Jan 24, 2016

I'm sorry if this is a stupid question. Can you explain why it is not possible? Why would it not be possible to start a NLA server with RDPY?

@armin884
Copy link

armin884 commented Jun 2, 2016

@obeleh look here #39
But my question is even if NLA is not possible how does the client decide to use CredSSP or not? Does rdpy support CredSSP ? I'm still looking for a way to get that security prompt before connecting to server...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants