Arlecho's ScreenConnect 6 releases

[Arlecho]

Thanks, to any others please report back, even if you don't encounter any issues.

[Mr_sjappie]

Thanks, to any others please report back, even if you don't encounter any issues.

No problems here.

Going to test more.. but seems to be working.

Version 22.2.7029.8094

And let's hope for peace in the world!

[justsomeguy1234]

22.2.7029.8094 with patch 3.0.0 ALPHA2

So far seems to be working fine. Was able to update a couple extensions as well.

Will let you know if I run into any issues.

[fellow26]

Is there a way to use HTTPS? I have several WS that have been hacked by ransomware. I suspect they came in via Screenconnect. At least can I change the ports from 8040 8041 to something else and auto update on all the clients ?

[Arlecho]

Use an IIS proxy with certificate (do *NOT* use the "Use custom certificate" option in the patcher) to gain https.

Changing the relay ports will cause all clients to become unreachable.

Please do a thorough investigation into the infections, if it truly was through screenconnect (which https isn't going to fix most probably, that would have required a MITM attack) we need to raise some concern with the devs.

---

Changelog v3.0.0:

- Full v22.x.x support
- Less files needed
- Updated libraries
- Removed certificate patcher

Download
https://mega.nz/file/F0FXzSyA#Mb50HqdciK...5W5Epy57Zo
FckPtn

Notices, please read carefully
- Patch the installer before installing to prevent leaking your information!
- Linux can be patched, just copy the files over to a windows machine and select the directory!
- "External Accessibility Check", "Version Check" and "Browser URL Check" will now always fail!
- Installing/updating extensions could theoretically be spotted by Connectwise as they are downloaded directly from their servers!
- License no longer displays (not required for patch to function)
- Please do not post thanks and other posts that do not contribute (the mods don't like them and it clutters the thread)
- Hosts file editing no longer required as the uri's are patched out of the appropriate files

[justsomeguy1234]

After a few days all is still good.

Are there any important changes between 3.0.0 ALPHA2 and v3.0.0 that you'd recommend re-patching for if things seem to be working fine?

Thanks for your work!

[Arlecho]

Repatching shouldn't make a noticeable difference.

[justsomeguy1234]

Just updated to 22.2.7244.8111 that was released on the 17th and used the new 3.0 patcher and it is working well.

One question though. Do you know why the patcher would be making a connection to 72.21.91.29. it seems to happen at step 3 in the patcher. I noticed it because my firewall blocked it.

[Arlecho]

Did you mean during the actual ScreenConnect installer phase? If so did your firewall notice which executable is calling?

[Sinauth]

Just updated to 22.2.7244.8111 that was released on the 17th and used the new 3.0 patcher and it is working well.

One question though. Do you know why the patcher would be making a connection to 72.21.91.29. it seems to happen at step 3 in the patcher. I noticed it because my firewall blocked it.

Is your ISP Verizon by any chance?

If so, it would just be Verizon's TLS certificate system.