svn commit: r324296 - head/net/samba36

Jason Helfman jgh at FreeBSD.org
Wed Aug 7 15:06:59 UTC 2013


On Wed, Aug 7, 2013 at 6:42 AM, Alexey Dokuchaev <danfe at freebsd.org> wrote:

> On Wed, Aug 07, 2013 at 03:38:04PM +0200, Timur I. Bakeyev wrote:
> > Well, it's said that CVE code should be inserted there and by such a code
> > it's possible to fetch description and vulnerable versions in theory...
> But
> > true, never thought of it thoroughly..
>
> VuXML entries have too much stuff that has to be input manually, from exact
> versions vulnerable (NVidia drivers give me real PITA in this regard) up to
> writing summary excerpts, which in general case cannot be easily factored
> out from upstream CVE entry.
>
> ./danfe
>
>
I was really surprised to read this thread based on my original inquiry.
Vuxml is well-documented in the Porters Handbook, and there are plenty of
existing entries to learn from how to create an entry of your own. Beyond
this, there is a large group of committers that would be willing to review
your first attempt at making an entry and helping you to get it to a point
where it is committable.

When I was a mentee, I constantly took on new challenges that I was never
exposed to as a contributor with the flood of incoming problem reports that
were coming in. Once I took on a vulnerability, because I knew that I would
need to write a vuxml entry and learn it.

I suggest trying to write an entry. I would be more than willing to review
it, as well.

-jgh

-- 
Jason Helfman          | FreeBSD Committer
jgh at FreeBSD.org     | http://people.freebsd.org/~jgh  | The Power to Serve


More information about the svn-ports-all mailing list