Skip to content

Fix problem when nmap file has .txt extension (3.0)#1937

Merged
drwetter merged 2 commits into3.0from
fix_1935_3.0
Jul 25, 2021
Merged

Fix problem when nmap file has .txt extension (3.0)#1937
drwetter merged 2 commits into3.0from
fix_1935_3.0

Conversation

@drwetter
Copy link
Copy Markdown
Collaborator

This addresses a bug filed in #1935 in 3.1dev when the supplied file
has a .txt extension. In this scenario the input file was nulled
as from the input file in nmap format an internal input file was
generated which has a .txt extension, in the same directory.
The idea was to persist the file for the user.

Now, this internal input file is ephemeral and only written to $TEMPDIR.

drwetter added 2 commits July 25, 2021 16:40
This addresses a bug filed in #1935 in 3.1dev when the supplied file
has a .txt extension. In this scenario the input file was nulled
as from the input file in nmap format an internal input file was
generated which has a .txt extension, in the same directory.
The idea was to persist the file for the user.

Now, this internal input file is ephemeral and only written to $TEMPDIR.
... see #1936.

It is ~ copied from testssl.sh. It adds a detection for the
strings ssl and https. If those run at non-standard ports but nmap
detected it, it'll show up in the output file.
@drwetter drwetter merged commit f4800f8 into 3.0 Jul 25, 2021
@drwetter drwetter deleted the fix_1935_3.0 branch July 25, 2021 15:17
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

Successfully merging this pull request may close these issues.

1 participant