From: "G.B." <bauhaus@notmyhomepage.invalid>
Subject: Re: Test for constant (or "in parameter" in procedure)
Date: Thu, 9 Feb 2017 18:31:41 +0100
Date: 2017-02-09T18:31:41+01:00 [thread overview]
Message-ID: <o7i8ui$jge$1@dont-email.me> (raw)
In-Reply-To: <o7i86r$1qul$1@gioia.aioe.org>
On 09.02.17 18:17, Dmitry A. Kazakov wrote:
>> Maybe SPARK has an answer.
>
> Rather the OS. Set the ads file read-only. Calculate its signature (of military-grade length). Store the signature on an encrypted flash drive protected by biometric scanner. Verify the signature each 5 seconds to detect malicious source code modifications by intruders...
Alternatively, you could store each line of source text
in a DBMS that offers access control to rows, or if each
spec lives in a separate table, to tables, etc.
Then, have rights grated to team members accordingly.
If working on Windows™, the object based UAC system could
be used for associating rights with file objects, per user.
next prev parent reply other threads:[~2017-02-09 17:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 4:38 Test for constant (or "in parameter" in procedure) reinkor
2017-02-09 12:11 ` AdaMagica
2017-02-09 12:46 ` reinkor
2017-02-09 13:09 ` Dmitry A. Kazakov
2017-02-09 14:10 ` AdaMagica
2017-02-09 15:01 ` reinkor
2017-02-09 16:51 ` G.B.
2017-02-09 16:59 ` reinkor
2017-02-09 17:17 ` Dmitry A. Kazakov
2017-02-09 17:31 ` G.B. [this message]
2017-02-09 18:46 ` Niklas Holsti
2017-02-10 7:48 ` reinkor
2017-02-09 18:03 ` Jeffrey R. Carter
2017-03-26 20:57 ` Norman Worth
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox