Subject ibsecure.exe / ibsecure barf on empty -d parameter
Author Jeroen Pluimers
Ann pointed me to the -d parameter.

It seems that when you specify -d, but no path after it, then
ibsecure.exe and ibsecure will crash.

On W2K Server SP1, ibsecure.exe produces an access violation.

On RedHat 6.1, ibsecure produces a core dump.