switch default conn from smbv1 to smbv3

[mpgn]

Description

As we all know, making connections with SMBv1 often causes errors like "connection reset by peer" or "broken pipe." This is why the --no-smbv1 flag was added by @XiaoliChan

Currently, the reason SMBv1 is checked in the first place is to determine the host info line smbv1: True/False. This is the only reason. However, if a connection with SMBv1 is successful, it will be used for all subsequent operations on the host (self.conn)

The idea: Why not use SMBv3 by default (and then fall back to SMBv1 if SMBv3 fails, essentially doing the opposite of what is done today) and perform a simple check for smbv1: True/False on the host without relying on self.conn (an independent check)

This approach would make Netexec much more reliable i think 💪

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

Against goad lab

Screenshots (if appropriate):

Checklist:

• I have ran Ruff against my changes (via poetry: poetry run python -m ruff check . --preview, use --fix to automatically fix what it can)
• My code follows the style guidelines of this project (should be covered by Ruff above)
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas

[XiaoliChan]

This logic is much make sense! When SMBv3 failed, then fallback to SMBv1

[NeffIsBack]

LGTM 👍

[XiaoliChan]

Don't forget test with server 2003

[NeffIsBack]

Don't forget test with server 2003

Why? It can communicate over SMBv3 or not?

[XiaoliChan]

Why? It can communicate over SMBv3 or not?

Server 2003 is not support SMBv3, that is why I ask need to test with server 2003 XD, BTW I will test it TMR