Talk:HFS Legacy Volume Name Stack Buffer Overflow

Name
I know pod2g coined this name, but this vulnerability's name is ridiculously long. I'd like to shorten it to "HFS Volume Name Stack Buffer Overflow" "HFS Volume Name Vulnerability," provided people are OK with the name change. -- Dialexio 19:11, 4 February 2011 (UTC)
 * I'm kind of playing devil's advocate here but the extreme length is kind of cool to show the intricacy and specificity of the exploit at hand -- and it's nice to preserve the original wording of things... But I suppose it's up to you. --Iemit737 21:27, 4 February 2011 (UTC)
 * I won't take action unless others agree; this seems like a major change that could stir up controversy. ;) I think we can drop "Legacy" because HFS itself is considered legacy (Apple's current thing is HFS+), and we can provide more details about the vulnerability on the article itself. -- Dialexio 22:08, 4 February 2011 (UTC)
 * I agree that it's long. But who cares? Nobody will ever enter this name into the search box - everybody will access this page through some link. And because pod2g created the name, I wouldn't change it unless he agrees. --http 23:43, 4 February 2011 (UTC)
 * I think that "Legacy Volume" is unnecessary but "Name Stack buffer overflow" is necessary because a Buffer overflow is not the same as vulnerability. Itaiyz97 05:58, 4 December 2011 (MST)

How exactly does this exploit work?
I haven't seen anything anywhere about how this exploit actually works... someone care to explain? --rdqronos 22:22, 3 December 2011 (MST)
 * Read i0n1c's slides, mentioned in the links. That should explain everything. --http 05:50, 5 December 2011 (MST)