On Wed, Sep 29, 2021 at 12:42:56PM -0600, Sam Hartman wrote:
> There's a chain of signatures for the installed files, and so you could
> presumably validate that the installed files have not been modified.
> That is much more challenging for files generated from the postinst.
I wondered about repr
> "Paul" == Paul Wise writes:
Paul> On Wed, Sep 29, 2021 at 8:25 AM Bastian Blank wrote:
>> All Python source is compiled into bytecode during installation.
Paul> Scripts in the bin/ directories are not compiled into
Paul> bytecode, and there are a number of packages that do
On Wed, Sep 29, 2021 at 8:25 AM Bastian Blank wrote:
> All Python source is compiled into bytecode during installation.
Scripts in the bin/ directories are not compiled into bytecode, and
there are a number of packages that do not compile .py files into
bytecode:
https://lists.debian.org/msgid-s
On Tue, Sep 28, 2021 at 08:37:15PM +0530, Manoj Singh wrote:
> For FIPS(federal information processing standards), required all python
> code in bytecode format(.pyc) instead of plain source .py.
All Python source is compiled into bytecode during installation.
Bastian
--
We have found all life
> "Manoj" == Manoj Singh writes:
Manoj> Hi Team, For FIPS(federal information processing standards),
Manoj> required all python code in bytecode format(.pyc) instead of
Manoj> plain source .py.
NIST publishes a lot of FIPS documents.
Can you please point to the specific version o
5 matches
Mail list logo
