|
-
May 3rd, 2001, 11:20 AM
#1
Thread Starter
Lively Member
Std Modules a security risk?
Hiya,
I've heard that having standard modules in a VB ActiveX COM DLL is a security risk? The DLL's should only contain class modules?
Is this true? If so why???
Cheers!
Gaurav
[email protected]
" Programming today is a race between software-engineers striving to build bigger and
better idiot-proof programs and the universe trying to produce bigger and better idiots.
So far the universe is winning". :-)
-
May 3rd, 2001, 02:17 PM
#2
Addicted Member
nah,
i think standard modules are fine... i mean how would you share for instance a global variable between 2 classes in the same DLL?
you need a standard module for that...
regards,
shizo
-
May 3rd, 2001, 02:31 PM
#3
Black Cat
I've heard that having standard modules in a VB ActiveX COM DLL is a security risk? The DLL's should only contain class modules?
Does this have anything to do with hackers being able to inject code into the memory space of a dll loaded into memory?
Josh
Get these: Mozilla Opera OpenBSD
I have books for sale: "MCSD in a Nutshell" and "VB Distributed Exam Cram" - PM me for details. Will also trade for a decent ATX Pentium 2 MB/CPU/RAM combo.
-
May 3rd, 2001, 02:59 PM
#4
Thread Starter
Lively Member
Originally posted by ShIzO
nah,
i think standard modules are fine... i mean how would you share for instance a global variable between 2 classes in the same DLL?
you need a standard module for that...
regards,
shizo
How about via a public property of an implemented class???
[email protected]
" Programming today is a race between software-engineers striving to build bigger and
better idiot-proof programs and the universe trying to produce bigger and better idiots.
So far the universe is winning". :-)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|