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

Bad version of Masscan installed from APT #566

Closed
choupit0 opened this issue Mar 12, 2021 · 6 comments
Closed

Bad version of Masscan installed from APT #566

choupit0 opened this issue Mar 12, 2021 · 6 comments

Comments

@choupit0
Copy link

Hello,

I do not know if I'm wrong but when I try to install Masscan on a fresh Debian version, the version installed is not the same as the apt show package.... Even if I try to install the specific version.

Debian version

Debian_version

APT version -> 1.0.5

APT_version-1-0-5

Version installed -> 1.0.4

Masscan_version1-0-4

An idea? Is it a Masscan issue or Debian/APT issue? Or it's me?....

@mzpqnxow
Copy link
Contributor

You may want to try which masscan to see if you're actually running a locally built version that you installed somewhere (e.g. in /usr/local/bin)

If that's not the issue, you'll have to send this to the maintainer (looks like team+pkg-security@tracker.debian.org)

Either way there's nothing that can be done for you here unfortunately- even if this were an issue with the version string in the masscan source, it will be the package maintainers that need to "fix" it

@its0x08
Copy link

its0x08 commented Mar 13, 2021

After locating both versions using which command, delete the old one and also check the $PATH variable and switch the path of the old one after the path of new one so in future all software being executed with be searched on that path first and then the next one in case in the first dir the bin doesnt exist.
An example..
old path PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
new path PATH=/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin

@choupit0 choupit0 reopened this Mar 13, 2021
@choupit0
Copy link
Author

choupit0 commented Mar 13, 2021

You may want to try which masscan to see if you're actually running a locally built version that you installed somewhere (e.g. in /usr/local/bin)

If that's not the issue, you'll have to send this to the maintainer (looks like team+pkg-security@tracker.debian.org)

Either way there's nothing that can be done for you here unfortunately- even if this were an issue with the version string in the masscan source, it will be the package maintainers that need to "fix" it

Unfortunately this is really Masscan 1.0.4 which is running... You are right, I will try to contact the maintainer.

Thank you.

Edit: Done.

@mzpqnxow
Copy link
Contributor

mzpqnxow commented Mar 13, 2021

Thank you.

Happy to help, glad you got it sorted

You can close this out now (I think it reopened when you commented)

@choupit0
Copy link
Author

You can close this out now (I think it reopened when you commented)

Nope, my bad. I closed it accidentaly.

@rhertzog
Copy link

Actually, your 1.0.5 tag points to a commit where src/masscan-version.h has 1.0.4:
https://github.com/robertdavidgraham/masscan/releases/tag/1.0.5
https://github.com/robertdavidgraham/masscan/tree/83fbdf6fde8f40573381a546d6b27cc78d77cc85/src
https://github.com/robertdavidgraham/masscan/blob/83fbdf6fde8f40573381a546d6b27cc78d77cc85/src/masscan-version.h

But there's no point in fixing anything here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants