Re: If It Ain't Broke, Don't Fix It, Or Why I've Chosen to Lern VB6
My last job before I lost my vision was as a senior software engineer for the popular Armadillo software protection and licensing system, you'd call it DRM. We were constantly dealing with hackers trying any kind of exploit they could to break our protection, part of trying to prevent their exploits from working was doing what ever we could to make sure that Armadillo was as secure as we could make it.
Certainly, an old language like VB6 has vulnerabilities that will never be fixed. A skilled developer might be able to write code to minimize the risk of writing in such an old language, but a beginner never will.
Any program that is installed on a computer can be executed, and if that program is vulnerable, while it is running, the system it is running on could be rendered equally vulnerable.
Given the choice, I'd prefer not to run any program written in VB6 or any other old and no longer supported system. But that is unrealistic, so the first thing I do is examine an executable to try to determine what it is written in, and sandbox those programs I want to run that are written in old languages like VB6.
Better safe than sorry.
@Aprone
You are, of course, entitled to your opinion, but I take exception to having someone like you assault my opinions by calling them fiction. Especially when you know almost nothing about me and my experience and what I might or might not know.
For that reason I will no longer participate in this particular discussion.
_______________________________________________ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
