Author Topic: How do the "OverrideSecurityFilename" parameter work?  (Read 1394 times)

0 Members and 1 Guest are viewing this topic.

Offline AnrDaemonTopic starter

From the parameter description,
;OverrideSecurityFilename
;System admins may find it desirable to install settings without prompting
;the user. In that case all prompts and security will be overridden if
;the name of the ini matches the name given here.
;If this is used, make sure it's suitably random and hence not likely
;to be downloaded.
;Default is empty (no override possible)
it seems, the parameter should let me tweak every new install of Miranda without the need of manual actions from a user.
But as it seems, it just doesn't work at all.
When I set it to "suitable random" name, the relevant files just don't get executed.
When I set it to default "autoexec_forced_*.ini", it gets picked by the "Glob=autoexec_*.ini" and floods screen with requests for changing the settings.

Miranda .95.5-dev.
 

Offline AnrDaemonTopic starter

Re: How do the "OverrideSecurityFilename" parameter work?
« Reply #1 on: 28 06 2015, 13:17:46 »
Anyone?
 

Offline AnrDaemonTopic starter

Re: How do the "OverrideSecurityFilename" parameter work?
« Reply #2 on: 03 07 2015, 05:12:20 »
No? 
 

Offline Robyer

Re: How do the "OverrideSecurityFilename" parameter work?
« Reply #3 on: 03 07 2015, 20:48:07 »
AnrDaemon, maybe try to ask ghazan directly in Jabber conference, I'm not sure whether he reads this topic.
I was developing mainly Facebook, Omegle, Steam, Dummy and MobileState plugins. Now I'm retired. Goodbye, everyone. ~ You can still find me on Facebook.