From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 16687] Desktop corruption when enabling Desktop Effects
Date: Sun, 15 May 2011 10:54:25 -0700 (PDT) [thread overview]
Message-ID: <20110515175425.83FCB13004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-16687-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=16687
--- Comment #12 from almos <aaalmosss@gmail.com> 2011-05-15 10:54:25 PDT ---
Is this problem still around? According to comments #6 and #9 it is fixed in
the currently preferred codepath (KMS/DRI2/EXA).
> Sadly, Mozilla's opinion is that security comes from paying shitloads of
> money to VeriSign. Hopefully they'll see the sense in publishing the
> CACert CA, and we'll have a CACert certificate, which will validate.
This is a known design flaw of SSL. See
http://blog.thoughtcrime.org/ssl-and-the-future-of-authenticity
for more information.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next parent reply other threads:[~2011-05-15 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16687-502@http.bugs.freedesktop.org/>
2011-05-15 17:54 ` bugzilla-daemon [this message]
2014-05-24 20:48 ` [Bug 16687] Desktop corruption when enabling Desktop Effects bugzilla-daemon
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=20110515175425.83FCB13004E@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).