Sophos can't pass login disclaimer Netmiko

[jhonrobh]

I am using netmiko to log in into a Sophos device and run some commands, but the Connection handler get stock on the login disclaimer waiting for the confirmation (y/n). Log shows error:

Pattern not detected: 'Main Menu' in output.

It is waiting for a Main menu, but banner is still there, waiting to confirmed, need to send 'y' in to connechandler.

Just running this code

try:
print("Connecting to Sophos XG Firewall...")
SSH = ConnectHandler(**device)

print("done")

except Exception as e:
print(f"error: {e}")

[ktbyers]

Which version of Netmiko are you using?

[ktbyers]

Can you show me what it looks like when you manually SSH to the device? Want to see the entire login disclaimer and menu.

Note, I messed up the GitHub issue history here...as I asked something that was irrelevant and accidentally deleted your earlier response.

[jhonrobh]

This the banner after log in wit user and password

Unauthorized access or violations of security regulations is unlawful and hence if monitoring reveals either, appropriate disciplinary action will be taken against the persons violating security regulations or making unauthorized use of this system.

    Are you sure you want to Continue (y/n):

Wait for confirmation and this is when connect handler got stock because is waiting for the menu

Main Menu

1.  Network  Configuration
2.  System   Configuration
3.  Route    Configuration
4.  Device Console
5.  Device Management
6.  VPN Management
7.  Shutdown/Reboot Device
0.  Exit

Select Menu Number [0-7]:

[ktbyers]

@jhonrobh Okay, so this is something your organization has configured--correct?

Unauthorized access or violations of security regulations is unlawful and hence if monitoring reveals either, appropriate disciplinary action will be taken against the persons violating security regulations or making unauthorized use of this system.

    Are you sure you want to Continue (y/n):

[jhonrobh]

Yes, We configured the login disclaimer

[ktbyers]

Easy fix is to see if you can get rid of the banner or the prompting.

Second fix is perhaps someone can implement some form of generic code we can enable if this type of handler is needed.

Third fix is someone can implement a specific handler for this Sophos message (there are other platforms that have this).

The second fix would be better so we don't have to reimplement a new solution every time someone enables a prompt like this on a given network operating system.