1.2.24 Release ( web release for 15/03/2019)

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Skyfighter » 2019-04-18 20:42

Thanks Rudi, but I've seen a similar description in info box while creating the AuthenticationKeys...and renamed them like that:
CAPSlower1234_Server_ClientAuth.pubkey
CAPSlower1234_Viewer_ClientAuth.pkey
SomethingElse_Server_ClientAuth.pubkey
SomethingElse_Viewer_ClientAuth.pkey
thereisonemore_Server_ClientAuth.pubkey
thereisonemore_Viewer_ClientAuth.pkey
Just to be sure I retested with a) lower case only and b) letters-only without numbers...but as soon as the server has "CAPSlower1234" and "SomethingElse" all viewer with only "SomethingElse" can't connect anymore. What have I done wrong?
Skyfighter
40
40
 
Posts: 105
Joined: 2014-12-31 22:10

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Rudi De Vos » 2019-04-20 10:08

server A has key mykey123__Server_ClientAuth.pubkey
server B has key mykey124__Server_ClientAuth.pubkey
Viewer has 2 keys mykey123_Viewer_ClientAuth.pkey en mykey124_Viewer_ClientAuth.pkey

Viewer use the correct key for each server
Tested viewer connnect to server

How are you testing ?
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5909
Joined: 2004-04-23 10:21

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Skyfighter » 2019-04-20 19:34

I'm testing on a single server with multiple (in my example: three) pubkey-files. In this constellation a viewer can only connect if it has the pkey for the first pubkey (alphabetical order) on the server. If a viewer "only" has the pkey's for the second and/or third pubkey of the server side a connection is not possible: "Response failed client authentication.".
In other words: multiple pubkeys on the server = only the first pubkey is usable (alphabetical order of the pubkey files) for viewers.
Skyfighter
40
40
 
Posts: 105
Joined: 2014-12-31 22:10

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Rudi De Vos » 2019-04-20 20:41

The server transmit the keyname to the viewer so the viewer know wath key he need to use.
When a server has multiple keys in his folder, he gonna use the first he find.

A viewer can have multiple keys, a server only one. That's how it's implemented.
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5909
Joined: 2004-04-23 10:21

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Skyfighter » 2019-04-21 07:36

