22 ms·
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 https://gitlab.com/gnachm
by teddyh 9y ago
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 https://gitlab.com/gnachman/iterm2/issues/3688) Or a year ago, when a second report was made? (https://gitlab.com/gnachman/iterm2/issues/5303 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?
- yanokwa 9y agoThis 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.
- woof 9y agoPlease don't call this "oversight". He was (made) aware of the problem and chose to keep the default.
- nolok 9y agoUhh, 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!“ ?