Re: How to handle the case with no CVE

2016-05-26 Thread Ola Lundqvist
Thanks a lot! // Ola On Thu, May 26, 2016 at 12:32 PM, Salvatore Bonaccorso wrote: > Hi Ola, > > On Thu, May 26, 2016 at 12:27:32PM +0200, Ola Lundqvist wrote: > > Hi Salvatore > > > > Thanks for quick answer. > > > > Yes I have seen that and uploaded to the archive. I guess it has not been > >

Re: How to handle the case with no CVE

2016-05-26 Thread Salvatore Bonaccorso
Hi Ola, On Thu, May 26, 2016 at 12:27:32PM +0200, Ola Lundqvist wrote: > Hi Salvatore > > Thanks for quick answer. > > Yes I have seen that and uploaded to the archive. I guess it has not been > processed yet. https://lists.debian.org/debian-lts-changes/2016/05/msg00063.html Regards, Salvatore

Re: How to handle the case with no CVE

2016-05-26 Thread Salvatore Bonaccorso
Hi Ola, On Thu, May 26, 2016 at 12:27:32PM +0200, Ola Lundqvist wrote: > Hi Salvatore > > Thanks for quick answer. > > Yes I have seen that and uploaded to the archive. I guess it has not been > processed yet. > > A CVE request was made half a year ago, but none assigned that I could find. Yes

Re: How to handle the case with no CVE

2016-05-26 Thread Ola Lundqvist
Hi Salvatore Thanks for quick answer. Yes I have seen that and uploaded to the archive. I guess it has not been processed yet. A CVE request was made half a year ago, but none assigned that I could find. Regarding the addition if a line to data/CVE/list. Shall I add it to a dummy id because the

Re: How to handle the case with no CVE

2016-05-26 Thread Salvatore Bonaccorso
Hi, On Thu, May 26, 2016 at 12:11:42PM +0200, Ola Lundqvist wrote: > Hi > > I have now fixed ruby-mail and the problem described there did not have a > CVE identifier. > See here: > https://security-tracker.debian.org/tracker/source-package/ruby-mail > Instead it has a TEMP-000-8B2928 identif

How to handle the case with no CVE

2016-05-26 Thread Ola Lundqvist
Hi I have now fixed ruby-mail and the problem described there did not have a CVE identifier. See here: https://security-tracker.debian.org/tracker/source-package/ruby-mail Instead it has a TEMP-000-8B2928 identifier. How do I mark that one as fixed? I could not add TEMP-... to to gen-DLA com