News for hackers. Stuff that matters.
Re:Compromising a Linux desktop using 6502 opcodes on the NES by partycoder on Monday November 14, 2016 @03:25PM (#12953003)
The UX should say: "This file is a NSF file, do you want to open it?"
Re:Compromising a Linux desktop using 6502 opcodes on the NES by alanh on Monday November 14, 2016 @04:07PM (#12953381)
1) Make an argument. This isn’t one.

2) Why suggest a prompt that doesn’t give the user an understanding of what they are being asked and why it matters?

Re:Compromising a Linux desktop using 6502 opcodes on the NES by partycoder on Monday November 14, 2016 @06:10PM (#12954208)
Implicit information is what allowed millions of devices to be infected via AUTORUN.INF files causing billions of dollars in damage.

People think in ways of making things simple and easy, but you end up harming people. It's a leaky abstraction of trust.

This would fall into the same category. You don't expect risk from a MP3. But then it's not an MP3, it's a NSF.

Re:Compromising a Linux desktop using 6502 opcodes on the NES by voltagex_ on Tuesday November 15, 2016 @01:24AM (#12956058)
and continuously prompting people for input is a good way to train them to always click "Yes".

https://www.nist.gov/news-events/news/2016/10/security-fatig...

Re:Compromising a Linux desktop using 6502 opcodes on the NES by partycoder on Tuesday November 15, 2016 @02:14AM (#12956222)
Would not be fatigue. If the extension is mp3 and the detected type is mp3, no need to show a dialog. Only show a dialog if there might be something phony going on.
Re:Compromising a Linux desktop using 6502 opcodes on the NES by fowl2 on Monday November 14, 2016 @03:50PM (#12953213)
What user, upon attempting to open the file, would say "no"?

I wouldn't.

Re:Compromising a Linux desktop using 6502 opcodes on the NES by tripzilch on Thursday November 17, 2016 @07:50AM (#12976978)
But then there is no helping you no matter what, is there.