Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Nov 2016 11:59:08 -0800
From:      "Google Inc." <jimukyoku@kpa.ees.kyushu-u.ac.jp>
To:        freebsd-questions@freebsd.org
Subject:   Google Award Notification
Message-ID:  <201611181959.uAIJWGQF012443@eesserv2.ees.kyushu-u.ac.jp>

Next in thread | Raw E-Mail | Index | Archive | Help
Dear Google User,

Congratulation for being selected as a winner, find attached email with fur=
ther information.

Sergey M. Brin,
Co-Founder/Foreign Bureau Administrator.
From owner-freebsd-questions@freebsd.org  Fri Nov 18 20:00:45 2016
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C167C48F8D
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Fri, 18 Nov 2016 20:00:45 +0000 (UTC)
 (envelope-from jimukyoku@kpa.ees.kyushu-u.ac.jp)
Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org
 [IPv6:2001:1900:2254:206a::50:5])
 by mx1.freebsd.org (Postfix) with ESMTP id 3FA8E1D76
 for <freebsd-questions@freebsd.org>; Fri, 18 Nov 2016 20:00:45 +0000 (UTC)
 (envelope-from jimukyoku@kpa.ees.kyushu-u.ac.jp)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 3EC10C48F88; Fri, 18 Nov 2016 20:00:45 +0000 (UTC)
Delivered-To: questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E0B2C48F87
 for <questions@mailman.ysv.freebsd.org>; Fri, 18 Nov 2016 20:00:45 +0000 (UTC)
 (envelope-from jimukyoku@kpa.ees.kyushu-u.ac.jp)
Received: from eesserv2.ees.kyushu-u.ac.jp (ckt.ees.kyushu-u.ac.jp
 [133.5.152.101])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 98C701D65
 for <questions@freebsd.org>; Fri, 18 Nov 2016 20:00:44 +0000 (UTC)
 (envelope-from jimukyoku@kpa.ees.kyushu-u.ac.jp)
Received: from [216.45.54.23] (216.45.54.23.static.greencloudvps.com
 [216.45.54.23] (may be forged)) (authenticated bits=0)
 by eesserv2.ees.kyushu-u.ac.jp (8.14.4/8.14.4) with ESMTP id uAIJWGSd012443
 for <questions@freebsd.org>; Sat, 19 Nov 2016 05:00:42 +0900
Message-Id: <201611182000.uAIJWGSd012443@eesserv2.ees.kyushu-u.ac.jp>
MIME-Version: 1.0
Subject: Google Award Notification
To: questions@freebsd.org
From: "Google Inc." <jimukyoku@kpa.ees.kyushu-u.ac.jp>
Date: Fri, 18 Nov 2016 12:00:46 -0800
Reply-To: mikhaylovichbrinsergey@gmail.com
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Description: Mail message body
X-Content-Filtered-By: Mailman/MimeDel 2.1.23
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2016 20:00:45 -0000

Dear Google User,

Congratulation for being selected as a winner, find attached email with fur=
ther information.

Sergey M. Brin,
Co-Founder/Foreign Bureau Administrator.
From owner-freebsd-questions@freebsd.org  Fri Nov 18 20:17:08 2016
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37BE3C47936
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Fri, 18 Nov 2016 20:17:08 +0000 (UTC)
 (envelope-from byrnejb@harte-lyne.ca)
Received: from inet08.hamilton.harte-lyne.ca (inet08.hamilton.harte-lyne.ca
 [216.185.71.28])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "inet08.hamilton.harte-lyne.ca",
 Issuer "CA HLL ISSUER 01" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 0377EB36
 for <freebsd-questions@freebsd.org>; Fri, 18 Nov 2016 20:17:07 +0000 (UTC)
 (envelope-from byrnejb@harte-lyne.ca)
Received: from localhost (localhost [127.0.0.1])
 by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTP id 402B562154
 for <freebsd-questions@freebsd.org>; Fri, 18 Nov 2016 15:08:56 -0500 (EST)
X-Virus-Scanned: amavisd-new at harte-lyne.ca
Received: from inet08.hamilton.harte-lyne.ca ([127.0.0.1])
 by localhost (inet08.hamilton.harte-lyne.ca [127.0.0.1]) (amavisd-new,
 port 10024)
 with ESMTP id BZGqA2cs4Gop for <freebsd-questions@freebsd.org>;
 Fri, 18 Nov 2016 15:08:54 -0500 (EST)
Received: from webmail.harte-lyne.ca (inet04.hamilton.harte-lyne.ca
 [216.185.71.24])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by inet08.hamilton.harte-lyne.ca (Postfix) with ESMTPSA id D80CA621B5
 for <freebsd-questions@freebsd.org>; Fri, 18 Nov 2016 15:08:53 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=harte-lyne.ca;
 s=dkim_hll; t=1479499734;
 bh=E5rdRJ7sjiQnRbWTpdPfOh5lc9Qa6siu+p7ApMongX4=;
 h=In-Reply-To:References:Date:Subject:From:To:Reply-To;
 b=J+pePIr/1GgwUEMi6CKHumJYW8BGLkrwPgjvP4yXNyViUS2t4BWorcMeoDFd3dAG7
 kioV6G+nLyHNIopeGQjMsYIInt2qPYraGR6ACztW4+C9anh0n4KuxYSbj3/P35r29/
 w2C7UQmL54IvQZ/2CAE4VU1AUI2meRy7XD7doqqUawxuDv00Y5moOPEq0sD+QzpTpp
 5AtLkWEWp4A3zY3SDd8EgBRz5/JAGyUJEUFj7RbfFpBsBIdNqgrW6rKqsmkjZKsPxt
 2Bihn6K2hQD6NVqbmfO6JfTXOqSeepTJLfzB5LLAeQ7g9BWjemICZPmMPlxJ6ZqD+y
 GhsMv1ZjZSLGA==
Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll)
 by webmail.harte-lyne.ca with HTTP; Fri, 18 Nov 2016 15:08:54 -0500
