Path: csiph.com!weretis.net!feeder4.news.weretis.net!newsfeed.datemas.de!news.datemas.de!.POSTED!not-for-mail
From: Alan Baker <alangbaker@telus.net>
Newsgroups: comp.sys.mac.system
Subject: Re: Could Mac Files be Ransomwared via Windows XP Running in a VM?
Date: Tue, 16 May 2017 09:45:41 -0700
Organization: Datemas.de http://www.news.datemas.de
Message-ID: <offabo$vre$1@news.datemas.de>
References: <0001HW.D53CC867004C47F0B02919BF@news.astraweb.com> <of8d8o$h5t$1@news.albasani.net> <ofa5vi$ep8$1@news.albasani.net> <ofabrk$vp8$1@gioia.aioe.org> <ofad0j$1225$1@gioia.aioe.org> <ofanpu$1jjr$2@gioia.aioe.org> <ofapa7$1l81$2@gioia.aioe.org> <super70s-25FF3A.08252515052017@reader.albasani.net> <ofd58k$1kq8$1@gioia.aioe.org> <ofd64a$9hc$1@news.datemas.de> <ofd6vt$1ne7$1@gioia.aioe.org> <150520171740426665%nospam@nospam.invalid> <ofd7v9$che$2@news.datemas.de> <150520171755581632%nospam@nospam.invalid> <enuu71Fd9p7U3@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 16 May 2017 16:45:44 +0000 (UTC)
Injection-Info: news.datemas.de; logging-data="32622"; mail-complaints-to="abuse@datemas.de"; x-trace=Vdq7Y+S399ksShPRE8X1gTcyYm+GbIrgd8srTzLRsTFPbFm7+J1iU4PnmwyOzQQyswNw4yuru6QrfJqFPlB1PJ3LK4TcG25QSSn68M8PjMSF9sMrWzMPpOynvnuXWQN3HG33rRYBClIgnWJoItqLx2lCc5v9ko1f
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
In-Reply-To: <enuu71Fd9p7U3@mid.individual.net>
Xref: csiph.com comp.sys.mac.system:106929

On 2017-05-15 5:08 PM, Jolly Roger wrote:
> On 2017-05-15, nospam <nospam@nospam.invalid> wrote:
>> In article <ofd7v9$che$2@news.datemas.de>, Alan Baker
>> <alangbaker@telus.net> wrote:
>>
>>>>>>>> "Repair Permissions" is not useless since it does do something,
>>>>>>>> BUT whether running that process actually fixes *all* the
>>>>>>>> problems it supposedly does is a totally different question.
>>>>>>>
>>>>>>> it's useless and rarely fixes anything, if ever.
>>>>>
>>>>> It fixes what it was designed to fix ... Permissions.
>>>>
>>>> permissions do not break, so there's nothing to fix.
>>>
>>> I'm sorry, but at the very least, permissions DID (past tense) break.
>>
>> permissions are just a setting. they cannot break.
>>
>> they might be different than what apple thinks they should be but that
>> doesn't mean they're broken. it just means they're different.
>>
>> there are valid reasons for permissions to be different and without
>> causing any issues whatsoever.
>>
>>>> it resets permissions to what apple thinks they should be, which
>>>> isn't the only valid choice.
>>>
>>> Ummm... ...no.
>>
>> um, yes.
>>
>> there is no single 'correct' permission setting.
>
> Yep. In fact the glaring design fault of Repair Permissions is that it
> has no way to resolve the case where two different receipts have
> differing permission settings for a given file, which actually happens
> quite frequently. That means it's actually quite common for there to be
> disagreement (even between two *Apple* installs) about what the correct
> permissions should be for installed files.
>

Cite, please...