handle seeing current priv again after trying to escalate auth #234
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
dont timeout when devices are not ready to escalate auth. cropped up in scrapligo/boxen when connecting to device that just fired up -- sending "enable" caused the device to say something like "cant do that yet, not ready" and kicked back to the exec prompt. scrapligo died at that point as it was looking for either the password prompt or the privilege exec prompt. this fixes that to also accept seeing the exec (or w/e the current prompt is) prompt one more time. this is fine because before moving on we validate the current prompt/priv level is what we want (before breaking out of the escalate auth loop).