Andrew !
Your overview abilities seem to be driven by some kind of a super power.
Nice job on “Foundations of Social Engineering…” on Corbett Report.
Will subscribe to your podcasts as soon as funds allow.. Soon enough.
The very best to you and keep ‘em coming !
This following text (‘warning’) was presented to me upon linking to this page and I suspect is a form of fear mongering censorship.
——————–|||
THIS IS PROBABLY NOT THE SITE YOU ARE LOOKING FOR!
You attempted to reach colonel6.com, but instead you actually reached a server identifying itself as *.wordpress.com. This may be caused by a misconfiguration on the server or by something more serious. An attacker on your network could be trying to get you to visit a fake (and potentially harmful) version of colonel6.com.
You should not proceed, especially if you have never seen this warning before for this site.
Proceed anyway Back to safety
HELP ME UNDERSTAND < [Link/TAB] — Shows…
When you connect to a secure website, the server hosting that site presents your browser with something called a "certificate" to verify its identity. This certificate contains identity information, such as the address of the website, which is verified by a third party that your computer trusts. By checking that the address in the certificate matches the address of the website, it is possible to verify that you are securely communicating with the website you intended, and not a third party (such as an attacker on your network).
In this case, the address listed in the certificate does not match the address of the website your browser tried to go to. One possible reason for this is that your communications are being intercepted by an attacker who is presenting a certificate for a different website, which would cause a mismatch. Another possible reason is that the server is set up to return the same certificate for multiple websites, including the one you are attempting to visit, even though that certificate is not valid for all of those websites. Google Chrome can say for sure that you reached *.wordpress.com, but cannot verify that that is the same site as colonel6.com which you intended to reach. If you proceed, Chrome will not check for any further name mismatches.
——————–|||
Thought you might like to know.
Delete this comment if you wish. no offence either way.
Keep up the great work.
Andrew !
Your overview abilities seem to be driven by some kind of a super power.
Nice job on “Foundations of Social Engineering…” on Corbett Report.
Will subscribe to your podcasts as soon as funds allow.. Soon enough.
The very best to you and keep ‘em coming !
Posted by Liam Bradley | April 4, 2012, 10:42 pmThis following text (‘warning’) was presented to me upon linking to this page and I suspect is a form of fear mongering censorship.
——————–|||
THIS IS PROBABLY NOT THE SITE YOU ARE LOOKING FOR!
You attempted to reach colonel6.com, but instead you actually reached a server identifying itself as *.wordpress.com. This may be caused by a misconfiguration on the server or by something more serious. An attacker on your network could be trying to get you to visit a fake (and potentially harmful) version of colonel6.com.
You should not proceed, especially if you have never seen this warning before for this site.
Proceed anyway Back to safety
HELP ME UNDERSTAND < [Link/TAB] — Shows…
When you connect to a secure website, the server hosting that site presents your browser with something called a "certificate" to verify its identity. This certificate contains identity information, such as the address of the website, which is verified by a third party that your computer trusts. By checking that the address in the certificate matches the address of the website, it is possible to verify that you are securely communicating with the website you intended, and not a third party (such as an attacker on your network).
In this case, the address listed in the certificate does not match the address of the website your browser tried to go to. One possible reason for this is that your communications are being intercepted by an attacker who is presenting a certificate for a different website, which would cause a mismatch. Another possible reason is that the server is set up to return the same certificate for multiple websites, including the one you are attempting to visit, even though that certificate is not valid for all of those websites. Google Chrome can say for sure that you reached *.wordpress.com, but cannot verify that that is the same site as colonel6.com which you intended to reach. If you proceed, Chrome will not check for any further name mismatches.
——————–|||
Thought you might like to know.
Delete this comment if you wish. no offence either way.
Keep up the great work.
Posted by Liam Bradley | April 5, 2012, 10:09 am