SystemsSec 2018W Lecture 8 - Revision history

Soma at 19:10, 31 January 2018

2018-01-31T19:10:33Z

← Older revision		Revision as of 19:10, 31 January 2018
Line 1:		Line 1:
	==Audio==		==Audio==

	[http://homeostasis.scs.carleton.ca/~soma/systemssec-2018w/comp4108-2018w.~~ova~~ Lecture 8 Audio]		[http://homeostasis.scs.carleton.ca/~soma/systemssec-2018w/lectures/comp4108-2018w-lec08-31Jan2018.m4a Lecture 8 Audio]

	==Notes==		==Notes==

Soma at 19:09, 31 January 2018

2018-01-31T19:09:42Z

← Older revision		Revision as of 19:09, 31 January 2018
Line 1:		Line 1:
			==Audio==

			[http://homeostasis.scs.carleton.ca/~soma/systemssec-2018w/comp4108-2018w.ova Lecture 8 Audio]

			==Notes==

	<!> Reminder to complete the experiences on time (before March 26th)		<!> Reminder to complete the experiences on time (before March 26th)

	~~= Review of networking =~~

	== ~~What is the~~ basis of the internet~~? ==~~		===The IP packet===

			The basis of the internet

	~~=== The IP packet ===~~
	If you want to connect to the internet all you need to be able to do is send/receive packets to someone who is connected to the internet. Everyone along the line can forward or pass along packets. What about ethernet and wifi? It’s just ways of sending packets		If you want to connect to the internet all you need to be able to do is send/receive packets to someone who is connected to the internet. Everyone along the line can forward or pass along packets. What about ethernet and wifi? It’s just ways of sending packets

	~~=== What’s~~ an ip packet? ~~===~~		What's in an IP packet?

	Data structure		Data structure
	:Header		:Header
Line 20:		Line 27:
	<blockquote>''Note: Packets are unprotected! There’s no confidentiality, it’s all in the open. Everyone who touches it on the way gets to see (or change!) the entire packet. Example; NAT is changing the source and destination packets!''</blockquote>		<blockquote>''Note: Packets are unprotected! There’s no confidentiality, it’s all in the open. Everyone who touches it on the way gets to see (or change!) the entire packet. Example; NAT is changing the source and destination packets!''</blockquote>

	=== ~~What’s the security problem?~~ ===		===Securing IP packets===
	~~There is~~ no security! How would you secure it? Certain fundamental problems about locking this down. What attacks can you perform on a set of IP packets?
			IP packets on their own have no security, and this isn't a simple oversight. Packet-level security is hard.

			How would you secure it? Certain fundamental problems about locking this down. What attacks can you perform on a set of IP packets?
	; Eavesdropping		; Eavesdropping
	: '''Δ''' You can only encrypt the payload!		: '''Δ''' You can only encrypt the payload!

Yannick: /* What’s the security problem? */

2018-01-31T17:31:09Z

What’s the security problem?

← Older revision		Revision as of 17:31, 31 January 2018
Line 33:		Line 33:

	'''Δ''' You can use a trusted intermediary service		'''Δ''' You can use a trusted intermediary service
	Δ Can also use onion routing (Tor) at the cost of speed
			'''Δ''' Can also use onion routing (Tor) at the cost of speed

	It’s not that the designers weren’t smart, it’s that their decision had to factor in a tradeoff between functionality and security costs.		It’s not that the designers weren’t smart, it’s that their decision had to factor in a tradeoff between functionality and security costs.


	=== Key management ===		=== Key management ===

Yannick at 17:30, 31 January 2018

2018-01-31T17:30:16Z

← Older revision		Revision as of 17:30, 31 January 2018
Line 1:		Line 1:
	<!> Reminder to complete the experiences on time (before March 26th)		<!> Reminder to complete the experiences on time (before March 26th)

	Review of networking		= Review of networking =
	~~What is the basis of the internet?~~
	~~IP packet, if you want to connect to the internet all you need it to be able to send/receive packets to someone who is connected to the internet~~
	~~Everyone along the line can forward or pass along packets~~
	~~What about ethernet and wifi? It’s just ways of sending packets~~

	What’s an ip packet?		== What is the basis of the internet? ==

			=== The IP packet ===
			If you want to connect to the internet all you need to be able to do is send/receive packets to someone who is connected to the internet. Everyone along the line can forward or pass along packets. What about ethernet and wifi? It’s just ways of sending packets

			=== What’s an ip packet? ===
	Data structure		Data structure
	Header		:Header
	Source IP		::Source IP
	Destination IP		::Destination IP
	Checksum		::Checksum
	Etc.		::Etc.
	Payload		:Payload
	Most important fields; source IP address and destination IP address		Most important fields are the '''source IP address''' and the '''destination IP address'''

	<!> Packets are unprotected! There’s no confidentiality, it’s all in the open. Everyone who touches it on the way gets to see (or change!) the entire packet. Example; NAT is changing the source and destination packets!		<blockquote>''Note: Packets are unprotected! There’s no confidentiality, it’s all in the open. Everyone who touches it on the way gets to see (or change!) the entire packet. Example; NAT is changing the source and destination packets!''</blockquote>

	What’s the security problem? There is no security!		=== What’s the security problem? ===
			There is no security! How would you secure it? Certain fundamental problems about locking this down. What attacks can you perform on a set of IP packets?
			; Eavesdropping
			: '''Δ''' You can only encrypt the payload!
			; Traffic analysis; rate of traffic, who’s talking to who, when they’re talking
			: The only way to prevent traffic analysis is to encrypt the header and mask it

	~~How would you secure it? Certain fundamental problems about locking this down. What attacks can you perform on a set of IP packets?~~		<blockquote>
	~~Eavesdropping~~		; Pizza delivery attack
	<!> ~~You can only encrypt the payload!~~		: Let’s say you’re a military organization, and you want to plan an attack but your employees are staying late? Oh look they ordered a pizza late at night, so now you have to order pizza all the time, keep the parking lot full, etc.
	~~Traffic analysis~~; ~~rate of traffic~~, ~~who’s talking~~ to ~~who~~, ~~when they’re talking~~		</blockquote>
	~~The only way~~ to ~~prevent traffic analysis is to encrypt~~ the ~~header and mask it~~

	~~<!> Pizza delivery attack~~		'''Δ''' You can use a trusted intermediary service
	~~Let’s say you’re a military organization, and you want to plan an attack but your employees are staying late? Oh look they ordered a pizza late~~ at ~~night, so now you have to order pizza all the time, keep~~ the ~~parking lot full, etc.~~		Δ Can also use onion routing (Tor) at the cost of speed

	~~<!> You can use~~ a ~~trusted intermediary service~~		It’s not that the designers weren’t smart, it’s that their decision had to factor in a tradeoff between functionality and security costs.
	~~<!> Can also use onion routing (Tor) at the cost of speed~~

	~~It’s not that the designers weren’t smart, it’s that their decision had to factor in a tradeoff between functionality and security costs.~~

			=== Key management ===
			You're going to send these packets to arbitrary other machines. Let’s assume you're going to do proper security (authentication, encrypt, etc..), you need to be able to identify the destination, you need their '''public key'''.

	~~Key management~~		; Where do I get the key? : Domain name system (DNS).
	~~I’m going to send these packets to arbitrary other machines. Let’s assume we’re going to~~ do ~~proper security (authentication, encrypt, etc..),~~ I ~~need to be able to identify~~ the ~~destination, I need their public~~ key.

	~~Where do I get the key? Domain name system (~~DNS).		The DNS maps Hostnames to IP addresses. Every domain name technically ends with a ‘.’ which is defined as the root, from there it goes down a level to com, and again down to something like google, etc..
	Every domain name ends with a ‘.’
	~~Starts from~~ root, goes to com, ~~goes~~ to google, etc..
	~~Hostname => IP address~~

	DNS is a bunch of records, there’s no cryptographic protection in DNS. ~~You~~ have to encrypt the entire ~~mappins, who do~~ you trust to do that? Who has the authority to manage this? DNSSEC is an attempt to solve this and is currently being deployed but from a management’s perspective is painful.		DNS is a bunch of public records, there’s no cryptographic protection in DNS. If you wanted to do that you would have to encrypt the entire mappings. Who would you trust to do that? Who has the authority to manage this? DNSSEC is an attempt to solve this and is currently being deployed but from a management’s perspective it is painful.

	What protocols would we use to securely communicate? TLS/SSH, but this would only work for the payload. ~~Gives~~ us end-to-end protection, except that everyone can see that those two endpoints are communicating.		What protocols would we use to securely communicate? TLS/SSH, but this would only work for the payload. It gives us end-to-end protection, except that everyone can see that those two endpoints are communicating.

	~~<!>~~ VOIP attack, you can figure out the words being said simply by examining the size of the packets being sent.		'''Δ''' There is a VOIP attack, in which you can figure out the words being said simply by examining the size of the packets being sent.

	What does a VPN give you?		=== What does a VPN give you? ===
	~~<!>~~ What part of the traffic encrypted and how is it authenticated?		'''Δ''' What part of the traffic is encrypted and how is it authenticated?
	~~The~~ whole packet is being encrypted, but it’s encapsulated in another header directed to the VPN gateway. Anyone observing your traffic would only see communication between you and the gateway.		With a VPN the whole packet is being encrypted, but it’s encapsulated in another header directed to the VPN gateway. Anyone observing your traffic would only see communication between you and the gateway.

	All you’ve done is move the problem, so why use it? It can help you against attackers close to you in the network space. If they have to compromise a VPN system further away that’s better maintained, it can in principle be harder to compromise.		All you’ve done is move the problem, so why use it? It can help you against attackers close to you in the network space. If they have to compromise a VPN system further away that’s better maintained, it can (in principle) be harder to compromise.

	What is your path of trust?		=== What is your path of trust? ===
	You cannot trust hostnames because DNS can be messed with. You can’t trust IP address as those can be changed. You can only trust the encryption in the payload.		You cannot trust hostnames because DNS can be messed with. You can’t trust IP address as those can be changed. You can only trust the encryption in the payload.

	How do you authenticate to a classic website?		=== How do you authenticate to a classic website? ===
	Download a certificate and it is vouched for by a built-in authority. But how does the site authenticate with you? You can have a public key (and a private key) to identify yourself to the organization. Example is the Yubikey; an external thumb drive to store your key.		Download a certificate and it is vouched for by a built-in authority. But how does the site authenticate with you? You can have a public key (and a private key) to identify yourself to the organization. Example is the Yubikey; an external thumb drive to store your key.

	Why not give everyone a key pair?		=== Why not give everyone a key pair? ===
	Hard to explain it to the everyone, and what happens when the cryptography becomes obsolete.		Hard to explain it to the everyone, and what happens when the cryptography becomes obsolete.

	At the end of the day, we can only really work with end-to-end and secure it on either end and hope that both ends are the correct ends.		At the end of the day, we can only really work with end-to-end and secure it on either end and hope that both ends are the correct ends.

Yannick: Created page with " Reminder to complete the experiences on time (before March 26th) Review of networking What is the basis of the internet? IP packet, if you want to connect to the internet..."

2018-01-31T17:11:56Z

Created page with "<!> Reminder to complete the experiences on time (before March 26th) Review of networking What is the basis of the internet? IP packet, if you want to connect to the internet..."

New page

<!> Reminder to complete the experiences on time (before March 26th)

Review of networking
What is the basis of the internet?
IP packet, if you want to connect to the internet all you need it to be able to send/receive packets to someone who is connected to the internet
Everyone along the line can forward or pass along packets
What about ethernet and wifi? It’s just ways of sending packets

What’s an ip packet?
Data structure
Header
Source IP
Destination IP
Checksum
Etc.
Payload
Most important fields; source IP address and destination IP address

<!> Packets are unprotected! There’s no confidentiality, it’s all in the open. Everyone who touches it on the way gets to see (or change!) the entire packet. Example; NAT is changing the source and destination packets!

What’s the security problem? There is no security!

How would you secure it? Certain fundamental problems about locking this down. What attacks can you perform on a set of IP packets?
Eavesdropping
<!> You can only encrypt the payload!
Traffic analysis; rate of traffic, who’s talking to who, when they’re talking
The only way to prevent traffic analysis is to encrypt the header and mask it

<!> Pizza delivery attack
Let’s say you’re a military organization, and you want to plan an attack but your employees are staying late? Oh look they ordered a pizza late at night, so now you have to order pizza all the time, keep the parking lot full, etc.

<!> You can use a trusted intermediary service
<!> Can also use onion routing (Tor) at the cost of speed

It’s not that the designers weren’t smart, it’s that their decision had to factor in a tradeoff between functionality and security costs.

Key management
I’m going to send these packets to arbitrary other machines. Let’s assume we’re going to do proper security (authentication, encrypt, etc..), I need to be able to identify the destination, I need their public key.

Where do I get the key? Domain name system (DNS).
Every domain name ends with a ‘.’
Starts from root, goes to com, goes to google, etc..
Hostname => IP address

DNS is a bunch of records, there’s no cryptographic protection in DNS. You have to encrypt the entire mappins, who do you trust to do that? Who has the authority to manage this? DNSSEC is an attempt to solve this and is currently being deployed but from a management’s perspective is painful.

What protocols would we use to securely communicate? TLS/SSH, but this would only work for the payload. Gives us end-to-end protection, except that everyone can see that those two endpoints are communicating.

<!> VOIP attack, you can figure out the words being said simply by examining the size of the packets being sent.

What does a VPN give you?
<!> What part of the traffic encrypted and how is it authenticated?
The whole packet is being encrypted, but it’s encapsulated in another header directed to the VPN gateway. Anyone observing your traffic would only see communication between you and the gateway.

All you’ve done is move the problem, so why use it? It can help you against attackers close to you in the network space. If they have to compromise a VPN system further away that’s better maintained, it can in principle be harder to compromise.

What is your path of trust?
You cannot trust hostnames because DNS can be messed with. You can’t trust IP address as those can be changed. You can only trust the encryption in the payload.

How do you authenticate to a classic website?
Download a certificate and it is vouched for by a built-in authority. But how does the site authenticate with you? You can have a public key (and a private key) to identify yourself to the organization. Example is the Yubikey; an external thumb drive to store your key.

Why not give everyone a key pair?
Hard to explain it to the everyone, and what happens when the cryptography becomes obsolete.

At the end of the day, we can only really work with end-to-end and secure it on either end and hope that both ends are the correct ends.