On 9 Jul 2024 15:20:05 GMT, Jolly Roger wrote:

> Before you even start up, Windows 11 is on guard.

When I looked it up, it was pretty clear in all the reports that these
cocoapods flaws are only in the Apple ecosystem as far as I have read.

Please cite where you got the idea cocoapods is part of the Windows
ecosystem as everything you say is wrong until you can show that cite.

On 2024-07-09 09:26, Wolf Greenblatt wrote:
> On Tue, 9 Jul 2024 08:07:20 -0400, Alan Browne wrote:
>
>>> Three million iOS/macOS apps were vulnerable for a decade, and Apple didn't
>>> even care to think about backing up their own claims of safety & security.
>>
>> I and others have made clear that this is not in Apple's court, and you
>> have admitted that you don't understand 3rd party toolchains and code
>> source, but you keep banging the same drum.
>
> While it's clear I don't understand how Apple could have allowed this hole
> in their ecosystem to exist for a decade, what I do very clearly understand
> is that Apple's safe & secure ecosystem claims are shown to be unsupported.

As explained, and you keep obtusely jumping around, the "hole" doesn't
belong to Apple.

And, unless some actual malicious code comes in via the hole that
belongs to someone else, Apple won't detect it.

> Why does Apple say their system is safe & secure when obviously it's not?

All that is obvious is you have no understanding of the issue.

Apple cares. Their system is as safe and secure as is reasonable
considering it is a very popular destination for 3rd party apps.

And again, the vast majority of malware that gets to the App Store is
stopped there.

And AGAIN: There is ZERO evidence of any of the abandoned source code
being converted to malicious code and thence onto the App Store.

NONE. NADA. ZILCH.

Which renders all of your dog whistle nonsense into noise.

Done. Really.

--
"It would be a measureless disaster if Russian barbarism overlaid
the culture and independence of the ancient States of Europe."
Winston Churchill

On 2024-07-09 12:03, Alan wrote:
> On 2024-07-09 06:26, Wolf Greenblatt wrote:
>> On Tue, 9 Jul 2024 08:07:20 -0400, Alan Browne wrote:
>>
>>>> Three million iOS/macOS apps were vulnerable for a decade, and Apple
>>>> didn't
>>>> even care to think about backing up their own claims of safety &
>>>> security.
>>>
>>> I and others have made clear that this is not in Apple's court, and you
>>> have admitted that you don't understand 3rd party toolchains and code
>>> source, but you keep banging the same drum.
>>
>> While it's clear I don't understand how Apple could have allowed this
>> hole
>> in their ecosystem to exist for a decade, what I do very clearly
>> understand
>> is that Apple's safe & secure ecosystem claims are shown to be
>> unsupported.
>
> It wasn't a hole in "their ecosystem", doofus.
>
> This was something OUTSIDE Apple's ecosystem; a third-party tool used by
> developers before their software was ever submitted to Apple.

He's a pig and shit.
Wrestling with it gets you filthy and he enjoys it.

--
"It would be a measureless disaster if Russian barbarism overlaid
the culture and independence of the ancient States of Europe."
Winston Churchill

On 2024-07-09 09:42, Wolf Greenblatt wrote:
> On 9 Jul 2024 15:20:05 GMT, Jolly Roger wrote:
>
>> Before you even start up, Windows 11 is on guard.
>
> When I looked it up, it was pretty clear in all the reports that these
> cocoapods flaws are only in the Apple ecosystem as far as I have read.

There are similar tools (dependency managers for developers) across all
OS ecosystems, doofus.

>
> Please cite where you got the idea cocoapods is part of the Windows
> ecosystem as everything you say is wrong until you can show that cite.

On 2024-07-09, Wolf Greenblatt <wolf@greenblatt.net> wrote:
> On 9 Jul 2024 15:20:05 GMT, Jolly Roger wrote:
>
>> Before you even start up, Windows 11 is on guard.
>
> When I looked it up, it was pretty clear in all the reports that these
> cocoapods flaws are only in the Apple ecosystem as far as I have read.
>
> Please cite where you got the idea cocoapods is part of the Windows
> ecosystem as everything you say is wrong until you can show that cite.

