News for hackers. Stuff that matters.
Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by teddyh on Wednesday September 20, 2017 @02:13AM (#15291209)
Why didn’t you do this two years ago, when the first bug report about this was made? (https://gitlab.com/gnachman/iterm2/issues/3688) Or a year ago, when a second report was made? (https://gitlab.com/gnachman/iterm2/issues/5303) Note that the first bug report explicitly mentions the leaking of passwords.

Was it really all about the “level of concern”, as you say, and you wouldn’t have changed this without the exposure?

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by yanokwa on Wednesday September 20, 2017 @02:30AM (#15291273)
This is a deeply unkind thing to say to someone who donates their free time to provide a public good. George apologized for his oversight and fixed the problem. Take him at his word and thank him.
Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by woof on Wednesday September 20, 2017 @06:41AM (#15292282)
Please don't call this "oversight".

He was (made) aware of the problem and chose to keep the default.

Re:iTerm2: Please disable 'Perform DNS lookups to check if U... by nolok on Wednesday September 20, 2017 @08:11AM (#15292804)
Uhh, to be fair both reports were answered with appropriate concerns.

First made it sound like a very specific issue for that one user, and was given a way to disable it for him.

Second made it sound like an entire class of users would need it off, and an option switch was provided.

What do you think is more probable, that he intentionally left that hole open despite not directly benefitting from it, or simply that when he answered both original reports and provided an appropriate solution, he didn't fully think about the details and implications of what those issues meant?

Have you really never have a closed issue come back to you "went from bad to worse, abort!“ ?