You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been looking into packaging pwncat for Kali, as per https://bugs.kali.org/view.php?id=8522. However, During packaging, I noticed that 4 dependencies of pwncat will have to be packaged as well, one of which is paramiko-ng.
When paramiko-ng is packaged, it does not save itself under paramiko-ng space (i.e., ./usr/lib/python3/dist-packages/paramiko-ng/), but instead paramiko's space (i.e., ./usr/lib/python3/dist-packages/paramiko/).
Unless the library is "patched" (preferably by the people who forked paramiko) to account for this change, it will conflict with paramiko and the 58 packages that depend on paramiko.
As a result, it is possible for you to change paramiko-ng with paramiko to facilitate the packaging of pwncat?
TIA.
The text was updated successfully, but these errors were encountered:
I'd like to mention that the main paramiko project looks more active than paramiko-ng right now (December 2024). There were 3 paramiko releases this year while the last paramiko-ng release is from January 2022 and the last paramiko-ng happened in February 2023.
Hey there,
I've been looking into packaging
pwncat
for Kali, as per https://bugs.kali.org/view.php?id=8522. However, During packaging, I noticed that 4 dependencies ofpwncat
will have to be packaged as well, one of which isparamiko-ng
.When
paramiko-ng
is packaged, it does not save itself underparamiko-ng
space (i.e.,./usr/lib/python3/dist-packages/paramiko-ng/
), but insteadparamiko
's space (i.e.,./usr/lib/python3/dist-packages/paramiko/
).Unless the library is "patched" (preferably by the people who forked
paramiko
) to account for this change, it will conflict withparamiko
and the 58 packages that depend onparamiko
.As a result, it is possible for you to change
paramiko-ng
withparamiko
to facilitate the packaging ofpwncat
?TIA.
The text was updated successfully, but these errors were encountered: