Certificates - Revision history

Admin: /* Stealing certificates */

2017-12-15T16:32:46Z

Stealing certificates

← Older revision		Revision as of 16:32, 15 December 2017
Line 61:		Line 61:
	=Attacks on Certificates=		=Attacks on Certificates=

	==Stealing ~~certificates~~==		==Stealing SSL session info==

			One way to decrypt HTTPS information is to steal SSL session information, either in the form of SSL keys extracted from memory, or by obtaining the private key .pem file utilized by the browser to encrypt private HTTPS connections.

			These two approaches are covered here:
			* [[MITM Labs/Decrypting HTTPS Traffic with Private Key File]]
			* [[MITM Labs/Decrypting HTTPS Traffic by Obtaining Browser SSL Session Info]]

	==Exploiting/Forging certificates==		==Exploiting/Forging certificates==

Admin: /* Planting certificates */

2017-12-15T16:31:13Z

Planting certificates

← Older revision		Revision as of 16:31, 15 December 2017
Line 62:		Line 62:

	==Stealing certificates==		==Stealing certificates==

	~~==Planting certificates==~~

	==Exploiting/Forging certificates==		==Exploiting/Forging certificates==

Admin: /* Faking certificates */

2017-12-15T16:22:30Z

Faking certificates

@@ Line 84: / Line 84: @@
 Check out the following resources for HTTPS certificates and known private keys for embedded devices:
 * BenBE kompromat: https://github.com/BenBE/kompromat
 =Flags=

Admin: /* Corrupting Firefox certificates */

2017-12-15T16:22:17Z

Corrupting Firefox certificates

@@ Line 84: / Line 84: @@
 Check out the following resources for HTTPS certificates and known private keys for embedded devices:
 * BenBE kompromat: https://github.com/BenBE/kompromat
 =Flags=

Admin: /* Attacks on Certificates */

2017-12-15T16:22:10Z

Attacks on Certificates

← Older revision		Revision as of 16:22, 15 December 2017
Line 61:		Line 61:
	=Attacks on Certificates=		=Attacks on Certificates=

	==Defeating HTTPS with sslsniff and fake certificates==		==Stealing certificates==

			==Planting certificates==

			==Exploiting/Forging certificates==

			Topics in this category include:
			* Frankencert to create fake certificates
			* Bundled certificates whose private keys are compromised, but still might be bundled...
			* Fuzzing to generate certificates that will crash something like openssl or the ssl certificate checking software

			===Defeating HTTPS with sslsniff and fake certificates===

	{{Main\|SSLSniff}}		{{Main\|SSLSniff}}
Line 69:		Line 80:
	More on forged certificates below.		More on forged certificates below.

	==Faking certificates==		===Faking certificates===

	Check out the following resources for HTTPS certificates and known private keys for embedded devices:		Check out the following resources for HTTPS certificates and known private keys for embedded devices:
Line 80:		Line 91:
	Firefox comes bundled with certificate authorities. Here's how those work.		Firefox comes bundled with certificate authorities. Here's how those work.

	When a sheep connects to a server that claims to be a website like linux.org, the sheep's browser receives a certificate. To verify the certificate is valid, the sheep needs a trusted, third-party authority whose principal role is to go around signing certificates of people who can prove they are who their certificate says they are. If a sheep receives a certificate that says "I'm Google.com" and it's drawn in crayon on the back of an old homework assignment, it seems suspicious. If a sheep receives a certificate that says "I'm Google.com" and it has a signed note from The Pope that says "I can verify this certificate is valid", you can ~~bet~~ it's the real deal.		When a sheep connects to a server that claims to be a website like linux.org, the sheep's browser receives a certificate. To verify the certificate is valid, the sheep needs a trusted, third-party authority whose principal role is to go around signing certificates of people who can prove they are who their certificate says they are. If a sheep receives a certificate that says "I'm Google.com" and it's drawn in crayon on the back of an old homework assignment, it seems suspicious. If a sheep receives a certificate that says "I'm Google.com" and it has a signed note from The Pope that says "I can verify this certificate is valid", you can assume it is the real deal (assuming the Pope knows anything about internet infrastructure).

	To check third-party signatures, Firefox comes bundled with a set of certificate authorities, which it can use to independently check the signatures of the trusted third party.		To check third-party signatures, Firefox comes bundled with a set of certificate authorities, which it can use to independently check the signatures of the trusted third party.

Admin: /* Defeating HTTPS with sslsniff and fake certificates */

2016-08-29T10:59:15Z

Defeating HTTPS with sslsniff and fake certificates

← Older revision		Revision as of 10:59, 29 August 2016
Line 67:		Line 67:
	To defeat HTTPS in a way that is transparent to the sheep, you must be able to issue a certificate that the sheep trusts, and obtain a private key for that certificate. sslsniff allows you to use various self-made certificates and serve them up for various domains. This makes it easy to automate dealing with large numbers of forged certificates.		To defeat HTTPS in a way that is transparent to the sheep, you must be able to issue a certificate that the sheep trusts, and obtain a private key for that certificate. sslsniff allows you to use various self-made certificates and serve them up for various domains. This makes it easy to automate dealing with large numbers of forged certificates.

	More on ~~fake~~ certificates:		More on forged certificates below.

			==Faking certificates==

			Check out the following resources for HTTPS certificates and known private keys for embedded devices:
			* BenBE kompromat: https://github.com/BenBE/kompromat

	==Corrupting Firefox certificates==		==Corrupting Firefox certificates==

Admin: /* Defeating HTTPS with sslsniff and fake certificates */

2016-08-29T10:55:38Z

Defeating HTTPS with sslsniff and fake certificates

← Older revision		Revision as of 10:55, 29 August 2016
Line 62:		Line 62:

	==Defeating HTTPS with sslsniff and fake certificates==		==Defeating HTTPS with sslsniff and fake certificates==

			{{Main\|SSLSniff}}

	To defeat HTTPS in a way that is transparent to the sheep, you must be able to issue a certificate that the sheep trusts, and obtain a private key for that certificate. sslsniff allows you to use various self-made certificates and serve them up for various domains. This makes it easy to automate dealing with large numbers of forged certificates.		To defeat HTTPS in a way that is transparent to the sheep, you must be able to issue a certificate that the sheep trusts, and obtain a private key for that certificate. sslsniff allows you to use various self-made certificates and serve them up for various domains. This makes it easy to automate dealing with large numbers of forged certificates.

			More on fake certificates:

	==Corrupting Firefox certificates==		==Corrupting Firefox certificates==

Admin at 10:55, 29 August 2016

2016-08-29T10:55:03Z

← Older revision		Revision as of 10:55, 29 August 2016
Line 82:		Line 82:

	{{MITMFlag}}		{{MITMFlag}}

			[[Category:August 2016]]

Admin: /* Detecting the Attack */

2016-08-24T01:29:09Z

Detecting the Attack

← Older revision		Revision as of 01:29, 24 August 2016
Line 49:		Line 49:
	The end result: the attacker has established secure, encrypted communication channels with the sheep and the server.		The end result: the attacker has established secure, encrypted communication channels with the sheep and the server.

	===Detecting the Attack===		==Detecting the Attack==

	The naive may think this is enough to thwart encryption. But there's an alternate channel here for verifying identity: the public key. If the domain and the public key do not match, the sheep knows the traffic is being tampered with and that it is being presented with a fake certificate.		The naive may think this is enough to thwart encryption. But there's an alternate channel here for verifying identity: the public key. If the domain and the public key do not match, the sheep knows the traffic is being tampered with and that it is being presented with a fake certificate.

Admin: /* MITMed HTTPS Session */

2016-08-24T01:28:59Z

MITMed HTTPS Session

← Older revision		Revision as of 01:28, 24 August 2016
Line 31:		Line 31:
	The end result: secure, encrypted communications established by exchanging only public information on a public channel.		The end result: secure, encrypted communications established by exchanging only public information on a public channel.

	===MITMed HTTPS Session===		==MITMed HTTPS Session==

	When an HTTPS session is attacked with a man in the middle attack, the modified sequence looks like this:		When an HTTPS session is attacked with a man in the middle attack, the modified sequence looks like this:
Line 47:		Line 47:
	Client Key: The client responds to the attacker's (self-signed) certificate with its own public key, so that it can communicate securely with the attacker (which it thinks is the trusted HTTPS web server).		Client Key: The client responds to the attacker's (self-signed) certificate with its own public key, so that it can communicate securely with the attacker (which it thinks is the trusted HTTPS web server).

	The end result: the attacker has established secure, encrypted communication channels with the sheep and the server.		The end result: the attacker has established secure, encrypted communication channels with the sheep and the server.

	===Detecting the Attack===		===Detecting the Attack===