Wouldn't it be nice, when a file 'knows' its best own security setting?
And what about retrieving and activating the files persistent security
settings?

All GreenHouse developed executables (code 100 and 700) do know their
best security setting as of 08Sep1999.

The following security relevant flags are known:

• ProgID
• Clear-on-Purge
• Licensed
• REWP Guardian security string
• owner

The persistent settings are part of the executable. They are stored in
form of entry points. These entry points have to be compiled into the
program.

A typical persistent security procedure looks like this:
!
! Persistent Security Settings
! by GreenHouse Software & Consulting
!
Proc PersistentSecurity;
------------------------

Begin

Entry PerSecOwner_SUPER_SUPER;
Entry PerSecProgID_OFF;
Entry PerSecClearonPurge_OFF;
Entry PerSecLicense_OFF;
Entry PerSecSecurity_OONO;

PerSecOwner_SUPER_SUPER:
PerSecProgID_OFF:
PerSecClearonPurge_OFF:
PerSecLicense_OFF:
PerSecSecurity_OONO:

End;

The PerSec program can
- display the persistent security setting
- compare the actual file settings with the persistent ones
- activate the persistent security setting
(for security reasons, only SUPER.SUPER can activate the persistent
settings)