[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Firefox video tag
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Firefox video tag
- From: Gregory Maxwell <gmaxwell@xxxxxxxxx>
- Date: Tue, 30 Jun 2009 21:56:05 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Tue, 30 Jun 2009 21:56:07 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=30Akdu8YE88OkgJdjgSy1KoF68GDsDo+34LjDPnIN5Q=; b=k8e0jKsnZJ6Gir/Po+Ku2K9+AqR6Yw2RR+NzVBNYPT8+ooqhhnoqHdLMpAuR7vkP2/ NMcXSCNBqa/sviT8bFJjxrcDbmbmv+qwjo68+a9rOW4QPuZ7/ZAQ4ZeGcp3uSHp9B6GU L+IrYL5+P1Gs9tfaua8kYaRqZApZA3ZRQtvSU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=xbOrWtYJtFbUuOIFROTlOhJ+A5NfOQgbjhRyvKc0+69L/v0aJmCtIjw6kZ3jLg1FQ0 F4ecwOcrrBbk42ql3ZCsysdM8fuu3N/CZb65qgspFkZezYwrFUvGgQQm9mGtHybd7YzN fhP5kk/i2gRMjKZSwoqZBcKKaeVi55yjwIdrU=
- In-reply-to: <4a4a8aea.0702d00a.63cc.4299@xxxxxxxxxxxxx>
- References: <4a4a8aea.0702d00a.63cc.4299@xxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
On Tue, Jun 30, 2009 at 6:02 PM, Erilenz<erilenz@xxxxxxxxx> wrote:
> Hi,
>
> Firefox 3.5 was released today. Has anyone investigated the new video tag that
> it supports with regards to whether or not it can cause leaks with Tor?
<video> and <audio> should have exactly the same attack surface as <img> has.
Thats one of the benefits that firefox's approach of building the
codecs internally rather than invoking an external media framework
(like safari does) should have.
I've been hoping very much that tor would not ultimately need to filter these…