Added ssl port range to certificate check in decryption stage

Evidence from my own test as well as one carried out on IRC shows that there are cases where the tshark execution on lines 294.. in tlsnotary-auditee.py fails to find a certificate frame, unless the ssl ports range is properly reset. I'm not sure that this is always the case (i.e. I'm not sure that tshark/wireshark requires the port to be an ssl port in order to recognize handshake packets), but whether it is or not, some sites trigger the exception on line 298/300 if this is not done.