fix false positive with untrusted flag

[RamanaReddy0M]

#268 False positive with untrusted flag, but manual certificate check shows trusted status

[RamanaReddy0M]

✗ ./tlsx -un -host ebay.co.jp,comicon.it,sambonet.it
  

  _____ _    _____  __
 |_   _| |  / __\ \/ /
   | | | |__\__ \>  < 
   |_| |____|___/_/\_\  v1.1.0

                projectdiscovery.io

[INF] Current tlsx version v1.1.0 (latest)
sambonet.it:443
ebay.co.jp:443
comicon.it:443
[INF] Connections made using crypto/tls: 3, zcrypto/tls: 0, openssl: 0

[Mzack9999]

lgtm - I suggest moving the update certificate logic to a separate cmd utility (e.g., https://github.com/projectdiscovery/wappalyzergo/blob/main/cmd/update-fingerprints/main.go) that is run with a cron-fashion. Then it just gets loaded via embed, removing the need of reading/writing any external file as it gets included directly in the final binary:

import (
	_ "embed"
)

//go:embed root_certs.pem
var data string

What do you think?

[Mzack9999]

lgtm!

$ go run . -un -host ebay.co.jp,comicon.it,sambonet.it
...
sambonet.it:443
comicon.it:443
ebay.co.jp:443
[INF] Connections made using crypto/tls: 3, zcrypto/tls: 0, openssl: 0