< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index |
I would strongly advise against
doing this, as it means you're defenseless against a
man-in-the-middle attack. The problem with sip2sip.info is that
either the cert being served by sipthor.net isn't authoritative
for sip2sip.info (which means that it appears to be a DNS-mediated
man-in-the-middle attack), or it is and we aren't handling the
cert correctly. If it is the former, any implementation that works
has a serious security vulnerability, or some special bit of
configuration that tells it to treat these two domains as
equivalent. It would be nice to see a dump of the cert being
served by sipthor.net to rule out the latter.
Best regards, Byron Campen
|