Reply to thread

Message

<blockquote data-quote="Libera Milanesi" data-source="post: 758629" data-attributes="member: 74385">I&#039;m aware of what vulnerable processes are and as for the encryption, its functionality in cipher.exe and using cmd.exe to use the functionality isn&#039;t mandatory.I wasn&#039;t referring to vulnerable processes earlier on. It doesn&#039;t matter as to what I was referring to, it&#039;ll just introduce paranoia discussions and cause tons of misunderstanding. Forget about anything I said outside of my post edit.The .NET Framework is filled with tons of security holes and worst of all, a lot of software engineers decide to use older versions for compatibility reasons (e.g. default versions pre-installed on Windows 7 or other versions of Windows) which leaves them even more vulnerable for using an outdated version. 99% of the .NET community isn&#039;t going to understand security... and the .NET Framework was never designed to be secure in the first place as far as I am concerned (and if it was, that&#039;s even more embarrassing).The .NET Framework can be useful for some things but I do not think this outweighs the cons.Each to their own though. I myself agree with you and I know a lot of my colleagues would also.</blockquote>

[QUOTE="Libera Milanesi, post: 758629, member: 74385"] I'm aware of what vulnerable processes are and as for the encryption, its functionality in cipher.exe and using cmd.exe to use the functionality isn't mandatory. I wasn't referring to vulnerable processes earlier on. It doesn't matter as to what I was referring to, it'll just introduce paranoia discussions and cause tons of misunderstanding. Forget about anything I said outside of my post edit. The .NET Framework is filled with tons of security holes and worst of all, a lot of software engineers decide to use older versions for compatibility reasons (e.g. default versions pre-installed on Windows 7 or other versions of Windows) which leaves them even more vulnerable for using an outdated version. 99% of the .NET community isn't going to understand security... and the .NET Framework was never designed to be secure in the first place as far as I am concerned (and if it was, that's even more embarrassing). The .NET Framework can be useful for some things but I do not think this outweighs the cons. Each to their own though. I myself agree with you and I know a lot of my colleagues would also. [/QUOTE]

Verification