On 05/19/2010 03:11 PM, Christoph Anton Mitterer wrote: > Or is that already, the case? At least I've had the impression that > neither mine, nor the arguments of some other people (Harald, Peter, etc.) > were even answered here. You've only mentioned that SSH won't operate if the write bit is set on the keys or anything under the ~/.ssh/ directory. Can you explain how an ssh client failing to connect to an external ssh server because of the umask is compromising security on the system? Also, can you please provide an extra carriage return between your reply and the quoted text? Reading your replies is a bit annoying. > The reason could be that people simply don't recognise, that they might > have compromised their own security... and those who know what happens > don't complain. Please explain how people's security is compromised because their umask is 0002 instead of 0022. I'm still waiting for this FUD to be backed up. -- . O . O . O . . O O . . . O . . . O . O O O . O . O O . . O O O O . O . . O O O O . O O O
Attachment:
signature.asc
Description: OpenPGP digital signature