Processing commands for [EMAIL PROTECTED]:
> severity 500461 important
Bug#500461: libtidy-ruby1.8: SecurityError raised by Tidy.open on ruby1.8
1.8.7.72-1
Severity set to `important' from `grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Deb
severity 500461 important
thanks
On Fri, Oct 10, 2008 at 9:41 PM, Gunnar Wolf <[EMAIL PROTECTED]> wrote:
> Before anything else: This bug is marked as "grave", because it
> "renders package unusable". Dmitry, I'd downgrade the bug's severity,
> as the package is perfectly usable as long as you don
Before anything else: This bug is marked as "grave", because it
"renders package unusable". Dmitry, I'd downgrade the bug's severity,
as the package is perfectly usable as long as you don't raise
$SAFE. Of course, it _is_ a bug, and it _should_ be fixed, but I don't
see it as grave.
Umh... I'm try
On Fri, Oct 3, 2008 at 10:43 PM, Arnaud Cornet <[EMAIL PROTECTED]> wrote:
> I can have libtidy-ruby work correcly at least on some cases. So this
> probably needs more information on how to reproduce.
>
> Typically, in the source package, running test/usage.rb instanciates a
> Tidy object and does
I can have libtidy-ruby work correcly at least on some cases. So this
probably needs more information on how to reproduce.
Typically, in the source package, running test/usage.rb instanciates a
Tidy object and does not raise any security exception.
--
Arnaud Cornet
--
To UNSUBSCRIBE, email
Package: libtidy-ruby1.8
Version: 1.1.2-3
Severity: grave
Justification: renders package unusable
Tags: upstream, help
As reported on ruby-talk ML[0], any attempt to initialize Tidy object
fails with the following exception:
SecurityError: Insecure operation - call
Backtrace:
(eval):5:in `call'
(
6 matches
Mail list logo