Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fortra/impacket v. Pennyw0rth/impacket Conflict Resolution #205

Closed
Arszilla opened this issue Mar 14, 2024 · 1 comment
Closed

Fortra/impacket v. Pennyw0rth/impacket Conflict Resolution #205

Arszilla opened this issue Mar 14, 2024 · 1 comment
Labels
dependencies Pull requests that update a dependency file

Comments

@Arszilla
Copy link

Arszilla commented Mar 14, 2024

As discussed in Discord, I am opening this issue to track progress and solve this issue.

Since Fortra’s impacket Debian package (python3-impacket) is maintained by Debian's Debian Python Team and is a reverse dependency for various penetration testing tools, including the libraries used by netexec, the creation of another impacket package (of Pennyw0rth/impacket) on Kali’s side (with a different package name (python3-impacket-nxc), and potentially with Replaces or Conflicts headers) is not a possibility. Thus, thwarting netexec's packaging on Kali side.

As a result; a potential solution is that Pennyw0rth/impacket may need a name change, resulting in a different namespace for the library, other than impacket. This means both the Pennyw0rth/impacket repo and Pennyw0rth/netexec will require an update to reflect the change in dependency name.

@NeffIsBack NeffIsBack added the dependencies Pull requests that update a dependency file label Mar 21, 2024
@NeffIsBack
Copy link
Contributor

As we swapped back to fortra/impacket with #234 i will close this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

No branches or pull requests

2 participants