Skip to main content
11 events
when toggle format what by license comment
Jul 14, 2023 at 20:10 comment added Coruscate5 A normal cert should be like ---- BEGIN CERTIFICATE ---- [base64data] ---- END CERTIFICATE ---- - I just copied over to notepad from nmap to clean up the formatting and verify the encoding
Jul 14, 2023 at 20:07 comment added Coruscate5 there's just some cruft in the nmap output, just need to clean up the indents and pipes. nmap's tool is the only one that seems to support this over SQL protocol, sslscan just explodes
Jul 11, 2023 at 13:16 comment added jpierson I didn't see that in my output. I'll run it again and double check things. I wonder if the behavior is different if certificate is installed and encryption is enabled but not forced? Thanks for the example.
Jul 9, 2023 at 20:15 comment added gdeff Example output added. You could pipe it through sed, for example, to get a readable certificate file: nmap -sV -p <port> -vv --script ssl-cert <address>| sed -En "s/^\|.//p" > cert.crt # Still not seeing a certificate in your output? ¯\_(ツ)_/¯
Jul 9, 2023 at 20:05 history edited gdeff CC BY-SA 4.0
example output added
Jul 7, 2023 at 12:29 comment added jpierson I ran this exact command which succeeded but did not appear to output anything that I could discern as a public certificate. Is there an extra parameter necessary or does the certificate get stuck into some file based report somewhere? I more detailed answer on where to find the certificate after running the command would be useful.
Mar 11, 2023 at 1:03 history edited mustaccio CC BY-SA 4.0
edited body
Mar 11, 2023 at 0:15 history edited gdeff CC BY-SA 4.0
added 124 characters in body
Mar 8, 2023 at 20:55 review Low quality posts
Mar 10, 2023 at 15:51
S Mar 8, 2023 at 20:35 review First answers
Mar 8, 2023 at 21:03
S Mar 8, 2023 at 20:35 history answered gdeff CC BY-SA 4.0