xehonu / skipfish

Automatically exported from code.google.com/p/skipfish
Apache License 2.0
0 stars 0 forks source link

ignore ssl certificate errors #33

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Would it be possible to have a flag for ignoring:
1) self signed ssl certificates
2) out of date ssl certificates

Many thanks

Original issue reported on code.google.com by gdsmarsh...@googlemail.com on 24 Mar 2010 at 12:17

GoogleCodeExporter commented 8 years ago
That's just one warning per scan (or at least, should be), why not just glance 
over it 
if you don't care?

Original comment by lcam...@gmail.com on 24 Mar 2010 at 12:25

GoogleCodeExporter commented 8 years ago
I was pretty certain it did not continue. i.e. got an out of date certificate 
and
then ended, otherwise you are correct, the warning should be ignored rather than
changing the code.  I will check again tonight.

Thank you

Original comment by gdsmarsh...@googlemail.com on 24 Mar 2010 at 11:26

GoogleCodeExporter commented 8 years ago
That should not be the case; please reopen if you observe otherwise.

Original comment by lcam...@gmail.com on 24 Mar 2010 at 3:28

GoogleCodeExporter commented 8 years ago
[Internal warning]  
Resource fetch failed

   1.
      Fetch result: Connection error
      Memo: during initial directory fetch

be my guest and point at https://www.dalmany.co.uk

Original comment by gdsmarsh...@googlemail.com on 24 Mar 2010 at 8:33

GoogleCodeExporter commented 8 years ago
jfyi this is the command I am using
./skipfish -o output_dir3 https://www.dalmany.co.uk

Original comment by gdsmarsh...@googlemail.com on 24 Mar 2010 at 8:35

GoogleCodeExporter commented 8 years ago
Can't reproduce - I see a valid scan with an SSL cert warning.

The only problem seems to be that the server is *very* slow to respond - you 
might
want to specify -w 60 -t 60 in the command-line.

Original comment by lcam...@google.com on 24 Mar 2010 at 8:45

GoogleCodeExporter commented 8 years ago
At home I am using IPv6 at work I use IPv4.  I get no problem just like you.

Original comment by gdsmarsh...@googlemail.com on 26 Mar 2010 at 12:14