[perpass] YASV (Yet another spy vector)

Hugo Maxwell Connery <hmco@env.dtu.dk> Fri, 12 February 2016 19:20 UTC

From: Hugo Maxwell Connery <hmco@env.dtu.dk>
To: perpass <perpass@ietf.org>
Thread-Topic: YASV (Yet another spy vector)
Thread-Index: AQHRZckAv2eshwEF90ylThXZcIU9lw==
Date: Fri, 12 Feb 2016 19:20:01 +0000
Message-ID: <6CB05D82CE245B4083BBF3B97E2ED47016E36391@ait-pex01mbx01.win.dtu.dk>
Accept-Language: en-AU, da-DK, en-US
Content-Language: en-AU
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/perpass/Qrys6xdLTfMSWIfrI9VrN8n3btg>
Subject: [perpass] YASV (Yet another spy vector)
Precedence: list

Hi all,

A few zillion firmware locked devices have internet based communication
protocol hardware support and sit in peoples homes.

Problem A:  ! firmware

A few thousand manufacturers want access to the bulk data to 
analyse / sell, and the people purchasing/using them dont know
how to deal with firmware.

Problem B:  no privacy

The data is uploaded to Mr. X and user A gets to see  their part
only (in some summarised form -- see Faceb--k).

Solutions:

Create a standard for interoperability *in the home*.  This is not the
early internet where interoperability was paramount across the continents.
It is in the private spaces.

Create a (commercial) example of this integration in the home.

If not, see previous discussions (and many thanks for those contributions).

The other point is that the software that presents the analysis of
this collected data needs also to be available "in the home".

Effort required,

Regards,  Hugo Connery

[perpass] YASV (Yet another spy vector) Hugo Maxwell Connery