2.0.4.0
- Fix typo's
- Updated library
Download
https://mega.nz/#!9xdWFI7S!pCBxUzTg0NoqJ...dZ3RRNBxxQ
Password: 64ujeharswb\daz11234we5stkrlfg
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
(Oct 31, 2019, 04:58 am)Arlecho Wrote: [ -> ]2.0.4.0
- Fix typo's
- Updated library
Download
https://mega.nz/#!9xdWFI7S!pCBxUzTg0NoqJ...dZ3RRNBxxQ
Password: 64ujeharswb\daz11234we5stkrlfg
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
I have loaded the latest current version ScreenConnect 19.4.25759.7247 for Linux moved it over to Windows to patch it then move it back to Linux, but I either receive an error about License file has been altered or it goes through good but cannot log in after following the steps from the patcher. Any advise would be helpful.
Please ensure everyone is running at the latest 19.4.25759.7247 release, servers appear to be getting hacked and there have been a few point releases from connectwise, I'm willing to bet they've fixed it but not made it public.
Also the latest release mentions "WebClient requests fail due to unsupported feature on Mono server" on the changelog.
Edit: 19.5 beta seems to work just fine.
I'm observing a bit of odd behavior. I ran the installer for 19.4.25759.7247 on a patched 19.3.25270.7185 Linux server. I copied the files to a Windows machine, ran the patcher (tried with 2.0.3.0 and 2.0.4.0), and got a message that said files were missing. The unpatched 19.4 install still allows me to log in, but I'm hesitant to let it out yet. Is there a way to tell what files the patcher expects but doesn't see?
EDIT: Upgraded my Linux server to 19.5.25838. Downloaded and patched ScreenConnect_19.5.25838.7256_Debug.msi, installed on my windows machine, copied the files from my Linux install over the the files in C:\Program Files (X86)\ScreenConnect, ran the 2.0.4.0 patcher. Compared the files and saw that ScreenConnect.Server.dll and ScreenConnect.Service.exe were modified. Copied those files back to my Linux server. Old clients are reconnecting and upgrading fine (Linux and Windows).
Minor nitpick: Is anyone aware of an issue with changing settings in Admin > Configuration wherein everything under the headings "Disable Host Client Menu Items" and "Application Configuration" returns "Object reference not set to an instance of an object"? This functionality is provided by a ConnectWise plugin, so I understand if it doesn't work on a patched system.
I've done some light searching on the forum and on the web but can't find a way to download the older version of those extensions. Am I missing something obvious?
SC http to https redirect,
yeah I'll need to open 443 on my iptables.
may be an old subject to some, but I'll get to it eventually
tried to move my DNS to Cloudflare and my http site would not resolve as only https will work on CF.
so many choices
I have the pdf instructions direct from SC and their linux-ssh_cert_script. Don't know if that will messup my
Arlecho licensed SC version.
I also have these links...
https://github.com/stylnchris/sc_ssl_support
and
https://mangolassi.it/topic/20126/config...ts-encrypt
and
https://tylermade.net/2017/05/04/easy-ss...rse-proxy/
So who has done the redirect and which one is recommended (are there more?) for a debian9-sys running an Arlecho SC version from Jan 2017?
All insights welcome.
Best wishes to all for this Holiday season!
Their ssl script should not mess up this patch, but personally I prefer a reverse proxy via iis/apache/nginx or the likes.
2.0.5.0
- Fix compatibility with latest 19.5 beta
Download
https://mega.nz/#!V5EnnKyJ!to7m7YTf_9iib...7le04uvNTQ
5jrysteznbdsfwq34q2y3u54jtdnmgf
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
I have a really stupid question... I cannot find what the password is set to once the patcher is ran.
Everything works fine but I could not sign into the windows version
(Dec 01, 2019, 20:15 pm)cypheredout Wrote: [ -> ]I have a really stupid question... I cannot find what the password is set to once the patcher is ran.
Everything works fine but I could not sign into the windows version
It either preserves the existing user(s) or creates a default, there is a popup message AND a log line when that happens (which would be only the first time as the next run would preserve the previously generated account).