07-12-2005, 04:17 PM
A macro is vulnerable if it passes a password to an user defined function or dll function, even if all is encrypted. Somebody that is able to edit your macros can delete the function that is called and replace it to a compatible function (same name, same arguments) that simply shows passed arguments. Of course, if only he knows or can guess what functions are called by your encrypted macro. And, only if he can run that macro.
A macro containing a password also is vulnerable if it for example pastes that password.
To make a macro containing passwords really secure:
1. Encrypt it.
2. If it passes the password to other functions (except QM intrinsic functions) or somehow outputs it (eg pastes), it also must ask for password to run it. To ask for password, use inpp. It is secure.
A macro containing a password also is vulnerable if it for example pastes that password.
To make a macro containing passwords really secure:
1. Encrypt it.
2. If it passes the password to other functions (except QM intrinsic functions) or somehow outputs it (eg pastes), it also must ask for password to run it. To ask for password, use inpp. It is secure.