* Recai Oktaş:
>> I'm not sure if it is worth the effort, until we have all other issues
>> sorted out.
>
> Agreed. I would be glad if you add yourself in "Uploaders" field.
> You're totally free to make any upload.
Uhm, I don't use elog myself and have zero interest in that package
beyond that
Dear all,
thanks for reporting these issues. I was completely unaware of them
until today. I will fix all things in the next days and let you know.
Best regards,
Stefan
Recai Oktaş wrote:
First of all thanks for the detailed analysis! I haven't been able to work
on elog much, due to heav
Hi,
* Florian Weimer [2006-01-24 00:07:35+0100]
> * Recai Oktaş:
>
> > I'm going to prepare an urgent sid upload for those bugs.
>
> I'm not sure if it is worth the effort, until we have all other issues
> sorted out.
Agreed. I would be glad if you add yourself in "Uploaders" field. You're
to
* Recai Oktaş:
> Thanks for the backport, unfortunately I don't have a Sarge box at the
> moment, but will try to find one.
A sarge chroot is probably good enough for this kind of package.
>> The following potential security issues have been fixed upstream, but
>> not in the sid version (there a
First of all thanks for the detailed analysis! I haven't been able to work
on elog much, due to heavy work load these days.
* Florian Weimer [2006-01-23 16:42:16+0100]
> Package: elog
> Version: 2.6.0beta2+r1716-1
> Tags: security upstream fixed-upstream
> Severity: grave
>
> First a little vers
Package: elog
Version: 2.6.0beta2+r1716-1
Tags: security upstream fixed-upstream
Severity: grave
First a little version cross-reference, based on the src/elog{,d}.c
files.
Debian CVS (elogd.c)Subversion
2.6.0beta2+r1716-1 1.717* r1445
2.5.7+r1558-3 1.558 +
6 matches
Mail list logo
