Certain Windows configurations can cause an infinite recursion #5
Comments
|
Actually I think this might happen regardless of UAC for me. On the other hand, my Windows 7 is screwed up and customised to the point where it might be the problem (although I wouldn't think with a separate new user account...) |
catb0t
added a commit
to catb0t/elevate
that referenced
this issue
Jun 18, 2019
- close barneygale#3: relative path expansion - **temporarily** fix barneygale#5 for windows - documentation is added to the workarounds in elevate_util This implementation uses an import hook, which may not be the cleanest solution possible. The import hook fixes argparse and similar modules seeing and complaining about --_with-elevate-* options, if the argument parser is called before the re-entrant call to elevate().
catb0t
added a commit
to catb0t/elevate
that referenced
this issue
Jun 18, 2019
- close barneygale#3: relative path expansion - **temporarily** fix barneygale#5 for windows - documentation is added to the workarounds in elevate_util This implementation uses an import hook, which may not be the cleanest solution possible. The import hook fixes argparse and similar modules seeing and complaining about --_with-elevate-* options, if the argument parser is called before the re-entrant call to elevate().
barneygale
added a commit
that referenced
this issue
Jun 18, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
when UAC is disabled (no asking passwords) but the account isn't an administrator, then windows.elevate recurses forever (as
isUserAnAdmin()is never true and the function never crashes) and eventually eats up all the RAM spawning new processes.Next I'll write the more permanent fix but i'm using a shim one in the path-resolving branch for now.
The text was updated successfully, but these errors were encountered: