-
Notifications
You must be signed in to change notification settings - Fork 174
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
freerdp 1.2 not detected properly + incompatible (freerdp module not working) #6
Comments
I am sorry, Is there any working solution for RDP checking? I looked up freerdp code but found no way to check wheter auth data was correct or not. |
didn't they just renamed stuff? I'm pretty sure it has to be possible to check it one or the other way. Maybe try writing the authors an email (I would not just open an issue, they most likely will not notice that because of 200 other issues 😿 ) |
@anthraxx, I don't know, really, there's a lot of code and understanding of how it works will take a lot of time, but as far as I saw there's no definition of auth states and errors. Maybe they were in oldest versions? |
@astro-train maybe you don't have to mention that you write a bruteforce tool. just say you are writing a RDP (maybe GUI) tool that uses freerdp as a library and you want to check the authentication login state for success or different type of failed codes. Something like that 😄 |
@anthraxx, oh okay, but it still sounds like I'am writing bf. Lol FreeRDP/FreeRDP#2893 |
is there really no other way doing this? It really sounds weird that its not possible to get a result of a login attempt. 😭 |
There's talk on the FreeRDP mailing list of freezing the API later this summer and a release being in the foreseeable future. I'm planning to revisit the Medusa RDP module when that happens. FreeRDP has been too much of a moving target. |
that sounds awesome 😄
so the header is f.e. in |
@jmk-foofus In the mean time FreeRDP 1.x has gotten obsolete. Do you plan to port the code to version 2.x ? This is needed for the Debian package if we want to keep the RDP module enabled. See https://bugs.debian.org/888322 TIA. |
same applies for Arch Linux, i was forced to not ship RDP module for now 😢 |
I do plan to port the RDP module. Unfortunately, I do not have an estimated date for this.
Joe
From: Raphaël Hertzog [mailto:notifications@github.com]
Sent: Tuesday, February 6, 2018 2:12 AM
To: jmk-foofus/medusa <medusa@noreply.github.com>
Cc: jmk-foofus <jmk@foofus.net>; Mention <mention@noreply.github.com>
Subject: Re: [jmk-foofus/medusa] freerdp 1.2 not detected properly + incompatible (freerdp module not working) (#6)
@jmk-foofus <https://github.com/jmk-foofus> In the mean time FreeRDP 1.x has gotten obsolete. Do you plan to port the code to version 2.x ? This is needed for the Debian package if we want to keep the RDP module enabled. See https://bugs.debian.org/888322
TIA.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#6 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AMDPCa8ZB_TAag6ggV_93M8YUX8-30K6ks5tSAlUgaJpZM4HAmJZ> . <https://github.com/notifications/beacon/AMDPCSS4c-CEyXpiqrMjFKY8X9u4sCWmks5tSAlUgaJpZM4HAmJZ.gif>
|
RDP module in master should be working with current releases of FreeRDP. |
Hey,
I have noticed that the RDP plugin does not work properly with an up-to-date freerdp. The configure detection seems to fail and HAVE_LIBFREERDP12 will not be defined and therefor tries to use freerdp_channels_global_init:
the configure script fails to find WLog_CallbackAppender_SetCallbacks as that function does not exist in freerdp 1.2.0-beta1+android9 and also not in the current git HEAD.
But as mentioned, its not just the detection of 1.2 but also the API changed and there is no Log_CallbackAppender_SetCallbacks function anymore in the current freerdp git HEAD (neither in the last tag 1.2.0-beta1+android9).
It would be great if the freerdp module works with the current git HEAD, i would highly appreciate that 😄
cheers,
anthraxx
The text was updated successfully, but these errors were encountered: