4 ms·

For a use case of a new XP install, I have clients with DVR systems, with a webui that only works in IE. However, IE mode in Edge comes with 1) an unremovable

For a use case of a new XP install, I have clients with DVR systems, with a webui that only works in IE. However, IE mode in Edge comes with 1) an unremovable banner warning you to stop using IE mode and 2) an automatic 6 month expiration of sites you put in the IE Mode whitelist (supposedly overrulable by a GPO - but it's commonly broken). It turned out to be less trouble to spin up an XP VM and make IE available to network users as a Remote App.

scq 3y ago
There are still ways to use the IE engine on current Windows, aside from Edge's IE mode. Namely, there's the WebBrowser ActiveX control, which uses the IE engine on all Windows versions. Easily embeddable in a .NET app: https://learn.microsoft.com/en-us/dotnet/desktop/winforms/controls/webbrowser-control-overview https://learn.microsoft.com/en-us/dotnet/desktop/winforms/co...
- WarOnPrivacy 3y ago
  This could be really promising but I seem to be lacking the background to grok it easily. I'll get myself edumakated.
hsbauauvhabzb 3y ago
You could drop a reverse proxy infront which rewrites the user agent, this will probably fox many of the issues. I’d be cautious about using a DVR for any sensitive situation if it’s unmaintained if the Dvr is used in sensitive scenarios. There would be a significant amount of reputational damage if it’s ever hacked, particularly if ugly workarounds are used to bypass software being totally EOL’d.
- WarOnPrivacy 3y ago
  > You could drop a reverse proxy infront which rewrites the user agent, this will probably fox many of the issues. The user agent thing makes me think you're trying to fool the DVR. The DVR requires a browser that is running it's ActiveX plugin. IE is the only browser that runs them. > I’d be cautious about using a DVR for any sensitive situation if it’s unmaintained if the Dvr is used in sensitive scenarios. External access to the DVR is limited (by the firewall) to 1 external IP address. If it were hacked, someone would have breached the firewall and the DVR would be the least of our issues.

scq 3y ago

There are still ways to use the IE engine on current Windows, aside from Edge's IE mode. Namely, there's the WebBrowser ActiveX control, which uses the IE engine on all Windows versions. Easily embeddable in a .NET app: https://learn.microsoft.com/en-us/dotnet/desktop/winforms/controls/webbrowser-control-overview https://learn.microsoft.com/en-us/dotnet/desktop/winforms/co...

WarOnPrivacy 3y ago
This could be really promising but I seem to be lacking the background to grok it easily. I'll get myself edumakated.

hsbauauvhabzb 3y ago

You could drop a reverse proxy infront which rewrites the user agent, this will probably fox many of the issues. I’d be cautious about using a DVR for any sensitive situation if it’s unmaintained if the Dvr is used in sensitive scenarios. There would be a significant amount of reputational damage if it’s ever hacked, particularly if ugly workarounds are used to bypass software being totally EOL’d.

WarOnPrivacy 3y ago
> You could drop a reverse proxy infront which rewrites the user agent, this will probably fox many of the issues. The user agent thing makes me think you're trying to fool the DVR. The DVR requires a browser that is running it's ActiveX plugin. IE is the only browser that runs them. > I’d be cautious about using a DVR for any sensitive situation if it’s unmaintained if the Dvr is used in sensitive scenarios. External access to the DVR is limited (by the firewall) to 1 external IP address. If it were hacked, someone would have breached the firewall and the DVR would be the least of our issues.