top | item 20793956 (no title) jpjuni0r | 6 years ago I'm curious how sscanf is considered bad? discuss order hn newest saagarjha|6 years ago scanf(“%s”, …) can cause a buffer overflow. mort96|6 years ago It sucks that there's no scanf("%.*s"), where you give the buffer length as a separate argument. The fact that it's in a string literal also makes using a compile-time constant really ugly. claystu|6 years ago You can overflow buffers all sorts of ways in C.
saagarjha|6 years ago scanf(“%s”, …) can cause a buffer overflow. mort96|6 years ago It sucks that there's no scanf("%.*s"), where you give the buffer length as a separate argument. The fact that it's in a string literal also makes using a compile-time constant really ugly. claystu|6 years ago You can overflow buffers all sorts of ways in C.
mort96|6 years ago It sucks that there's no scanf("%.*s"), where you give the buffer length as a separate argument. The fact that it's in a string literal also makes using a compile-time constant really ugly.
saagarjha|6 years ago
mort96|6 years ago
claystu|6 years ago