Ok, working as intended. Thank you very much for the clarification, Rudi!
Unfortunately, this prevents my plan from using user(group)-related keys... :(
Skyfighter
40
40
 
Posts: 105
Joined: 2014-12-31 22:10

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby WKjun » 2019-05-02 10:46

Hello!

I have discovered a small glitch in the Viewer which I cannot recall to be present in the previous release.
It is about the "profiles" (LAN, ULTRA, SLOW, ...) and its corresponding options checkboxes in the background. If a profile is selected, a checkbox may be checked or unchecked accordingly. Some however do not come back ever again after beeing unchecked while others do.

Examples from a fresh install without an old options.vnc.

LAN (equals Auto) -> ULTRA -> back to LAN

[v] Use CopyRect encoding
[ ] Use Cache Encoding
[v] Zip/Tight Compression: 6
[v] Jpeg (Tight) - Quality: 6
[ ] Preemtive Updates

[ ] Use CopyRect encoding
[ ] Use Cache Encoding
[v] Zip/Tight Compression: 6
[v] Jpeg (Tight) - Quality: 6
[ ] Preemtive Updates

[ ] Use CopyRect encoding
[ ] Use Cache Encoding
[v] Zip/Tight Compression: 6
[v] Jpeg (Tight) - Quality: 6
[ ] Preemtive Updates


LAN (equals Auto) -> SLOW -> back to LAN

[v] Use CopyRect encoding
[ ] Use Cache Encoding
[v] Zip/Tight Compression: 6
[v] Jpeg (Tight) - Quality: 6
[ ] Preemtive Updates

[v] Use CopyRect encoding
[v] Use Cache Encoding
[v] Zip/Tight Compression: 6
[ ] Jpeg (Tight) - Quality: 6
[ ] Preemtive Updates

[v] Use CopyRect encoding
[ ] Use Cache Encoding
[v] Zip/Tight Compression: 6
[ ] Jpeg (Tight) - Quality: 6
[ ] Preemtive Updates


One more:

Within connection options, where Format and Encoding is being set, options described above do not change at all - which I can understand, as here is all manual - Zlib (+xor) however checks Use Cache Encoding, while none of the other options unckeck it.

I hope this helps clearing it up.
WKjun
 
Posts: 3
Joined: 2019-03-03 10:45
Location: Austria

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Nanobot » 2019-06-05 15:47

Hi Rudi,

are the IPv6 patched binaries fpr the "1224b" version are already available ?

Sorry if this results in a double post, I can't find my first post I just wrote about this question.

Thx in adavance, Nanobot
Nanobot
 
Posts: 7
Joined: 2019-03-06 20:44


Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Nanobot » 2019-06-06 19:07

2019-03-30 18:31
Rudi De Vos wrote:Files are updated 1224b
*keyboard patch disabled, enable using [v] international keys
Some keys behave bad with the patch
*ddengine fix for multimonitors on same video card

2019-04-01 16:06
Craig87 wrote:Do I need an updated exe for IPv6?

2019-04-04 23:02
Rudi De Vos wrote:I will run a ipv6 this weekend.
Current trying to fix a flash issue with the ddengine and remote cursor.


Thanks for your answer, but the archiv you pointed me to seems to contain the ipv6 binaries for the "a" version, not for the "b" version. They are dated to be changed at 2019-03-20, while you published the "b" version on 2019-03-30. The reason why I am asking is that IPv6 with the "b" version and the patched binaries does not work at all. Instead, a connection attempt results in the following error message:

Code: Select all
"Connection failed - End of stream"
Possible causes:
- Another user is already listening on this ID
- Bad connection"


To clarify that (all tests with IPv6 patched binaries):

viewer 1212 -> server 1212 IPv4 and IPv6 ok
viewer 1212 -> server 1224b IPv4 ok, IPv6 error
viewer 1224b -> server 1212 IPv4 and IPv6 ok
viewer 1224b -> server 1224b IPv4 ok, IPv6 error

That makes me think that the IPv6 enabled binaries in the archive you pointed me to are not compatible with the "b" version and needs to be replaced by new compiled versions from the "b" source code. One more suggestion: Shouldn't there be a patched version of uvnc_settings.exe which allows it to enable IPv6 by setting a checkmark, like in the admin properties of winvnc.exe ?

Thx again and keep up the good work.

C.U. Nanobot
Nanobot
 
Posts: 7
Joined: 2019-03-06 20:44

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Rudi De Vos » 2019-06-06 21:42

Then i need to rebuild the bins, will be for the weekend
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5909
Joined: 2004-04-23 10:21

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Nanobot » 2019-06-06 21:46

No problem, it's not urgent on my side, and thanks
Nanobot
 
Posts: 7
Joined: 2019-03-06 20:44

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Nanobot » 2019-07-10 20:44

Sorry for bothering you, Rudi, but I think you forgot to recompile the IPv6 enabled binaries ? :wink:

I am asking for them because here in Germany, the cable companies mostly provide access to the internet using ds-lite. And therefore it is very helpful to have an actual and working UVNC version with IPv6 enabled at hand, because without IPv6, it is not possible to offer assistance to those people using UVNC.

C.U. Nanobot
Nanobot
 
Posts: 7
Joined: 2019-03-06 20:44

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Rudi De Vos » 2019-07-14 15:42

Code was broken while adding new stuff... reverted back to build ipv6
32 and 64 server + viewer
http://www.uvnc.eu/download/1225/ipv6.zip
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5909
Joined: 2004-04-23 10:21

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Nanobot » 2019-07-14 21:50

Hi Rudi,

thx for the new version, but unfortunately the new ipv6 binary does not solve the problem:

Image
Image Image

As before, IPv4 connections work without any problems. I am on Windows10 Pro 64bit 1903 Build 18362.239 on both machines.
Nanobot
 
Posts: 7
Joined: 2019-03-06 20:44

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Rudi De Vos » 2019-07-15 20:27

Updated, new server (15/07), viewer was ok.
Rudi De Vos
Admin & Developer
Admin & Developer
 
Posts: 5909
Joined: 2004-04-23 10:21

Re: 1.2.24 Release ( web release for 15/03/2019)

Postby Nanobot » 2019-07-15 23:00

I can happily confirm that IPv6 now, at least locally tested in my LAN, works correct again. I will do a real world test over the internet tomorrow.

Many thx for your effort :thumbs:

The real world test over the internet also showed that Ipv6 connections do work again.
Nanobot
 
Posts: 7
Joined: 2019-03-06 20:44

Previous

Return to 1.2.2.x

Who is online

Users browsing this forum: No registered users and 1 guest