Message-ID: <e435f4e60e8b855ce9338f5aaa507520.squirrel@webmail.harte-lyne.ca>
In-Reply-To: <mailman.3226.1479484184.4389.freebsd-questions@freebsd.org>
References: <mailman.3226.1479484184.4389.freebsd-questions@freebsd.org>
Date: Fri, 18 Nov 2016 15:08:54 -0500
Subject: Re: Microsoft announced it is joining The Linux Foundation?
From: "James B. Byrne" <byrnejb@harte-lyne.ca>
To: freebsd-questions@freebsd.org
Reply-To: byrnejb@harte-lyne.ca
User-Agent: SquirrelMail/1.4.22-4.el6
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2016 20:17:08 -0000


On Fri, November 18, 2016 09:59, Ralf Mardorf wrote:
> On Fri, 18 Nov 2016 14:25:47 +0000, Steve O'Hara-Smith wrote:
>>I won't be buying because I'd rather own the hardware that holds my
>>data but that's my personal preference.
>
> Your company perhaps isn't that huge. I could imagine that for huge
> companies, it's an advantage not to maintain their own server farms
> all
> over the world, but instead to pay for a company doing it for them.
> This is not my domain, I don't know how secure, or insecure this
> approach is, compared to maintaining internal server farms all over
> the
> world, but it's easy to imagine that regarding costs and maintenance
> huge companies could have reasons to pay for such a service bundle.
>
> However, while
> https://en.wikipedia.org/wiki/Microsoft_Azure#Privacy
> sounds insecure, owning intern server farms, could suffer from the
> same issues.
>
> Regards,
> Ralf
>
>


Yes there are obvious advantages. And some not so obvious problems. 
For one there is the matter of just where in the cloud is your data.
what country or countries is it in?

We have a wild-west situation at the moment. Few are paying particular
attention to this but ordinary people are getting a might sensitive to
having their financial, medical and other personal data subject to
unrestrained snooping by governments.  The cloud, in all its myriad
names, is completely, utterly and totally compromised from a data
security standpoint.  And that is by design.

We have been contacted by people that want to host our email, our
telephone system, our fax system, our accounting system, our business
operations system; and all for a fraction of the cost that it takes to
keep this stuff in house.  Of course when asked what they are doing to
prevent unauthorised snooping they all say that their security is
'state-of-the-art'. Which is pretty poor when you consider it.

They also have a rather loose concept of what 'authorised' means. 
>From reading their literature and asking some pointed questions it
evidently does not necessarily involve the courts.  It is not even
clear in which jurisdictions your data will reside and whose laws it
will be subject too.  In fact some of these 'contracts' all but say
outright that they are going to farm your data and sell whatever they
can to the highest bidders, however paltry that sum might be.

Data security is really simple when you get down to it. There are
three places where data streams are compromised: point of origin,
point of delivery and medium of exchange.  By far the most difficult
is compromising the medium of exchange.  And yet that is what gets all
the press.  Heartbleed, RSA certificates, 1024 bit vs 2048 bit, MD5
vs. SHA1 vs. SHA2. But compromising the medium of exchange is
expensive and unreliable.  It also requires a lot of people which is
the bane of covert surveillance.  Somebody always talks.

By far the best results are obtained by compromising the origin.  But
that requires overt penetration and compromise of equipment that is
usually physically secured to some degree.  And that is generally
watched over by some party that just might notice strange
transmissions going off-site. Because of its high value product it is
often attempted but, it fails far more often than it succeeds.  And
success is always fleeting.  Eventually somebody on-site twigs and the
result usually takes the form of a iron wall around their data.  Which
is usually the same thing you get after a failed attempt.

Failing compromising the origin or the exchange it is nearly just as
beneficial to compromise the delivery; and generally a lot easier. 
People tend to focus on what they directly control.  Few people worry
over much about how a client stores email messages sent to them,
however sensitive the contents. Off-site data backups frequently prove
a gaping hole in data security. In fact anything kept off-site
frequently becomes a route to compromise the internal security
systems.  Consider Home Depots experience and Target's.

Putting stuff on the cloud makes compromise of the delivery point a
trivial exercise for anyone with access to the underlying
infrastructure. And that infrastructure is not under the watchful eye
of the people whose data it stores.

If you want your enterprise to be turned into somebody's product and
save a few dollars then the easiest thing to do is turn over all of
your internal processes and data to a third party. However, the money
you save will end up being someone else's, eventually.

-- 
***          e-Mail is NOT a SECURE channel          ***
        Do NOT transmit sensitive data via e-Mail
 Do NOT open attachments nor follow links sent by e-Mail

James B. Byrne                mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?201611181959.uAIJWGQF012443>