Like a child, when presented with facts that show his lies to be false
(in this case that Microsoft supposedly doesn't tout security), little
Arlen snips context and tries to distort and misrepresent what was
actually said. His juvenile trolls are weak.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

On 2024-07-09, Alan <nuh-uh@nope.com> wrote:
> On 2024-07-09 09:42, Wolf Greenblatt wrote:
>> On 9 Jul 2024 15:20:05 GMT, Jolly Roger wrote:
>>
>>> Before you even start up, Windows 11 is on guard.
>>
>> When I looked it up, it was pretty clear in all the reports that
>> these cocoapods flaws are only in the Apple ecosystem as far as I
>> have read.
>
> There are similar tools (dependency managers for developers) across
> all OS ecosystems, doofus.

Yes, but we are supposed to ignore those (and also the FACT thati
contrary to little Arlen's lie, Microsoft and others do indeed tout
security of their platforms), because: troll.

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

Wolf Greenblatt <wolf@greenblatt.net> wrote:
> On Tue, 9 Jul 2024 11:56:44 +0100, Chris wrote:
>
>> You could say the same about any currently unknown, but existing,
>> vulnerability available in any software. Do Google, Microsoft, etc also
>> not care about those?
>
> Apple loudly advertises their ecosystem is safe & secure, not Microsoft.
> Why does Apple say their system is safe & secure when obviously it's not?

Why is this Apple's fault? Developers en masse chose to use a third party
set of tools that were maintained by a small team and supported by a wider
group of volunteers.

Should Apple ban the use of third party libraries? How would you solve this
issue from happening again?

On 2024-07-09 13:49, Alan wrote:
> On 2024-07-09 09:42, Wolf Greenblatt wrote:
>> On 9 Jul 2024 15:20:05 GMT, Jolly Roger wrote:
>>
>>> Before you even start up, Windows 11 is on guard.
>>
>> When I looked it up, it was pretty clear in all the reports that these
>> cocoapods flaws are only in the Apple ecosystem as far as I have read.
>
> There are similar tools (dependency managers for developers) across all
> OS ecosystems, doofus.
>
>>
>> Please cite where you got the idea cocoapods is part of the Windows
>> ecosystem as everything you say is wrong until you can show that cite.

You're in broken record territory with the big-droopy-eared-sad-eyed
troll thing.

--
"It would be a measureless disaster if Russian barbarism overlaid
the culture and independence of the ancient States of Europe."
Winston Churchill

Wolf Greenblatt wrote:
> On Tue, 9 Jul 2024 08:07:20 -0400, Alan Browne wrote:
>
>>> Three million iOS/macOS apps were vulnerable for a decade, and Apple didn't
>>> even care to think about backing up their own claims of safety & security.
>>
>> I and others have made clear that this is not in Apple's court, and you
>> have admitted that you don't understand 3rd party toolchains and code
>> source, but you keep banging the same drum.
>
> While it's clear I don't understand how Apple could have allowed this hole
> in their ecosystem to exist for a decade, what I do very clearly understand
> is that Apple's safe & secure ecosystem claims are shown to be unsupported.
>
> Why does Apple say their system is safe & secure when obviously it's not?

The more I argued with them, the better I came to know their dialectic.
First they counted on the stupidity of their adversary, and then, when there
was no other way out, they themselves simply played stupid.

If all this didn't help, they pretended not to understand, or, if
challenged, they changed the subject in a hurry, quoted platitudes which, if
you accepted them, they immediately related to entirely different matters,
and then, if again attacked, gave ground and pretended not to know exactly
what you were talking about.

Whenever you tried to attack one of these apostles, your hand closed on a
jelly-like slime which divided up and poured through your fingers, but in
the next moment collected again.

But if you really struck one of these fellows so telling a blow that,
observed by the audience, he couldn't help but agree, and if you believed
that this had taken you at least one step forward, your amazement was great
the next day.

The Jew had not the slightest recollection of the day before, he rattled off
his same old nonsense as though nothing at all had happened, and, if
indignantly challenged, affected amazement; he couldn't remember a thing,
except that he had proved the correctness of his assertions the previous
day.

Sometimes I stood there thunderstruck. I didn't know what to be more amazed
at: the agility of their tongues or their virtuosity at lying.

Gradually I began to hate them.

On 2024-07-16 23:33, GLOBUS wrote:
> Wolf Greenblatt wrote:
>> On Tue, 9 Jul 2024 08:07:20 -0400, Alan Browne wrote:
>>
>>>> Three million iOS/macOS apps were vulnerable for a decade, and Apple
>>>> didn't
>>>> even care to think about backing up their own claims of safety &
>>>> security.
>>>
>>> I and others have made clear that this is not in Apple's court, and you
>>> have admitted that you don't understand 3rd party toolchains and code
>>> source, but you keep banging the same drum.
>>
>> While it's clear I don't understand how Apple could have allowed this
>> hole
>> in their ecosystem to exist for a decade, what I do very clearly
>> understand
>> is that Apple's safe & secure ecosystem claims are shown to be
>> unsupported.
>>
>> Why does Apple say their system is safe & secure when obviously it's not?
>
> The more I argued with them, the better I came to know their dialectic.
> First they counted on the stupidity of their adversary, and then, when
> there
> was no other way out, they themselves simply played stupid.
>
> If all this didn't help, they pretended not to understand, or, if

Hmm, then please do tell us how Apple are responsible for 3rd party tool
chains and orphaned 3rd party code?

As a warmup exercise, please cite a specific instance where:

- Some orphaned code, was
- taken over by a hacker, then
- modified to do harm, then
- released into the 3rd party toolchain ecosystem, thence
- integrated with the 3rd party toolchain, into
- someone else's application, that
- was released on Apple's App Store, and
- got past Apple's validity checking, into
- the wild, and (for bonus points)
- caused harm.

Provide links.

--
"It would be a measureless disaster if Russian barbarism overlaid
the culture and independence of the ancient States of Europe."
Winston Churchill

On 2024-07-17 14:37, Alan Browne wrote:

>> was no other way out, they themselves simply played stupid.
>>
>> If all this didn't help, they pretended not to understand, or, if
>
> Hmm, then please do tell us how Apple are responsible for 3rd party tool
> chains and orphaned 3rd party code?
>
> As a warmup exercise, please cite a specific instance where:
>
> - Some orphaned code, was
> - taken over by a hacker, then
> - modified to do harm, then
> - released into the 3rd party toolchain ecosystem, thence
> - integrated with the 3rd party toolchain, into
> - someone else's application, that
> - was released on Apple's App Store, and
> - got past Apple's validity checking, into
> - the wild, and (for bonus points)
> - caused harm.
>
> Provide links.

<chirp><chirp><chirp>

Hmm, all I hear is crickets.

--
"It would be a measureless disaster if Russian barbarism overlaid
the culture and independence of the ancient States of Europe."
Winston Churchill

Alan Browne wrote:
> On 2024-07-17 14:37, Alan Browne wrote:
>
>>> was no other way out, they themselves simply played stupid.
>>>
>>> If all this didn't help, they pretended not to understand, or, if
>>
>> Hmm, then please do tell us how Apple are responsible for 3rd party tool
>> chains and orphaned 3rd party code?
>>
>> As a warmup exercise, please cite a specific instance where:
>>
>> - Some orphaned code, was
>> - taken over by a hacker, then
>> - modified to do harm, then
>> - released into the 3rd party toolchain ecosystem, thence
>> - integrated with the 3rd party toolchain, into
>> - someone else's application, that
>> - was released on Apple's App Store, and
>> - got past Apple's validity checking, into
>> - the wild, and (for bonus points)
>> - caused harm.
>>
>> Provide links.
>
> <chirp><chirp><chirp>
>
> Hmm, all I hear is crickets.
>

I was describing Wolf Greenblatt.

On 2024-07-18 20:14, GLOBUS wrote:
> Alan Browne wrote:
>> On 2024-07-17 14:37, Alan Browne wrote:
>>
>>>> was no other way out, they themselves simply played stupid.
>>>>
>>>> If all this didn't help, they pretended not to understand, or, if
>>>
>>> Hmm, then please do tell us how Apple are responsible for 3rd party
>>> tool chains and orphaned 3rd party code?
>>>
>>> As a warmup exercise, please cite a specific instance where:
>>>
>>> - Some orphaned code, was
>>> - taken over by a hacker, then
>>> - modified to do harm, then
>>> - released into the 3rd party toolchain ecosystem, thence
>>> - integrated with the 3rd party toolchain, into
>>> - someone else's application, that
>>> - was released on Apple's App Store, and
>>> - got past Apple's validity checking, into
>>> - the wild, and (for bonus points)
>>> - caused harm.
>>>
>>> Provide links.
>>
>> <chirp><chirp><chirp>
>>
>> Hmm, all I hear is crickets.
>>
>
> I was describing Wolf Greenblatt.

Doh! Sorry.

--
"It would be a measureless disaster if Russian barbarism overlaid
the culture and independence of the ancient States of Europe."
Winston Churchill