Page MenuHomeFeedback Tracker

Please add localNamespace (for MP security)
Closed, ResolvedPublic

Description

If you want to store variables safely on one machine/client without others being able to override it (with publicVariable) - you need to either use the uiNamespace or the parsingNamespace. Both are different to the default missionNamespace in that they persist between missions.

The ideal solution would be to add another namespace - call it "localNamespace" (or localMissionNamespace). This new namespace would be otherwise fully identical to the missionNamespace, but since it's not default - you won't be able to publicVariable/override anything in it.

Details

Legacy ID
2002144938
Severity
None
Resolution
Open
Reproducibility
N/A
Category
Scripting
Additional Information

Also, something like this should not be possible with the new local namespace:

with localNamespace do {

missionVar = "i hack you";
publicVariable "missionVar";

};

Event Timeline

simast edited Steps To Reproduce. (Show Details)May 22 2013, 1:41 PM
simast edited Additional Information. (Show Details)
simast set Category to Scripting.
simast set Reproducibility to N/A.
simast set Severity to None.
simast set Resolution to Open.
simast set Legacy ID to 2002144938.May 7 2016, 2:12 PM
eddieck added a subscriber: eddieck.May 7 2016, 2:12 PM

IMO the ideal solution would be to replace publicVariable with something that doesn't just modify global variables, but I'll go for this too. :)

Upvoted.

m1nd0 added a subscriber: m1nd0.May 7 2016, 2:12 PM
m1nd0 added a comment.May 22 2013, 2:10 PM

You got my vote.

You got my vote too !

MadDogX added a subscriber: MadDogX.May 7 2016, 2:12 PM

Mass closing ancient tickets with no activity for > 12 months; assume fixed or too trivial.

If this issue is still relevant in current dev build, please re-post.