Adobe is ENDING any further support/development of its Flash Player by
the end of 2020...and most web browsers have stopped support for pages
with Flash. The main reason is that Flash has become a severe security
risk, with many hackers using it to spread malware of all kinds.
Since echicken does one of the website interfaces with Synchronet
(webv4), I was curious if this will have an effect on the page, if
folks click on "Connect Via Telnet". Also, will the port (I think 843)
need to be disabled in ones router??
I think you're referring to Rick Parrish's fTelnet web app? It hasn't
used Flash in quite a long time now (the 'f' in its name is just a legacy). It uses HTML5 and WebSockets now.
The Synchronet FlashPolicy service (flashpolicyserver.js) isn't used/needed any longer. --
Adobe is ENDING any further support/development of its Flash Player by
Since echicken does one of the website interfaces with Synchronet
(webv4), I was curious if this will have an effect on the page, if
folks click on "Connect Via Telnet". Also, will the port (I think 843) need to be disabled in ones router??
So, can the port related to it (443) be disabled??
Adobe is ENDING any further support/development of its Flash Player
by
Since echicken does one of the website interfaces with Synchronet
(webv4), I was curious if this will have an effect on the page, if
This should have no impact on webv4. fTelnet uses modern web technologies to achieve the connection. (This is the role of the WebSocket service, which you may have one or two entries for (secure and insecure) in services.ini.)
There's a "Flash Socket Policy" service and I think it does listen on
port 843. You might as well disable the service and remove any port forwarding rules in your router - unless for some reason you want to continue supporting Flash clients.
So, can the port related to it (443) be disabled??
You can disable your rule(s) for port 843.
Port 443 on the other hand is for HTTPS, and you probably want to keep that.
port forwarding rules in your router - unless for some reason you
want to continue supporting Flash clients.
I've already done that...it's just too much of a risk.
On 11-03-20 06:26, Daryl Stout wrote to echicken <=-
There's a "Flash Socket Policy" service and I think it does listen on
port 843. You might as well disable the service and remove any port forwarding rules in your router - unless for some reason you want to continue supporting Flash clients.
I've already done that...it's just too much of a risk.
On 11-04-20 00:26, echicken wrote to Daryl Stout <=-
A risk to users who continue to use Flash in their browsers, but not so much for you on the server side. This is more a matter of tidying up.
port forwarding rules in your router - unless for some reason you
want to continue supporting Flash clients.
I've already done that...it's just too much of a risk.
A risk to users who continue to use Flash in their browsers, but not so much for you on the server side. This is more a matter of tidying up.
Tony Langdon wrote to echicken <=-
Adobe is currently warning users with Flash installed that support ends
on Dec 31, and recommending that it be uninstalled. Which I've done.
Tony Langdon wrote to echicken <=-
Adobe is currently warning users with Flash installed that support
ends on Dec 31, and recommending that it be uninstalled. Which I've
done.
I worked at Macromedia from 1995-1998, and the company bought a
little company out of San Diego for a package called FutureSplash. I
think they paid something like a million and change for it.
Hired the engineers, changed the name to Flash, and had a pretty good
run with it.
On 11-04-20 09:33, poindexter FORTRAN wrote to Tony Langdon <=-
I worked at Macromedia from 1995-1998, and the company bought a
little company out of San Diego for a package called FutureSplash. I
think they paid something like a million and change for it.
Hired the engineers, changed the name to Flash, and had a pretty good
run with it.
| Sysop: | Gate Keeper |
|---|---|
| Location: | Shelby, NC |
| Users: | 719 |
| Nodes: | 20 (0 / 20) |
| Uptime: | 79:36:31 |
| Calls: | 9,210 |
| Calls today: | 9 |
| Files: | 5,288 |
| D/L today: |
30 files (418M bytes) |
| Messages: | 466,288 |