public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ports Security
Date: Fri, 5 Sep 2003 00:17:45 -0400	[thread overview]
Message-ID: <200309050017.47227.vapier@gentoo.org> (raw)
In-Reply-To: <200309050110.44445.jk@microgalaxy.net>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 873 bytes --]

On Thursday 04 September 2003 21:10, Jan Krueger wrote:
> Hi,
>
> is there a guide like
> http://www.openbsd.org/porting.html#Security
> in progress? available?

uhh we have gentoo-hardened ... not sure what you're asking about ...

> Or even better tools bundled in a "esecurity_check":

putting this in an ebuild to be run everytime a pkg is unpacked is kind of 
dumb (no offense meant) ... we have no 'automated' ways for portage to scan 
source code looking for potential security issues, nor should there be ... 
the responsibility lies on the upstream author and the gentoo maintainer, and 
it should stop there ...
perhaps creating tools for developers to use when testing out a new pkg would 
be feasible ... then again i think if you want a 'secure' box you should 
follow the excellent work the gentoo-hardened team has put together ...
-mike

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2003-09-05  4:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-05  1:10 [gentoo-dev] Ports Security Jan Krueger
2003-09-05  4:17 ` Mike Frysinger [this message]
2003-09-05 14:13   ` Jan Krueger
2003-09-05 12:37     ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200309050017.47227.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox