Muttley@dastardlyhq.com writes:
>On Sat, 19 Aug 2023 16:15:32 +0300
>=?UTF-8?B?T8SfdXo=?= <oguzismailuysal@gmail.com> wrote:
>>On 8/19/23 1:33 PM, Phil Carmody wrote:
>>> Ben Bacarisse <ben.usenet@bsb.me.uk> writes:
>>>> Some file systems (depending on mount options) can have complex rules
>>>> such as rejecting any name with an invalid UTF-8 sequence.
>>>
>>> Oooh, now I'm tempted to name files in Latin-1, to deliberately break
>>> filesystems that make such assumptions!
>>Be careful with that attitude. The "memory-safe" sudo replacement
>>doesn't support non-UTF-8 input either:
>
>Whats memory unsafe about sudo?
>
https://www.cisa.gov/news-events/alerts/2021/02/02/sudo-heap-based-buffer-overflow-vulnerability-cve-2021-3156

On Sun, 20 Aug 2023 17:24:46 GMT
scott@slp53.sl.home (Scott Lurndal) wrote:
>Muttley@dastardlyhq.com writes:
>>On Sat, 19 Aug 2023 16:15:32 +0300
>>=?UTF-8?B?T8SfdXo=?= <oguzismailuysal@gmail.com> wrote:
>>>On 8/19/23 1:33 PM, Phil Carmody wrote:
>>>> Ben Bacarisse <ben.usenet@bsb.me.uk> writes:
>>>>> Some file systems (depending on mount options) can have complex rules
>>>>> such as rejecting any name with an invalid UTF-8 sequence.
>>>>
>>>> Oooh, now I'm tempted to name files in Latin-1, to deliberately break
>>>> filesystems that make such assumptions!
>>>Be careful with that attitude. The "memory-safe" sudo replacement
>>>doesn't support non-UTF-8 input either:
>>
>>Whats memory unsafe about sudo?
>>
>https://www.cisa.gov/news-events/alerts/2021/02/02/sudo-heap-based-buffer-overf
>low-vulnerability-cve-2021-3156

One bug in one version doesn't make it generally unsafe.

Muttley@dastardlyhq.com writes:
> On Sat, 19 Aug 2023 16:15:32 +0300
> =?UTF-8?B?T8SfdXo=?= <oguzismailuysal@gmail.com> wrote:
>>On 8/19/23 1:33 PM, Phil Carmody wrote:
>>> Ben Bacarisse <ben.usenet@bsb.me.uk> writes:
>>>> Some file systems (depending on mount options) can have complex rules
>>>> such as rejecting any name with an invalid UTF-8 sequence.
>>>
>>> Oooh, now I'm tempted to name files in Latin-1, to deliberately break
>>> filesystems that make such assumptions!
>>Be careful with that attitude. The "memory-safe" sudo replacement
>>doesn't support non-UTF-8 input either:
>
> Whats memory unsafe about sudo?

It's not written in a language whose extremely complicate runtime system
that's conjectured to be bug free in this respect by Really Wishful
Thinking[tm] is supposed to prevent simple memory access errors C
supports.

In article <87lee55t51.fsf@doppelsaurus.mobileactivedefense.com>,
Rainer Weikusat <rweikusat@talktalk.net> wrote:
....
>It's not written in a language whose extremely complicate runtime
>system that's conjectured to be bug free in this respect by Really
>Wishful Thinking[tm] is supposed to prevent simple memory access errors
>C supports.

What language was this quoted paragraph written in?

Preumably one in which word order doesn't matter.

--
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/Reaganomics

gazelle@shell.xmission.com (Kenny McCormack) writes:
>In article <87lee55t51.fsf@doppelsaurus.mobileactivedefense.com>,
>Rainer Weikusat <rweikusat@talktalk.net> wrote:
>...
>>It's not written in a language whose extremely complicate runtime
>>system that's conjectured to be bug free in this respect by Really
>>Wishful Thinking[tm] is supposed to prevent simple memory access errors
>>C supports.
>
>What language was this quoted paragraph written in?
>
>Preumably one in which word order doesn't matter.

Word order in German and English don't always agree.

Basically he is saying, somewhat mockingly, that because it is
not written in Rust, sudo written in C is inherently memory unsafe.

In article <g3zEM.718458$AsA.196497@fx18.iad>,
Scott Lurndal <slp53@pacbell.net> wrote:
>gazelle@shell.xmission.com (Kenny McCormack) writes:
>>In article <87lee55t51.fsf@doppelsaurus.mobileactivedefense.com>,
>>Rainer Weikusat <rweikusat@talktalk.net> wrote:
>>...
>>>It's not written in a language whose extremely complicate runtime
>>>system that's conjectured to be bug free in this respect by Really
>>>Wishful Thinking[tm] is supposed to prevent simple memory access errors
>>>C supports.
>>
>>What language was this quoted paragraph written in?
>>
>>Preumably one in which word order doesn't matter.
>
>Word order in German and English don't always agree.
>
>Basically he is saying, somewhat mockingly, that because it is
>not written in Rust, sudo written in C is inherently memory unsafe.

