From: Wu Fengguang <fengguang.wu@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Travis Place <wishie@wishie.net>
Subject: Re: alsa-info security/privacy concerns
Date: Wed, 7 Jan 2009 17:14:12 +0800 [thread overview]
Message-ID: <20090107091412.GA14855@localhost> (raw)
In-Reply-To: <s5hmye3sd0g.wl%tiwai@suse.de>
On Wed, Jan 07, 2009 at 11:04:31AM +0200, Takashi Iwai wrote:
> At Wed, 7 Jan 2009 16:33:06 +0800,
> Wu Fengguang wrote:
> >
> > Hi Jaroslav,
> >
> > On Wed, Jan 07, 2009 at 10:22:13AM +0200, Jaroslav Kysela wrote:
> > > On Wed, 7 Jan 2009, Wu Fengguang wrote:
> > >
> > > > Greetings,
> > > >
> > > > The auto-uploading behavior of http://www.alsa-project.org/alsa-info.sh
> > > > makes it act like a spyware.
> > >
> > > The script always prompts before the upload action, so user can break it.
> > > Just read the first dialog.
> >
> > What I'd like to add is a dedicated dialog for the warning message and
> > let users interactively choose between yes/no for uploading.
> >
> > Doesn't it sound reasonable?
>
> [Added Travis to Cc]
>
> I like the idea. We can give the following options:
>
> - the greeting dialog informs that the script collects info, waits
> for Y/N or OK button.
> - when --upload option is given, the data will be automatically
> uploaded.
> - when --no-upload option is given, the data is just stored locally
> and quit.
> - when neither options are given, show a dialog to ask to upload or
> not.
Good ideas, I'd embrace them!
Thanks,
Fengguang
prev parent reply other threads:[~2009-01-07 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 7:53 alsa-info security/privacy concerns Wu Fengguang
2009-01-07 8:22 ` Jaroslav Kysela
2009-01-07 8:33 ` Wu Fengguang
2009-01-07 9:04 ` Takashi Iwai
2009-01-07 9:14 ` Wu Fengguang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090107091412.GA14855@localhost \
--to=fengguang.wu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
--cc=wishie@wishie.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.