Non-strict privileged level #303
Unanswered
denisbondar
asked this question in
Q&A
Replies: 1 comment 1 reply
-
I think you can just use the “generic driver” with a custom “on open” function to do whatever setup steps you have. If you login to the device and then decide it should be in “privileged” mode (meaning you actually want the “network driver”), you can use the “commandeer” function to basically change from the network drive to generic (you could do this in reverse too of course). Hopefully that makes sense! Am on mobile at the moment but I believe there is a commandeer example and for the custom in open it’s just a callable that accepts the cls/self if the driver as first and only arg— so you can do whatever ya need to with that. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
There are some devices on my network that have privileged mode enabled by default, and after logging on to these devices there is no need to enter the enable command because we are already in this mode.
There are other devices where we get the unprivileged mode by default after logging on and we need to enter the
enable
command to switch to this mode.There are commands that are available in either of these modes and can be executed in both unprivileged and privileged modes in the same way.
However, it is not entirely clear how to configure the driver. If you set
privilege_exec
todefault_desired_privilege_level
, it will always try to go to privileged mode, and if you setexec
, it will always try to go back to unprivileged mode.My question is:
Is there any way to use the default unprivileged mode so that if the default device provides privileged mode, Scraply will not try to switch to unprivileged mode by passing disable or other command specified in deescalate?
Beta Was this translation helpful? Give feedback.
All reactions