OK, thanks.

I am glad that you were able to intuit that "Rust" was "the other language"
involved in the comparison.

--
They say compassion is a virtue, but I don't have the time!

- David Byrne -

On Mon, 21 Aug 2023 01:26:36 GMT
scott@slp53.sl.home (Scott Lurndal) wrote:
>gazelle@shell.xmission.com (Kenny McCormack) writes:
>>In article <87lee55t51.fsf@doppelsaurus.mobileactivedefense.com>,
>>Rainer Weikusat <rweikusat@talktalk.net> wrote:
>>...
>>>It's not written in a language whose extremely complicate runtime
>>>system that's conjectured to be bug free in this respect by Really
>>>Wishful Thinking[tm] is supposed to prevent simple memory access errors
>>>C supports.
>>
>>What language was this quoted paragraph written in?
>>
>>Preumably one in which word order doesn't matter.
>
>Word order in German and English don't always agree.
>
>Basically he is saying, somewhat mockingly, that because it is
>not written in Rust, sudo written in C is inherently memory unsafe.

To do anything low level Rust has to disable memory protection (or whatever
they call it) anyway, so its no safer than C/C++ in these circumstances.

gazelle@shell.xmission.com (Kenny McCormack) writes:
> In article <g3zEM.718458$AsA.196497@fx18.iad>,
> Scott Lurndal <slp53@pacbell.net> wrote:
>>gazelle@shell.xmission.com (Kenny McCormack) writes:
>>>In article <87lee55t51.fsf@doppelsaurus.mobileactivedefense.com>,
>>>Rainer Weikusat <rweikusat@talktalk.net> wrote:
>>>...
>>>>It's not written in a language whose extremely complicate runtime
>>>>system that's conjectured to be bug free in this respect by Really
>>>>Wishful Thinking[tm] is supposed to prevent simple memory access errors
>>>>C supports.
>>>
>>>What language was this quoted paragraph written in?
>>>
>>>Preumably one in which word order doesn't matter.
>>
>>Word order in German and English don't always agree.
>>
>>Basically he is saying, somewhat mockingly, that because it is
>>not written in Rust, sudo written in C is inherently memory unsafe.
>
> OK, thanks.
>
> I am glad that you were able to intuit that "Rust" was "the other language"
> involved in the comparison.

That's pretty obvious from the

,----
| Be careful with that attitude. The "memory-safe" sudo replacement
| doesn't support non-UTF-8 input either:
|
| https://github.com/memorysafety/sudo-rs/issues/213
`----

upthread. Rust is conjectured to be memory safe because people using it
really want to believe that the Rust runtime - some orders of magnitude
more complicated than a real lot of C programs - has not such bugs.

In article <87v8d8jrpo.fsf@doppelsaurus.mobileactivedefense.com>,
Rainer Weikusat <rweikusat@talktalk.net> wrote:
....
>,----
>| Be careful with that attitude. The "memory-safe" sudo replacement
>| doesn't support non-UTF-8 input either:
>|
>| https://github.com/memorysafety/sudo-rs/issues/213
>`----

That URL means nothing to me. But that's just me. Don't take it
personally.

--
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/Seriously

gazelle@shell.xmission.com (Kenny McCormack) writes:
> In article <87v8d8jrpo.fsf@doppelsaurus.mobileactivedefense.com>,
> Rainer Weikusat <rweikusat@talktalk.net> wrote:
> ...
>>,----
>>| Be careful with that attitude. The "memory-safe" sudo replacement
>>| doesn't support non-UTF-8 input either:
>>|
>>| https://github.com/memorysafety/sudo-rs/issues/213
>>`----
>
> That URL means nothing to me. But that's just me. Don't take it
> personally.

In this case, I suggest one of two options

1) You'll try to memorize that rs commonly means Rust. Eg, it's usually
the extension used for Rust source files.

2) You'll ask your full-time carer to click on the link for you and read
the content of the page to you.

In either case, posting more lame flames into this groups for no
conceivable reason is not going to improve your understanding of
anything.

In article <87r0nwjios.fsf@doppelsaurus.mobileactivedefense.com>,
Rainer Weikusat <rweikusat@talktalk.net> wrote:
>blah, blah, blah

I told you not to take it personally, but what do you go and do?

All I can say is that I tried to help you and to steer you in the right
direction.

--
Men rarely (if ever) manage to dream up a God superior to themselves.
Most Gods have the manners and morals of a spoiled child.

gazelle@shell.xmission.com (Kenny McCormack) writes:
> In article <87r0nwjios.fsf@doppelsaurus.mobileactivedefense.com>,
> Rainer Weikusat <rweikusat@talktalk.net> wrote:
>>blah, blah, blah
>
> I told you not to take it personally, but what do you go and do?

I'm principally interested in technical discussions, eg, about Rust and
memory safety, and sometimes motivated to try my hands at minimally
creative flames when people are trying to play the Most Importinant
Dickhead with the help of the usual boilerplate phrases.