BUG: Always prompted for password

[Prisma]

viewer/server 1.0.9.6.1 with repeater 2.0 mode II
1. If you establish a reverse connection the viewer always asks for a password. Earlier versions of ultraVNC never asked.
2. You are prompted for password even if "AuthRequired=0" and "SocketConnect=0"

The only way to be not prompted for password is to NEVER set a password or delete *[ultravnc] passwd/passw2* and set AuthRequired=0.
That's bad.

[B]

This came up recently and Rudi answered (you could search on his recent posts).

I believe the change was intentional.

[Prisma]

And what to search for? If I search for "password" nothing is found. Would you please be more explicit?

[B]

Sorry, no. You're asking that I do the search for you. The user name is Rudi de Vos. He doesn't post that frequently so it shouldn't be too hard to find.

But again, as far as I recall, the new requirement for authenticated reverse connections was intentional.

[Prisma]

Thank you, I know who Rudi is.

Strange sound man, sorry for my suggestions. Possibly it is better better to switch of my brain and let the things happen...
We not yet communicated with each other, did we? Otherwise you'd know I wouldn't post it as a bug, if it would make sense for me and appear consistent. But it doesn't make sense:

If it is intended, ultraVNC should react on AuthRequired=0 within a reverse connection. Otherwise you could have the situation, that you are able to connect forward without password, and if you connect backward (what is saver per se) you're prompted for a password. This makes ABSOLUTELY no sense, does it?

[B]

Here's the second Google hit; I think he explained it more in another thread though.

https://forum.ultravnc.net/viewtopic.php?f=29&t=28319

[Prisma]

I never talked about encryption and SecureVNC. That's what the post is about. In my test environment NO encryption is enabled.

(And even if: I have to use rc4, because I introduced encryption at my customers with rc4. We got over 500 customers with thousands of installations and several support centres, I can't roll out a new encryption method that easy)

[B]

Sorry I'm not giving this as much time as I otherwise might; I'm just very busy at the moment. Anyway, I found a couple of other threads that might (or might not) be relevant.

https://forum.ultravnc.net/viewtopic.php?f=10&t=27414

https://forum.ultravnc.net/viewtopic.ph ... 701#p86701

[Prisma]

First, thank you for your efforts. The links are both related to my bug report. But I think they are explaining different situations, and from my point of view, in this cases winvnc is operating consistent and /or as needed.
I'll do some tests, and get back to you...