Re: GCC reporting piped input as a security feature

Zack Weinberg wrote: On Tue, Apr 9, 2024, at 11:35 PM, Jacob Bachmeyer wrote: Jan Engelhardt wrote: On Tuesday 2024-04-09 05:37, Jacob Bachmeyer wrote: In principle it could be posible to output something different to describe this stramge situation explicitly. For instance, o

Re: GCC reporting piped input as a security feature

On Tue, Apr 9, 2024, at 11:35 PM, Jacob Bachmeyer wrote: > Jan Engelhardt wrote: >> On Tuesday 2024-04-09 05:37, Jacob Bachmeyer wrote: >> In principle it could be posible to output something different to describe this stramge situation explicitly. For instance, output "via stdin" a

Re: GCC reporting piped input as a security feature

Jan Engelhardt wrote: On Tuesday 2024-04-09 05:37, Jacob Bachmeyer wrote: In principle it could be posible to output something different to describe this stramge situation explicitly. For instance, output "via stdin" as a comment, or output `stdin/../filename' as the file name. (Programs tha

Re: GCC reporting piped input as a security feature

Alan D. Salewski wrote: On 2024-04-08 22:37:50, Jacob Bachmeyer spake thus: Richard Stallman wrote: [...] In principle it could be posible to output something different to describe this stramge situation explicitly. For instance, output "via stdin" as a comment, or output `stdin/../filename'

Re: GCC reporting piped input as a security feature

On 2024-04-08 22:37:50, Jacob Bachmeyer spake thus: Richard Stallman wrote: [...] In principle it could be posible to output something different to describe this stramge situation explicitly. For instance, output "via stdin" as a comment, or output `stdin/../filename' as the file name. (Progr

Re: GCC reporting piped input as a security feature

On Tuesday 2024-04-09 05:37, Jacob Bachmeyer wrote: > >> In principle it could be posible to output something different to >> describe this stramge situation explicitly. For instance, output "via >> stdin" as a comment, or output `stdin/../filename' as the file name. >> (Programs that optimize t

Re: GCC reporting piped input as a security feature

Richard Stallman wrote: [[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > While it does not /prevent/ cracks, there is something

Re: GCC reporting piped input as a security feature (was: GNU Coding Standards, automake, and the recent xz-utils backdoor)

[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > While it does not /prevent/ cracks, there is something we can ensure > that we

Re: GCC reporting piped input as a security feature (was: GNU Coding Standards, automake, and the recent xz-utils backdoor)

[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > To avoid false positives if this test is used, we might want to add a > rule t

Re: GCC reporting piped input as a security feature (was: GNU Coding Standards, automake, and the recent xz-utils backdoor)

Richard Stallman wrote: [[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] [...] When considering any such change, we still should co