Latest versions of cdrecord, xcdroast, k3b can't burn my CDs

I updated my FC2 system last night with the new versions of CD burner
software that was release yesterday... and this morning...

I can't burn CDs any more.  I'm not sure I can blank CDs either.

I noticed that I had to go through the xcdroast setup procedure again.

Its progress bars don't work for me anymore, and the result
of a burn, is not mountable.

When I try k3b, it causes my CD burner to drive the head into
the end stops (not a nice sound), and I get the same bad
result.  The first time, it couldn't even complete the burn,
and the second time, it completed, but again it was un-mountable.

I know one other person, who can't burn CDs anymore too,
so its not just me.

Comments??

[Pybe]

On Thu, 30 Sep 2004 12:27:13 -0400, [e-mail]
 wrote:
> I know one other person, who can't burn CDs anymore too,
> so its not just me.

Hell I havent been able to burn cd's for ages, just got cdrecord to
work again with help from here. I will try the updates and report back
as it cant be worse than it is already. Maybe it will fix my problem
=)

Pybe

[Aly Dharshi]

Are you using the most recent kernel aka 2.6.8.x series ?

Pybe wrote:
> On Thu, 30 Sep 2004 12:27:13 -0400, [e-mail]
>  wrote:
> > I know one other person, who can't burn CDs anymore too,
> > so its not just me.
>
> Hell I havent been able to burn cd's for ages, just got cdrecord to
> work again with help from here. I will try the updates and report back
> as it cant be worse than it is already. Maybe it will fix my problem
> =)
>
> Pybe

[Schlueri]

Am Do, den 30.09.2004 schrieb [e-mail] um 18:27:
> Comments??

I'm fully updated, too (kernel-2.6.8-1.521).
Today, after the update, i burned with k3b, works, but still only as
root. k3b doesn't find any burner as user.

What does this mean, in detail?

---------------------------------------------------------------------
Update Information:

Updated due to new kernel scsi filtering.

---------------------------------------------------------------------

[Tom Mitchell]

On Thu, Sep 30, 2004 at 06:45:16PM +0200, Schlueri wrote:
> Am Do, den 30.09.2004 schrieb [e-mail] um 18:27:
> Today, after the update, i burned with k3b, works, but still only as
> root. k3b doesn't find any burner as user.
> What does this mean, in detail?
> Updated due to new kernel scsi filtering.

The key to the details is that access to the special hardware commands
that are needed to burn CDROMs also gives access to special commands
that permit trashing other disks.

The result is that any user that had permission to burn the cdrom also
had access to the low level commands that can trash the entire system.

To eliminate ANY POSSIBILITY of a trashed system the low level
stuff was blocked as soon as the risk was understood.

The "SCSI filtering" is a reference to code that validates
specific commands as being safe or appropriate for the device.
Eventually the filter will validate and pass the correct
stuff in the correct limited context.

I must admit that I have modified my X-roast icon to use 'sudo' tricks
to make it appear simple.  I did not like the idea of making is SUID.

Some changes just arrived in the test world, I am about to undo the
sudo thing and tinker/explore...

Since the risk was so grave I think that the right thing
has and is being done by all involved.  Stay current and
keep a couple of old bits handy to smooth the bumps.

[Matthew Miller]

On Thu, Sep 30, 2004 at 04:29:43PM -0700, Nifty Hat Mitch wrote:
> I must admit that I have modified my X-roast icon to use 'sudo' tricks
> to make it appear simple.  I did not like the idea of making is SUID.

FWIW, usermode/consolehelper would be another approach to this same
workaround.

[Tom Mitchell]

On Thu, Sep 30, 2004 at 07:32:13PM -0400, Matthew Miller wrote:
> On Thu, Sep 30, 2004 at 04:29:43PM -0700, Nifty Hat Mitch wrote:
> > I must admit that I have modified my X-roast icon to use 'sudo' tricks
> > to make it appear simple.  I did not like the idea of making is SUID.
>
> FWIW, usermode/consolehelper would be another approach to this same
> workaround.

Yes it would.

This need for a work arround should go away so I did not wish to
invest very much time.