Fix compatibility with Python 3.13 (crypt module removal & deprecated import logic)

[Chocapikk]

This PR fixes pwncat compatibility with Python 3.13 by addressing five key issues:

---

Fixes included

Module replacement

• Removed use of deprecated crypt module (dropped in Python 3.13)
• Replaced with passlib.hash.sha512_crypt for hashing /etc/passwd entries
  → Updated in:
  • modules/linux/enumerate/escalate/append_passwd.py
  • modules/linux/implant/passwd.py

Import system cleanup

• Replaced deprecated:

  loader.find_module(...).load_module(...)

  with:

  importlib.util.spec_from_loader(...) + exec_module(...)

  → Applied in:
  • pwncat/commands/__init__.py
  • pwncat/manager.py

CVE-2019-14287 detection fix

• Made the version parsing more robust using try/except with packaging.version.parse()
  → Prevents crashes on systems with distro-specific or malformed sudo versions.

Pickle serialization fix

• Fixed a bug introduced in a previous commit that broke object serialization with ZODB
  → Restores proper enumeration, persistence, and database commits.

Dependency update

• Added passlib to pyproject.toml to support the new password hashing backend.

---

Errors resolved

• ModuleNotFoundError: No module named 'crypt'
• AttributeError: 'FileFinder' object has no attribute 'find_module'
• PicklingError: Can't pickle <class ...>

---

How to install this fix immediately

If this PR is not yet merged, you can install the fixed version directly from my fork:

pipx install git+https://github.com/Chocapikk/pwncat-vl

[Yakui420]

Are you also getting an error when trying to get a shell from a windows target?

I get this:

[12:05:36] received connection from 10.10.100.15:49331         
[12:06:06] connection failed: channel receive timed out: b"Invoke-Expression : The
           term 'stty' is not recognized as the name of a cmdlet, function, script
           file, or operable \r\nprogram. Check the spelling of the name, or if a
           path was included, verify that the path is correct and try again.\r\nAt
           line:1 char:501\r\n+ ... BytesRead - 1);$Output = try {Invoke-Expression
           $Command 2>&1 | Out-S ...\r\n+
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n    + CategoryInfo          :
           ObjectNotFound: (stty:String) [Invoke-Expression],
           CommandNotFoundException\r\n    + FullyQualifiedErrorId : CommandNotFoun
           dException,Microsoft.PowerShell.Commands.InvokeExpressionCommand\r\n
           \r\n"
(local) pwncat$

[Chocapikk]

Hey @Yakui420 , I haven't looked or tested it on Windows environments. But I just think that this payload is not compatible with the env. It says that a command cannot be found, I think it's "stty" here, you will have to add an alternative payload for the interactive shell.