From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on ip-172-31-91-241.ec2.internal X-Spam-Level: X-Spam-Status: No, score=0.0 required=3.0 tests=none autolearn=ham autolearn_force=no version=3.4.6 Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Kevin Chadwick Newsgroups: comp.lang.ada Subject: Re: US Government looking into memory safe programming Date: Tue, 26 Sep 2023 11:23:24 -0000 (UTC) Organization: A noiseless patient Spider Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Tue, 26 Sep 2023 11:23:24 -0000 (UTC) Injection-Info: dont-email.me; posting-host="3f34db6aa2e6d6afb05f2a0cdf4cdc40"; logging-data="2615141"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/CC+4mNR9oC+q2/RVGDuAArm53zYQ4oe8=" User-Agent: PhoNews/3.12.0 (Android/13) Cancel-Lock: sha1:Ho2pXzEYstE98EyCtRltadMv+9s= In-Reply-To: Xref: news.eternal-september.org comp.lang.ada:65731 List-Id: >> Or when they realize that there is only one rust compiler, and therefore >> that a single compiler virus could ruin the whole defense system. > >Good point ! > >Still some doubts about their ability to reason that far ;) Whilst I have in the past refused to use lattice semi conductor hardware due to a CDN preventing secure compiler verification, whilst apparently noone or few noticed. I assume you mean trojaned compiler code inserted upstream to disable protections or ignore unsafe code? Or do you mean utf-8 library code substitution aimed at a particular compiler? -- Regards, Kc