1
Internet / Re: Problems with OpenSSL library after update.
« on: February 10, 2026, 03:17:53 am »The brute force
set OPENSSL_ia32cap=:0
should do this. The less brutish
set OPENSSL_ia32cap=:~0x20
I've already tried this. It doesn't help.
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
The brute force
set OPENSSL_ia32cap=:0
should do this. The less brutish
set OPENSSL_ia32cap=:~0x20
It appears it should be possible to configure OPENSSL at runtime to avoid attempting to use the problematic code via the OPENSSL_ia32cap environment variable.
For the curious, the relevant code is at
crypto\cryptlib.c:694
if ((env = getenv("OPENSSL_ia32cap"))) {
in the netlabs openssl sources.
How about an OS/2 or ARCOS without Windows and DOS? Wouldn't that be easier?
Quick test - I works :-)
Not much time for extensive test, but €@²³µ work now. Thanks.
I've now checked with xkbev which key codes is received. On the local keyboard AltGr produces keycode 108. When connected via ofreerdp the same key on the remote keyboard produces 2 keycodes - 37 and 64. Which probably is Ctrl and Alt. And this does not work. There are more differences but this one is the biggest problem.
Connecting the Linux box from Win10 instead OS/2 the Win AltGr produces keypress 37, keyrelease 37, keypress 113 and keyrelease 113.
So either our ofreerdp should send
1) keypress 108 when pressing AltGr and keyrelease 108 when releasing AltGr (in the meantime the other keys are should sent as usual) to mimik local behaviour or
2) keypress 37, keyrelase 37, keypress 113, keyrelease 113 to mimik Win behaviour. But Win make autorepeat of this sequence as long as AltGr is pressed. So option 1) like local keyboard maybe better
Have to say I'm no expert on this. But working combinations are -
- Win to Linux
- OS/2 to Win
non AltGr working is with -
- OS/2 to Linux
Also /kbd: options seems to do nothing (not implemented?) on our OS/2 client (ofreerdp.exe) as it always shows the usage messages. But this can be overcome with xrdp.ini and xrdp_keyboard.ini entries (force DE with override instead default to EN).

With Win10 it works as expected. Seems some setting in X11 / xrdp?
IBut none of the 3th keys work when I connect to a Linux/Debian box. I tried @ € ² ³ ~ tried. Currently I've no /kbd option on command line. Should I try again with /kbd:de,lang:de? My notes says this does not work in the past.
I start with (user/password changed to xxxx) -Code: [Select]ofreerdp.exe /u:xxx /p:xxx /w:2100 /h:1600 /v:m92p
).Still not working is <Alt Gr> <e> EURO character and even worse @ (Alt Gr + q). Or better said I've not found a way to insert these. The way with <Alt> + number keys don't work too. No clue if this is a general limitation of rdp or some setting or....