From: "Daniel da Veiga" <danieldaveiga@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} Opinions on Host's Decision Please
Date: Fri, 21 Sep 2007 19:40:46 -0300 [thread overview]
Message-ID: <342e1090709211540i3daf5329m76c84beeaeafa3b2@mail.gmail.com> (raw)
In-Reply-To: <49bf44f10709211437l67dfa91av64dc4df6b25fa385@mail.gmail.com>
On 9/21/07, Grant <emailgrant@gmail.com> wrote:
> Hello,
>
> As I have previously posted about, my host sent me an email a few days
> ago stating that support tickets for 5,000-6,000 of their clients had
> been broken into. I checked my records and found that my root
> password had previously been submitted in a support ticket. I then
> decided I needed to reinstall my system.
>
> I requested that my host allow me access to a second machine for 2-5
> days while I switch over to a clean system, after that I would turn
> the old system over to them and continue with the new system.
>
> My request was denied! I'm blown away by this. Was I asking too much?
>
Information that was valuable leaked because they screw it, so, no
matter what terms of service say, they must fix their own mistakes. If
the machine crashes, the data center is burned down to the ground or
the manager's kid pull the plug on the main server, that's a situation
where they can say "not our fault, deal with it". But in your case
their support system had a breach, and thus its their fault. They must
provide you the means to ensure that YOUR information is safe, cause
they caused the incident in the first place. You're unsure about your
information, and information is money.
If I were you I would be backing up my data by now, would then request
a physical backup and after I get it:
1) Send them email about the actions I'm about to take.
2) Move away from their services and look for a better server.
3) Write a cool blog entry about their services and how secure they are.
Of course they could answer the (1) email granting your requests and
maybe you wouldn't have to take steps (2) and (3). Happened to me
once.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-09-21 23:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 21:37 [gentoo-user] {OT} Opinions on Host's Decision Please Grant
2007-09-21 22:18 ` Novensiles divi Flamen
2007-09-21 22:36 ` Grant
2007-09-21 23:21 ` Novensiles divi Flamen
2007-09-21 22:40 ` Daniel da Veiga [this message]
2007-09-21 23:16 ` Grant
2007-09-22 3:31 ` Dale
2007-09-22 16:49 ` Dan Farrell
2007-09-22 16:54 ` Dan Farrell
2007-09-22 18:09 ` Doug Whitesell
2007-09-22 23:14 ` Novensiles divi Flamen
2007-09-24 21:51 ` Grant
2007-09-24 23:21 ` Grant
2007-09-25 1:53 ` Doug Whitesell
2007-09-25 2:11 ` Grant
2007-09-25 17:54 ` Mick
2007-09-25 18:54 ` Grant
2007-09-25 21:07 ` Dan Farrell
2007-09-25 23:00 ` Grant
2007-09-25 23:23 ` Novensiles divi Flamen
2007-09-25 23:29 ` kashani
2007-09-26 1:33 ` Dan Farrell
2007-09-26 1:31 ` Dan Farrell
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=342e1090709211540i3daf5329m76c84beeaeafa3b2@mail.gmail.com \
--to=danieldaveiga@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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