[Freerdp-devel] have a question,
Hi I have a question to use this FreeRDP. I am coding python such like this. " ... import struct import sys from freerdp import rdpRdp from freerdp import crypto from freerdp.rdpRdp import rdpNego " When I execute this such as "python free.py", such error appeared File "free.py", line 10, in ? from freerdp import rdpRdp ImportError: No module named freerdp How can I solve this problem? I am using RHEL 5 and installed these rpms freerdp-1.0.1-3.el5.i386.rpm freerdp-devel-1.0.1-3.el5.i386.rpm freerdp-libs-1.0.1-3.el5.i386.rpm freerdp-plugins-1.0.1-3.el5.i386.rpm Please give me good answer. Wait your reply. Regards. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
[Freerdp-devel] FreeRDP on Android and iOS
Hi Is there any interest in a shared and open port of FreeRDP to the tablet platforms? I am sure there will be one. The question is when, and how many then will be left at a dead end with their own port. /Mads -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [Freerdp-devel] have a question,
On Mar 20, 2012 9:30 AM, "xin a" wrote: > > Hi > > I have a question to use this FreeRDP. > > I am coding python such like this. There is no such thing as a FreeRDP python module, and that code is from a *fake* MS12-020 proof of concept. You are way behind on this, many real working exploits have been published since then. Just a reminder to everyone if you've been living under a rock: patch your systems ASAP. Many working exploits float on the internet, but they are all denial of service attacks. Remote code execution exploits are in the works, and you probably don't want to wait until those are out in the wild before patching your stuff. > > " > ... > import struct > import sys > from freerdp import rdpRdp > from freerdp import crypto > from freerdp.rdpRdp import rdpNego > > " > > When I execute this such as "python free.py", such error appeared > > File "free.py", line 10, in ? > from freerdp import rdpRdp > ImportError: No module named freerdp > > How can I solve this problem? > I am using RHEL 5 and installed these rpms > freerdp-1.0.1-3.el5.i386.rpm > freerdp-devel-1.0.1-3.el5.i386.rpm > freerdp-libs-1.0.1-3.el5.i386.rpm > freerdp-plugins-1.0.1-3.el5.i386.rpm > > Please give me good answer. > > Wait your reply. > > Regards. > -- > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > ___ > Freerdp-devel mailing list > Freerdp-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freerdp-devel -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
Re: [Freerdp-devel] mingw cross compilation from linux to windows
Actually, I had to apply the following very small patch to one of
FreeRDPs headers because Mingw already defines the "boolean" type in one
of its headers:
Index: include/freerdp/types.h
==
--- include/freerdp/types.h
+++ include/freerdp/types.h
@@ -63,11 +63,11 @@
typedef signed long long sint64;
#endif
#endif /* HAVE_INTTYPES_H */
-#ifdef HAVE_STDBOOL_H
+#if defined(HAVE_STDBOOL_H) && !(defined(__MINGW32__) || defined(__MINGW64__))
#include
typedef int boolean;
Additionally, I changed the CMakeFile.txt in the main directory because I
wanted a statically linked version of wfreerdp:
Index: CMakeLists.txt
==
--- CMakeLists.txt
+++ CMakeLists.txt
@@ -48,11 +48,11 @@
set(CMAKE_BUILD_TYPE "Release")
endif()
# build shared libs
if(NOT BUILD_SHARED_LIBS)
-set(BUILD_SHARED_LIBS ON)
+#set(BUILD_SHARED_LIBS ON)
endif()
# Compiler-specific flags
if(CMAKE_COMPILER_IS_GNUCC)
set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wall")
Then I ran cmake like this (I install FreeRDP in a local directory in my $HOME
which is specified in $INSTALLPATH), OpenSSL (1.0.0g) is installed in this
folder as well:
cmake -DCMAKE_SYSTEM_NAME="Windows" \
-DCMAKE_C_COMPILER="/usr/local/mingw/bin/x86_64-w64-mingw32-gcc" \
-DCMAKE_RC_COMPILER="/usr/local/mingw/bin/x86_64-w64-mingw32-windres" \
-DCMAKE_INSTALL_PREFIX="$INSTALLPATH" \
-DBUILD_SHARED_LIBS=OFF \
-DCMAKE_C_FLAGS="-DFREERDP_EXPORTS -Dsprintf_s=snprintf $CFLAGS" \
-DCMAKE_EXE_LINKER_FLAGS="$LDFLAGS" \
-DWITH_SSE2=OFF \
-DWITH_SSE2_TARGET=OFF \
-DOPENSSL_INCLUDE_DIR="$INSTALLPATH/include" \
-DLIB_EAY="$INSTALLPATH/lib/libcrypto.a" \
-DSSL_EAY="$INSTALLPATH/lib/libssl.a" \
.
Am Dienstag, den 20.03.2012, 01:27 +0100 schrieb Mads Kiilerich:
> You could build without any patches?
>
> Ok - I will try harder ;-)
>
> /Mads
>
>
> Felix Wolfheimer wrote, On 03/19/2012 10:26 PM:
> > Hi Mads,
> >
> > I also cross-compiled Freerdp-1.0.1 (Mingw-w64 version 2.0 with gcc
> > 4.7.0) for 32 Bit as well as for 64 Bit Windows. I tested it recently on
> > a Windows 7 (64 Bit) client connecting to a Windows Server 2008 R2.
> >
> > You need to specify a user name and password on the command line like
> > this:
> >
> > wfreerdp -u -p
> >
> > Then the connection works (at least in my setup). If you omit this it
> > will fail silently. But the functionality is currently very limited. In
> > my case the color scheme is completely messed up for some reason (looks
> > like it uses an 8 bit color scheme) and it seems to ignore any attempt
> > to change this.
> >
> > Note: If you define the PP macro WITH_DEBUG when you compile wfreerdp it
> > will create a console window where you can see its output. Guess that
> > will help to find out why it fails in your case.
> >
> > Regards
> >
> > Felix
> >
> >
> >
> > Am Montag, den 19.03.2012, 20:57 +0100 schrieb Mads Kiilerich:
> >> I am trying to compile FreeRDP with mingw32 from Fedora 16 to win32.
> >>
> >> With a non-trivial number of patches it compiles ... but it silently
> >> fails to run.
> >>
> >> Has anybody else seen any success with mingw compilation recently?
> >>
> >> https://github.com/FreeRDP/FreeRDP/wiki/Compilation from a couple of
> >> months ago mentions cross compilation with Mingw-w64, so I wonder if I
> >> am doing something wrong or if things has changed a lot since then?
> >>
> >> /Mads
> >>
> >> --
> >> This SF email is sponsosred by:
> >> Try Windows Azure free for 90 days Click Here
> >> http://p.sf.net/sfu/sfd2d-msazure
> >> ___
> >> Freerdp-devel mailing list
> >> Freerdp-devel@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/freerdp-devel
> >
>
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
___
Freerdp-devel mailing list
Freerdp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
[Freerdp-devel] Japanese Keyboard not working
Dear all,
I am trying to get 109 Japanese Keyboard (*1) to work with freerdp without
success.
(*1) Actually the 109A keyboard. I am told that it is very similar to
109 and the difference between them is minimal, as shown in the
2nd image of the following link (Sorry in Japanese):
http://home.impress.co.jp/magazine/dosvpr/q-a/0305/qa0305_1.htm
+ Note the "~" highlighted in grey, you can ignore the rest.
I haven't checked all the keys but some keys, particulary at the right
side of the keyboard (*2) doesn't seem to work as intended.
(*2) Some examples represented in this picture, right-side keys with
scancode highlighted on them.
http://www.win.tue.nl/~aeb/linux/kbd/jp106-with-scancodes.jpg
-> goto http://www.win.tue.nl/~aeb/linux/kbd/scancodes-8.html to
see imprinted symbols on key.
I am still unable to get the RDP server to correctly recognize the keys
and I would very much appreciate if anyone can help me fix this issue.
Here's what I did/found so far: (A bit too long but please bear with me)
I had no clue as to what might be wrong so I put my focus on the "\|"
keycap (and work my way up to other keycaps).
Here is my understanding of keycodes and scancodes for "\" (compiled
from various sources):
X11 keycode: AE13(0x84)#(*3)
Virtual keycode: VK_OEM_5 (0xDC) #(*4)
scancode #: 0x7D #JIS109 Keyboard(*5)
(*3) /usr/share/X11/xkb/keycodes/evdev
(*4) http://www.win.tue.nl/~aeb/linux/kbd/scancodes-8.html
(*5) http://msdn.microsoft.com/en-us/library/ms892472.aspx
Downloaded the latest source 131c19f (at the time) on Xubuntu 11.10,
and enabled DEBUG_KBD. I run the executable and here's what I got:
DBG_KBD detect_keyboard_layout_from_xkb (378): display: 0x9384270
DBG_KBD detect_keyboard_layout_from_xkb (382): layouts: jp
DBG_KBD detect_keyboard_layout_from_xkb (383): variants:
DBG_KBD detect_keyboard_layout_from_xkb (390): group: 0
DBG_KBD detect_keyboard_layout_from_xkb (395): layout: jp
DBG_KBD detect_keyboard_layout_from_xkb (396): variant:
DBG_KBD find_keyboard_layout_in_xorg_rules (908): xkbLayout: jp xkbVariant:
DBG_KBD freerdp_keyboard_init_xkb (336):
detect_keyboard_layout_from_xkb: E0010411
>From the above message, it seems that freerdp correctly recognizes the
Japanese keyboard. However, there are multiple Japanese keyboard in the
world (106,109,109A, etc) and I am not sure if freerdp really knows it's a 109A
Japanese keyboard.
Further down the log, I find two "\|" relevant debug messages:
DBG_KBD freerdp_keyboard_load_map_from_xkb (483): AE13: keycode:
0x84 -> no RDP scancode found
::snip::
DBG_KBD freerdp_keyboard_get_rdp_scancode_from_x11_keycode (284):
x11 keycode: 84 -> rdp code: 00
>From these logs, I figured X11 -> VK -> SC conversion table is
incorrect so I changed the following 2 codes:
*** libfreerdp-locale/keyboard_xkb.c2012-03-13 15:53:12.599159139 +0900
--- libfreerdp-locale/keyboard_xkb.c_org201203132012-03-08
17:47:00.0 +0900
***
*** 257,263
{ 0,"", "" },
{ 0,"", "" },
{ VK_OEM_4, "AD11", "" }, /* VK_OEM_4 */
! { VK_OEM_5, "AE13", "" }, /* VK_OEM_5 */
{ VK_OEM_6, "AD12", "" }, /* VK_OEM_6 */
{ VK_OEM_7, "AC11", "" }, /* VK_OEM_7 */
{ VK_OEM_8, "", "" }, /* VK_OEM_8 */
--- 257,263
{ 0,"", "" },
{ 0,"", "" },
{ VK_OEM_4, "AD11", "" }, /* VK_OEM_4 */
! { VK_OEM_5, "BKSL", "" }, /* VK_OEM_5 */
{ VK_OEM_6, "AD12", "" }, /* VK_OEM_6 */
{ VK_OEM_7, "AC11", "" }, /* VK_OEM_7 */
{ VK_OEM_8, "", "" }, /* VK_OEM_8 */
*** libfreerdp-locale/keyboard_layout.c 2012-03-13 14:38:53.673048515 +0900
--- libfreerdp-locale/keyboard_layout.c_org20120314 2012-03-08
17:47:00.0 +0900
***
*** 691,697
0x00,
0x00,
0x1A, /* VK_OEM_4 */
! 0x7D, /* VK_OEM_5 */
0x1B, /* VK_OEM_6 */
0x28, /* VK_OEM_7 */
0x1D, /* VK_OEM_8 */
--- 691,697
0x00,
0x00,
0x1A, /* VK_OEM_4 */
! 0x2B, /* VK_OEM_5 */
0x1B, /* VK_OEM_6 */
0x28, /* VK_OEM_7 */
0x1D, /* VK_OEM_8 */
This produced the following debug message, and I can see that freerdp
is sending the correct rdp scancode value to the RDP server.
DBG_KBD freerdp_keyboard_load_map_from_xkb (471): AE13: keycode:
0x84 -> vkcode: 0xDC -> rdp scancode: 0x7D
::snip::
DBG_KBD freerdp_keyboard_get_rdp_scancode_from_x11_keycode (284):
x11 keycode: 84 -> rdp code: 7D
On the RDP server-side(tried both Windows
