Show Posts

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.


Messages - Digi

Pages: [1] 2 3 ... 6
1
Internet / Re: Problems with OpenSSL library after update.
« on: Today at 11:48:28 am »
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.

I've been playing around with different values ​​for this variable, but so far without success.

For the curious, the relevant code is at

crypto\cryptlib.c:694
    if ((env = getenv("OPENSSL_ia32cap"))) {

in the netlabs openssl sources.

I don't see such a line in file https://github.com/bitwiseworks/openssl-os2/blob/master/crypto/cryptlib.c . There are only 282 lines.

2
Internet / Re: Problems with OpenSSL library after update.
« on: February 02, 2026, 03:25:08 am »
I think it's better to fix the problem itself than to create new workarounds. AVX support is a really big plus.

The OS/4 developers are currently at war in their own country ...[censored]... people there might have other concerns right now.

3
Internet / Re: Problems with OpenSSL library after update.
« on: February 02, 2026, 01:45:23 am »
My research has shown that the problem only occurs when using the OS/4 kernel. This kernel, unlike the ArcaOS kernel, has support for AVX - NPX thread context switching, etc. Most likely, OpenSSL checks for AVX support (via xgetbv?), and the problematic section of code with the ArcaOS kernel simply does not execute.

It would be great if the alignment issue (?) were resolved. Or, if it were easier, AVX support could be removed from OpenSSL. Although that's certainly not the best solution.

Unfortunately, the ArcaOS kernel here does not work well in VMWare

4
Internet / Re: Problems with OpenSSL library after update.
« on: January 26, 2026, 03:39:45 am »
Done. Updated the GitHub post.

5
Internet / Problems with OpenSSL library after update.
« on: January 24, 2026, 05:56:41 pm »
After updating the libraries on the internet server, one of the applications began crashing frequently. It turned out that the crashes were occurring in crypto11.dll when calling the SSL_accept() function (openssl ver. 1.1.1w-1).

I tried installing openssl version 3.4.1-2 from the netlabs-exp repository, and the situation repeated: crashes in crypto3.dll when calling SSL_accept().

Crashes don't happen every time. They mostly occur on certain connections from open port scanners or some hacking tools that operate over the internet.

My report on this issue on GitHub: https://github.com/bitwiseworks/openssl-os2/issues/6

If you use server applications related to openssl, do not update openssl yet!

6
Networking / Re: uacme
« on: January 21, 2026, 01:12:18 pm »
Thank you very much!

7
Networking / Re: uacme
« on: January 21, 2026, 12:43:21 am »
I'm trying to follow these instructions:
https://github.com/ndilieto/uacme/

But at the very first step I have a problem:

C:\Programs\uacme\bin>uacme.exe -v -c C:\Programs\uacme\bin\uacme.d new
uacme.exe: version 1.0.19 starting on Wed, 21 Jan 2026 10:39:02
uacme.exe: loading key from C:\Programs\uacme\bin\uacme.d/private/key.pem
uacme.exe: C:\Programs\uacme\bin\uacme.d/private/key.pem not found
uacme.exe: generating new 2048-bit RSA key
uacme.exe: key saved to C:\Programs\uacme\bin\uacme.d/private/key.pem
uacme.exe: fetching directory at https://acme-v02.api.letsencrypt.org/directory
uacme.exe: curl_get: GET https://acme-v02.api.letsencrypt.org/directory failed: Problem with the SSL CA cert (path? access rights?)
uacme.exe: curl_get: waiting 5 seconds before retrying

I can download the "directory" file manually without any problems (curl -O https://acme-v02.api.letsencrypt.org/directory).

What am I doing wrong?

8
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: April 01, 2025, 04:24:41 am »
How about an OS/2 or ARCOS without Windows and DOS? Wouldn't that be easier?

I think that DOS (and Win-OS2) should have been thrown out of the system many years ago. :-)

9
Quick test - I works :-)

Not much time for extensive test, but €@²³µ work now. Thanks.

Excellent! Thank you.

10
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).

As I understand it, the codes in your post are codes for X11. According to this: https://github.com/sulmone/X11/blob/master/share/X11/xkb/keycodes/xfree86 , your option 2 is AltGr -> LCTL + RALT. But that's exactly what OS/2 freerdp does now. However, I found that Right Alt can be sent to the RDP server with two different scan codes.  :o

Please check this: http://os2.snc.ru/pub/freerdp/test/freerdp-wpi-20250217.zip
here I use a different scancode for Right Alt to send AltGr -> Left Ctrl + Right Alt.

PS: I don't understand which key corresponds to code 108.

11
With Win10 it works as expected. Seems some setting in X11 / xrdp?

Hmm... Looks like it.
To be completely sure, it remains to check the Linux freerdp client to Debian. :)

12
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

I can't remember exactly what /kbd affects right now, I think we'll try without it for now (but of course nothing stops you from trying  :) ).

Now I thought - maybe I should send Left Ctrl + Left Alt instead of Left Ctrl + AltGr. If so, you should be able to type "@" by pressing Left Ctrl + Left Alt + q. Try it (but I doubt it).

It would be very interesting to know if AltGr works now on German systems when connecting ofreerdp to Windows...

13
Hi

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....

I see my old comment in the source code:

  /* Support for the AltGr key on a German keyboard
     (Request from Herwig Bauernfeind). */

Then the following scheme is executed: 1. The current country for OS/2 is recognized. 2. If it is Germany (code 49) and the Right Alt (AltGr) key is pressed, then the remote system is sent a press of two keys: Left Ctrl and Right Alt (AltGr).

I think it worked then because that part of the code hadn't changed for a very long time. Could you (or somebody from German here) verify that it doesn't work if you connect to Windows?

And please try the following (it doesn't matter whether it's with Linux or Windows): take this test version:

http://os2.snc.ru/pub/freerdp/test/freerdp-wpi-20250214.zip

Connect to the remote system, press and release the AltGr key, and look at the console. If everything is ok, you should see lines like this:

!TEST! country: 49, codepage: 850
!TEST! Right Alt (pressed) -> Ctrl (0x1D) + Right Alt
!TEST! Right Alt (released) -> Ctrl (0x1D) + Right Alt

If you only see the first line with a different country code, please let me know.

14
Web applications / Re: Dooble releases, Qt5 builds
« on: December 19, 2024, 10:56:23 pm »
I was able to choose a font that made the text visible. Now configured:
  Sans Serif: Droid Serif
But with most of the fonts I choose the text becomes invisible.

Now there is a new problem - I can't enter text in my language in the address bar and in forms on websites. Only English works. The text is not being entered, this is not due to the fact that it is invisible.

15
Web applications / Re: Dooble releases, Qt5 builds
« on: December 19, 2024, 10:24:41 pm »
Have you tried moving the profile out of the way? It is in %HOME%\.dooble. Other then that and trying different fonts, I don't have any ideas.

I tried this, it doesn't help.

What do you have under [tools] - [Inject custom style sheet] ?

See attachment.

Pages: [1] 2 3 ... 6