-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/09/2014 10:42 AM, Alex Legler wrote: > On 09.01.2014 01:08, Chris Reffett wrote: >> On 01/07/2014 08:42 PM, Tobias Heinlein wrote: >>> On 08.01.2014 02:40, Tobias Heinlein wrote: >>>> Our new approach works more like a whitelist; >> >>> "more like a blacklist", that is. >> >> >> I kind of would like the workaround field to remain (but perhaps >> be optional) since I have seen a few vulns that actually did >> have functional workarounds. Not absolutely necessary. >> > > Does it need to have its own field, can't it be part of the > (temporary) resolution? > >> Chris Reffett >> > I guess it would work as part of the resolution, perhaps we could have a template for "A temporary fix for this issue is also available: ..." for that. Didn't think of that. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iKYEARECAGYFAlLOw+RfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldEM2NzU5RjUyMDczREJDQkVDQTBDRkE1NERC Nzk1QThBNDI2MTgzNTQACgkQ23laikJhg1SKEgCeLuRlJxXSQFNDpVH23uXlrBEQ tFcAnRLbKzzL5KSWHpfu4LX0SxJA0jWA =92Vy -----END PGP SIGNATURE-----
