Not quite; someone who has been granted access to a file on a filesystem can transmit a copy to someone who hasn't. If the access control list is part of the filesystem, an unauthorised user can access the file's contents once they have a copy.
Thought I'd post this because quite a few people I've talked to recently aren't aware of the "Mixed DLL Loading Problem" that affects anyone mixing native and.NET code in the same DLL (ie. linking objects compiled with and without -clr). This MSDN article describes a problem where:
"...due to the way the loader works in version 1.0 and 1.1 of the common language runtime, deadlock situations are always possible with mixed DLLs..."
The problem exists in versions 1.0 and 1.1 of the.NET runtime (1.1 being the current production release).
I was always told cracking was "criminal hacking"... kinda rolls off the tongue even if it isn't true.
Where there's a will, there's a way!
Not quite; someone who has been granted access to a file on a filesystem can transmit a copy to someone who hasn't. If the access control list is part of the filesystem, an unauthorised user can access the file's contents once they have a copy.