From: Wu Fengguang <fengguang.wu@intel.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: alsa-info security/privacy concerns
Date: Wed, 7 Jan 2009 16:33:06 +0800 [thread overview]
Message-ID: <20090107083306.GA5282@localhost> (raw)
In-Reply-To: <Pine.LNX.4.61.0901070920060.8273@tm8103.perex-int.cz>
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?
Thanks,
Fengguang
next prev parent reply other threads:[~2009-01-07 8:33 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 [this message]
2009-01-07 9:04 ` Takashi Iwai
2009-01-07 9:14 ` Wu Fengguang
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=20090107083306.GA5282@localhost \
--to=fengguang.wu@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox