> On Feb 28, 2017, at 3:07 AM, grarpamp wrote:
>
>> On Mon, Feb 27, 2017 at 4:53 AM, John Newman wrote:
>> Yes and no. Joe Fuckhead (or me) shouldn't have to
>> worry about my NYC travels and all data needed to
>> clone my goddamn ID getting leaked all over the
>> place.
>>
>> But who knows,
On Mon, Feb 27, 2017 at 4:53 AM, John Newman wrote:
> Yes and no. Joe Fuckhead (or me) shouldn't have to
> worry about my NYC travels and all data needed to
> clone my goddamn ID getting leaked all over the
> place.
>
> But who knows, its likely just being traded quietly and
> more privately, if s
On February 26, 2017 9:17:03 PM EST, grarpamp wrote:
>On Sun, Feb 26, 2017 at 11:02 AM, Razer wrote:
>> Security error leaves NY airport servers unprotected for a year
>> The backup storage drive hadn't been password-protected since April.
>> The 760 GB
>
>Sad that people are more interested in
On Sun, Feb 26, 2017 at 11:02 AM, Razer wrote:
> Security error leaves NY airport servers unprotected for a year
> The backup storage drive hadn't been password-protected since April.
> The 760 GB
Sad that people are more interested in making a name for themselves
by getting '[non]security commun
From: Razer
>Security error leaves NY airport servers unprotected for a year
>The backup storage drive hadn't been password-protected since April.
>The 760 GB of exposed data included TSA letters of investigation, social
security numbers, internal airport schematics and emails, according to
Security error leaves NY airport servers unprotected for a year
The backup storage drive hadn't been password-protected since April.
The 760 GB of exposed data included TSA letters of investigation, social
security numbers, internal airport schematics and emails, according to
Chris Vickery, lead
