Re: [debian-devel] Status of mICQ code audit

2003-04-28 Thread Martin Schulze
Gerfried Fuchs wrote: > * Glenn Maynard <[EMAIL PROTECTED]> [2003-04-23 03:30]: > > If someone missed a meeting because a program they installed out of > > Debian had a time bomb in it, they would be justified in questioning > > their use of Debian, not just the application. > > No. They would b

Re: [debian-devel] Status of mICQ code audit

2003-04-25 Thread Glenn Maynard
On Fri, Apr 25, 2003 at 09:24:14AM +0200, Gerfried Fuchs wrote: > * Glenn Maynard <[EMAIL PROTECTED]> [2003-04-23 03:30]: > > If someone missed a meeting because a program they installed out of > > Debian had a time bomb in it, they would be justified in questioning > > their use of Debian, not jus

Re: [debian-devel] Status of mICQ code audit

2003-04-25 Thread Travis Crump
Gerfried Fuchs wrote: * Glenn Maynard <[EMAIL PROTECTED]> [2003-04-23 03:30]: If someone missed a meeting because a program they installed out of Debian had a time bomb in it, they would be justified in questioning their use of Debian, not just the application. No. They would be justified in que

Re: [debian-devel] Status of mICQ code audit

2003-04-25 Thread Gerfried Fuchs
* Glenn Maynard <[EMAIL PROTECTED]> [2003-04-23 03:30]: > If someone missed a meeting because a program they installed out of > Debian had a time bomb in it, they would be justified in questioning > their use of Debian, not just the application. No. They would be justified in questioning their o

Re: [debian-devel] Status of mICQ code audit

2003-04-23 Thread Manoj Srivastava
On Wed, 23 Apr 2003 13:26:13 +1000, Russell Coker <[EMAIL PROTECTED]> said: > Harmful to Debian even if possibly not harmful to the user. This > could be clarified in the next DWN article on the topic (now that > Rudi has started the debate again another DWN article is probably > due anyway).

Re: [debian-devel] Status of mICQ code audit

2003-04-22 Thread Russell Coker
On Wed, 23 Apr 2003 07:25, Drew Scott Daniels wrote: > I wouldn't call it malicious, but I question the use of the word "harmful". > It should have been replaced, attributed or removed. I wondered about it > at the time but didn't comment as the article had already been released. > But maybe it can

Re: [debian-devel] Status of mICQ code audit

2003-04-22 Thread Glenn Maynard
On Tue, Apr 22, 2003 at 04:25:11PM -0500, Drew Scott Daniels wrote: > I wouldn't call it malicious, but I question the use of the word "harmful". I don't. Some people do use these applications for purposes more important than chatting with friends. If someone missed a meeting because a program t

Re: [debian-devel] Status of mICQ code audit

2003-04-22 Thread Adam Heath
On Wed, 23 Apr 2003, Richard Braakman wrote: > On Tue, Apr 22, 2003 at 04:25:11PM -0500, Drew Scott Daniels wrote: > > I wouldn't call it malicious, but I question the use of the word "harmful". > > I would definitely consider an easter egg that disables the package > to be "harmful". By contrast

Re: [debian-devel] Status of mICQ code audit

2003-04-22 Thread Richard Braakman
On Tue, Apr 22, 2003 at 04:25:11PM -0500, Drew Scott Daniels wrote: > I wouldn't call it malicious, but I question the use of the word "harmful". I would definitely consider an easter egg that disables the package to be "harmful". By contrast, an easter egg that makes a little penguin dance aroun

Re: [debian-devel] Status of mICQ code audit

2003-04-22 Thread Drew Scott Daniels
On Tue, 22 Apr 2003 23:57:25 +1000, Russell Coker wrote: > On Tue, 22 Apr 2003 23:07, Rdiger Kuhlmann wrote: > > d) the libel published in the Debian Weekly News of 2003-02-18; cf > > > > http://lists.debian.org/debian-devel/2003/debian-devel-200302/msg01391.html > > > > .. none of those can be fix

Re: [debian-devel] Status of mICQ code audit

2003-04-22 Thread Robert Lemmen
On Tue, Apr 22, 2003 at 07:36:30PM +0200, Rüdiger Kuhlmann wrote: > It's kinda overdue, which is why I'm asking. I now have the missing > translations for a few new strings so that I can activate the code that uses > them in the stable branch. But the fixes are not that many yet that waiting > for

Re: [debian-devel] Status of mICQ code audit

2003-04-22 Thread Rüdiger Kuhlmann
>--[Robert Lemmen]--<[EMAIL PROTECTED]> > On Tue, Apr 22, 2003 at 03:07:28PM +0200, Rüdiger Kuhlmann wrote: > > > couple of non-intentional errors (buffer overruns, null-dereferences, etc) > > If you really found some that haven't been fixed in the meanwhile, you could > > send them to me so that

Re: [debian-devel] Status of mICQ code audit

2003-04-22 Thread Robert Lemmen
On Tue, Apr 22, 2003 at 03:07:28PM +0200, Rüdiger Kuhlmann wrote: > > couple of non-intentional errors (buffer overruns, null-dereferences, etc) > > If you really found some that haven't been fixed in the meanwhile, you could > send them to me so that I can fix them for the next update. we wanted

Re: [debian-devel] Status of mICQ code audit

2003-04-22 Thread Russell Coker
On Tue, 22 Apr 2003 23:07, Rüdiger Kuhlmann wrote: > c) the slander on this mailing list, in particular by Steve Langasek, > Russel Cooker and Manoj Srivastava Unable to spell? Which statements made by me, Steve, and Manoj do you claim to be false? Why do you believe that I want to maliciously d

Re: [debian-devel] Status of mICQ code audit

2003-04-22 Thread Rüdiger Kuhlmann
>--[Robert Lemmen]--<[EMAIL PROTECTED]> > On Sat, Apr 19, 2003 at 09:43:05PM +0200, Martin Loschwitz wrote: > > can you please inform the list and me about the current status of the > > mICQ code audit you two wanted to do? It's been a while and I didn't > > hear anything further from you since