Hi all,
if you allocate memory, e.g. via malloc(3), then it is automatically set
to zero. This is actually a security feature quite common nowadays. I
would like to know when this feature has made it into Fedora or in RHEL.
Is this a mandatory feature of some security policy as e.g. the Common
Cri
On Fr, 2010-08-06 at 09:37 -0700, Rick Stevens wrote:
> On 08/06/2010 07:44 AM, Stefan Schulze Frielinghaus wrote:
> > Hi all,
> >
> > if you allocate memory, e.g. via malloc(3), then it is automatically set
> > to zero. This is actually a security feature quite common
On Sa, 2010-08-07 at 09:43 -0700, Ulrich Drepper wrote:
[...]
> Anonymous memory returned by mmap must be cleared. Memory provided by
> sbrk can be cleared and it is on Linux.
I found a couple of messages at the LKML where they talk about zeroing
memory. For example this one:
http://marc.info/?l
Hi all,
How can I list all packages which have a *build* requirement on package
foo? AFAIK build requirements are not stored as meta data in RPM files.
Thus, repoquery won't help. The only option I am aware of would be to
download all SPEC files and search for build requirements manually. Any
othe
On Mon, Aug 19, 2019 at 12:47:20PM -0400, Todd Zullinger wrote:
> Hi,
>
> Stefan Schulze Frielinghaus wrote:
> > How can I list all packages which have a *build* requirement on package
> > foo? AFAIK build requirements are not stored as meta data in RPM files.
> > Thus
