Re: [Gimp-developer] [PATCH] mandrake patches dump

2002-06-12 Thread Sven Neumann
Hi, Thierry Vignaud <[EMAIL PROTECTED]> writes: > well, bugzilla.gnome.org has dead links and lacks a patch upload tool > (unless i miss it but i don't see this possibility in submission > form). this is a bit akward. You need to submit the bug-report first. You can then go to the page that has

Re: [Gimp-developer] gimp security bug, shared memory

2002-06-12 Thread Sven Neumann
Hi, David Fries <[EMAIL PROTECTED]> writes: > Currently the shared memory region that gimp uses to communicate to > and from plugins is readable and writable by every user on the system. > This is not good. I don't know what data or control information gimp > puts in this shared region, but som

Re: [Gimp-developer] gimp security bug, shared memory

2002-06-12 Thread Michael Natterer
David Fries <[EMAIL PROTECTED]> writes: > Currently the shared memory region that gimp uses to communicate to > and from plugins is readable and writable by every user on the system. > This is not good. I don't know what data or control information gimp > puts in this shared region, but someone

[Gimp-developer] CIBLEZ ET DEMARCHEZ GRATUITEMENT VOS PROSPECTS PAR CENTAINES DE MILLIERS

2002-06-12 Thread VOTRE SITE ...
CIBLEZ ET DEMARCHEZ GRATUITEMENT VOS PROSPECTS PAR CENTAINE DE MILLIERS GRACE AU ROBOT MAIL - 5000 fois p

Re: [Gimp-developer] gimp security bug, shared memory

2002-06-12 Thread Todd T. Fries
might as well patch the configure script (which has the 0777) so that the test during configure is the same as during the application runtime ;-) -- Todd Fries .. [EMAIL PROTECTED] (last updated $ToddFries: signature.p,v 1.2 2002/03/19 15:10:18 todd Exp $) Penned by Michael Natterer on Wed, Jun

[Gimp-developer] [Fwd: Bug#149726: gimp1.2: gimp security bug, shared memory]

2002-06-12 Thread Ben Gertzfield
Here's a patch from a Debian user regarding a possible security hole in GIMP's shared memory handling. Ben --- Begin Message --- Package: gimp1.2 Version: 1.2.2-2.1 Severity: normal Tags: security patch Currently the shared memory region that gimp uses to communicate to and from plugins is r

[Gimp-developer] CIBLEZ ET DEMARCHEZ GRATUITEMENT VOS PROSPECTS PAR CENTAINES DE MILLIERS

2002-06-12 Thread VOTRE SITE ...
CIBLEZ ET DEMARCHEZ GRATUITEMENT VOS PROSPECTS PAR CENTAINE DE MILLIERS GRACE AU ROBOT MAIL - 5000 fois p

[Gimp-developer] Electron microscopy

2002-06-12 Thread Mario J. Borgnia
Hi, I currently work with special image formats used in electron microscopy. I would like to be able to open, manipulate and save those files using The Gimp. Could anybody give me some pointers on how get started writing input filters? Thanks Mario -- +-+ | Mario

Re: [Gimp-developer] [PATCH] mandrake patches dump

2002-06-12 Thread Thierry Vignaud
Sven Neumann <[EMAIL PROTECTED]> writes: > well, my position in this thread is a bit biased since me and other > GIMP developers have spent lots of their free time hunting down bugs > that turned out to be caused by buggy GTK+ themes Mandrake used to > ship. which ones ? i've only got bug report

Re: [Gimp-developer] Electron microscopy

2002-06-12 Thread Carol Spears
On 2002-06-12 at 1514.45 -0400, Mario J. Borgnia typed this mail: > Hi, > I currently work with special image formats used in electron microscopy. > I would like to be able to open, manipulate and save those files using > The Gimp. Could anybody give me some pointers on how get started writing > i

Re: [Gimp-developer] Electron microscopy

2002-06-12 Thread David Neary
Mario J. Borgnia wrote: > Hi, > I currently work with special image formats used in electron microscopy. > I would like to be able to open, manipulate and save those files using > The Gimp. Could anybody give me some pointers on how get started writing > input filters? Hi Mario, The most difficu

Re: [Gimp-developer] gimp security bug, shared memory

2002-06-12 Thread Nathan Carl Summers
On 12 Jun 2002, Michael Natterer wrote: > David Fries <[EMAIL PROTECTED]> writes: > > Yes, the plug-ins are simply forked and thus have the same uid. > The patch looks like the right thing to do to me. If nobody objects > for some reason, it will be applied to both the stable and unstable > tre