<br><br><div><span class="gmail_quote">2008/3/11, Robby Workman <<a href="mailto:rworkman@slackbuilds.org">rworkman@slackbuilds.org</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
ciol wrote:<br> <br>> Robby Workman wrote:<br> >> Well, I'm not sure that's the right approach - there may very well be<br> >> some cases where the admin has assigned group permissions to be<br> >> readable or even writable, and we don't want to blow that away.<br>
>> That being said, it is somewhat of a corner case, and I guess that,<br> >> all things considered, it's probably better for the admin to have to<br> >> reset those permissions than to have compromised private key.<br>
>><br> ><br> <br>> echo "WARNING: you should do a chmod -r [...]"<br> ><br> > No?<br> <br> <br> <br>Well, that's an option, but there's no guarantee that it will be<br> seen (of course, there never it, but in this case especially).<br>
If the package is installed as part of a large group, the message<br> will scroll past way too quickly to read...<br> <br> I've got another idea, but I'll have to test - more later...</blockquote><div><br><br><a href="mailto:slackbuilds-security@slackbuilds.org">slackbuilds-security@slackbuilds.org</a> :o)<br>
<br></div></div>