** Changed in: gnome-keyring (upstream)
Status: New = Invalid
--
gnome-keyring-daemon crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/130938
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs
*** This bug is a duplicate of bug 129820 ***
https://bugs.launchpad.net/bugs/129820
that's a duplicate of bug #129820 which has been fixed to gutsy
** This bug has been marked a duplicate of bug 129820
gnome-keyring-daemon crashed with SIGSEGV in strchr()
--
gnome-keyring-daemon
** Changed in: gnome-keyring (upstream)
Status: Unknown = New
--
gnome-keyring-daemon crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/130938
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs
** Bug watch removed: GNOME Bug Tracker #464859
http://bugzilla.gnome.org/show_bug.cgi?id=464859
** Bug watch added: GNOME Bug Tracker #467451
http://bugzilla.gnome.org/show_bug.cgi?id=467451
--
gnome-keyring-daemon crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/130938
The apport bugs are private by default in gutsy, that should address
your concern. Look like Kees did an error while cleaning the list of
bugs wrongly tagged a security issue, that can happen to everybody
** This bug is no longer flagged as a security issue
--
gnome-keyring-daemon crashed with
Unchecking the security option again, that looks like a simple crash and
not a vulnerability that can be exploited
--
gnome-keyring-daemon crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/130938
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
On Thu, 2007-08-09 at 07:52 +, Sebastien Bacher wrote:
Unchecking the security option again, that looks like a simple crash and
not a vulnerability that can be exploited
I wasn't sure which flag was which and erred on the side of safety.
When a bug is private to subscribers only does
On Thu, 2007-08-09 at 07:51 +, Sebastien Bacher wrote:
The apport bugs are private by default in gutsy, that should address
your concern.
Partly, yes. Sensitive data is still being exposed albeit to a smaller
group of people. But it's also only be guarded by the security of
Launchpad.
I apologize for the mistake -- I accidentally overlooked that portion of
the report; if it is any consolation, the contents of the stacktrace
were not sent out in email. Again, sorry for this disclosure.
--
gnome-keyring-daemon crashed with SIGSEGV in strchr()
On Thu, 2007-08-09 at 14:37 +, Kees Cook wrote:
I apologize for the mistake -- I accidentally overlooked that portion of
the report; if it is any consolation, the contents of the stacktrace
were not sent out in email. Again, sorry for this disclosure.
That's fair enough. Apology
it should not be possible to subscribe to a private bug if you don't
have access to it, if you find a way that would be a launchpad bug
--
gnome-keyring-daemon crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/130938
You received this bug notification because you are a member of
** Visibility changed to: Public
** This bug is no longer flagged as a security issue
--
gnome-keyring-daemon crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/130938
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
The backtrace has 'secret = 0xb7efb038 now is the time', which
I didn't notice before sending the bug. Not sure if that's the keyring
key, the bug is marked private but you might want to change it if that's
a private information
--
gnome-keyring-daemon crashed with SIGSEGV in strchr()
Thanks for your bug report. This bug has been reported to the developers
of the software. You can track it and make comments here:
http://bugzilla.gnome.org/show_bug.cgi?id=464859
** Changed in: gnome-keyring (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: New = Triaged
On Wed, 2007-08-08 at 22:55 +, Sebastien Bacher wrote:
The backtrace has 'secret = 0xb7efb038 now is the time', which
I didn't notice before sending the bug. Not sure if that's the keyring
key, the bug is marked private but you might want to change it if that's
a private
On Wed, 2007-08-08 at 22:07 +, Kees Cook wrote:
** Visibility changed to: Public
Complete with my secret in it. Thanks very much.
I really don't think it is your place to determine if a bug I marked
private is indeed private or public. I marked it private for very good
reason. I
** Visibility changed to: Private
** This bug has been flagged as a security issue
--
gnome-keyring-daemon crashed with SIGSEGV in strchr()
https://bugs.launchpad.net/bugs/130938
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
17 matches
Mail list logo
