Bug#649384: [Gnash-dev] Bug#649384: gnash creates world-readable cookies under /tmp

Sandro Santilli strk at keybit.net
Mon Nov 21 09:05:16 UTC 2011

On Mon, Nov 21, 2011 at 12:56:29AM +0100, Gabriele Giacone wrote:

> I'd move them under ~/.gnash [0], although I don't know what could
> remove them at the end without introducing new rc options.
> Any developers alive?
> [0] http://paste.debian.net/plain/146441

We want to keep cookies alive when we requested to create a launcher.
This is because the launcher will reference the cookie file.

I don't think we implement that but libcurl also supports
reading cookies back in, which would allow us to send cookies
obtained by Gnash http requests back to the browser if the plugin
code takes care of doing that part.

In any case, the plugin should know if we want or not a launcher
(only way to it is an env variable, and is the plugin itself creating
the launcher) so you could cleanup the cookies if no launcher was

A safe way to put them in /tmp/ is still preferrable to me.
They are not really meant to survive a single instance of the
standalone player (except for the launcher case).


  ()   Free GIS & Flash consultant/developer
  /\   http://strk.keybit.net/services.html

More information about the pkg-flash-devel mailing list