user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: Re: libgmime experiences? (was: [PATCH] doc: update HACKING and TODO ...)
Date: Sat, 16 Nov 2019 02:50:27 +0000	[thread overview]
Message-ID: <20191116025027.GA8203@dcvr> (raw)
In-Reply-To: <20190921224003.GA21832@dcvr>

Eric Wong <> wrote:
> I've never used gmime as a user or hacker...

I still haven't used it as a user.

> However, looking at the Debian changelogs, there's only been one
> CVE (CVE-2010-0409) from nearly a decade ago.  Maybe all the
> bugs are fixed, or nobody really abuses it.

gmime 3.2.5 just came out which addresses stack exhaustion:

(but there may be more work to do in that area...)

      reply	other threads:[~2019-11-16  2:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-21  0:06 [PATCH] doc: update HACKING and TODO with a few items Eric Wong
2019-09-21 22:40 ` libgmime experiences? (was: [PATCH] doc: update HACKING and TODO ...) Eric Wong
2019-11-16  2:50   ` Eric Wong [this message]

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:

  List information:

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

  git send-email \
    --in-reply-to=20191116025027.GA8203@dcvr \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).