#168 closed Feature Request (Rejected)
RunAsSet() for 3.2.11.x
| Reported by: | JayMan | Owned by: | |
|---|---|---|---|
| Milestone: | Component: | AutoIt | |
| Version: | Severity: | ||
| Keywords: | RunAs RunAsSet RunAsWait 3.2.11.1 | Cc: |
Description
Is it possible to leave the RunAsSet() function in 3.2.11.x?
I understand this was replaced with RunAs() & RunAsWait(), but i really prefer the functionality of the RunAsSet() command, as it means i don't have to specify the username & password multiple times in the script.
Surely its possible to have all 3 commands available?
Attachments (0)
Change History (3)
comment:1 by , 18 years ago
| Version: | 3.2.11.1 |
|---|
follow-up: 3 comment:2 by , 18 years ago
| Resolution: | → Rejected |
|---|---|
| Status: | new → closed |
RunAsSet() is a security risk that we do not need. The RunAs() and RunAsWait() functions are superior in syntax, functionality and security (although they are still not 100% secure, they are at least now more secure than RunAsSet()).
comment:3 by , 18 years ago
I'm not sure how its any more of a security risk to be honest...
Sure if people don't code the script right, if they want only a section runas'd and they forget to do a RunAsSet() it'll continue with the elevated user instead...
If thats the only risk involved, rather than remove it completely, why not make it a function that requires a end to pass syntax checks (e.g. require 'RunAsEnd' or something to be present)
Ofcourse, I might be overlooking/unaware another security issue with this...
Automatic ticket cleanup.