From: Alexander Holler <holler@ahsoftware.de>
To: gentoo-security@lists.gentoo.org
Subject: [gentoo-security] Re: Trolling (was: Gentoo's security)
Date: Mon, 08 Nov 2004 05:36:25 +0100 [thread overview]
Message-ID: <418EF7C9.2090701@ahsoftware.de> (raw)
In-Reply-To: <200411081140.09816.jstubbs@work-at.co.jp>
Jason Stubbs wrote:
> On Monday 08 November 2004 11:02, Alexander Holler wrote:
...
> It really seems to me like you are trolling. The first email you sent was done
> so after getting frustrated with Mike Frysinger's (vapier) closing of the
> "versioned eclasses" bug. Yet, what you are talking about here is absolutely
> nothing to do with that. You made most of the same statements on the bug, but
> they were off-topic in that bug's context as well. Furthermore, there is
> already another bug open for that off-topicness.
Yes I'm trolling and I doesn't take care about opening and writing tons
of bugs if they got ignored or closed as worksforme/wontfix. I've
written enough bugs and somewhere came to the point that written bugs is
a useless spend of time.
In the bug I mentioned in my second post, I explain that the trojan for
ebuilds is also usable on eclasses (which I've missed because they where
relativly new and I've never used them). Ok, unrelated according to you.
And the second post, I also have reminder on the first post, where the
first bug is mentioned where I explain how a list with hashes would
help. Ok, very complicated and unrelated too.
> So, let me give you an account of where I see things are at:
> * SHA1 support is in portage but can't be enabled yet due to compatibility
> issues. That is, enabling it will prevent user's running <portage-2.0.51
> from being able to upgrade.
I still don't understand why just building a list with hashes (maybe
signed) takes over 2 years.
> * Ebuild signing support is in portage and is starting to be adopted.
> Presently, there is a push for developer education.
> * CVS portage now runs most ebuild phases as the portage user rather than
> root and work is being done to support the last few as well.
> * Eclass, package and profile signing are all currently being worked on (and
> had begun before you started trolling)
You don't have to repeat that "trolling'. I think everyone has
understood where gentoo is going too. emerge moo!
> The thing you seem to keep coming back to is why it hasn't already been
> completed. You've been given the answer to that several times - lack of time
> and higher priority issues. What I really would like to know is why you are
Things like FEATURES="candy"?
> trying to tie up so much more of the time of the people that you would have
> implement support for these critical features with these pointless emails?
Yes I'm totally pointless. It is unbelievable, but I'm too thinking that
eclasses are totally breaking the ebuild-versioning scheme. I'm so
pointless, I can't explain why.
Sorry, but as a troll I am, I'm now really leaving this list alone. I
have to troll.
Trolling,
Alexander
--
gentoo-security@gentoo.org mailing list
next prev parent reply other threads:[~2004-11-08 4:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 2:02 [gentoo-security] Gentoo's security Alexander Holler
2004-11-08 2:40 ` Jason Stubbs
2004-11-08 4:36 ` Alexander Holler [this message]
2004-11-08 4:50 ` [gentoo-security] Re: Trolling (was: Gentoo's security) Jason Stubbs
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=418EF7C9.2090701@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=gentoo-security@lists.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