public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] {OT} Opinions on Host's Decision Please
Date: Mon, 24 Sep 2007 16:21:41 -0700	[thread overview]
Message-ID: <49bf44f10709241621i1d6bdd33p3baf918c163a6fdf@mail.gmail.com> (raw)
In-Reply-To: <49bf44f10709241451m1f5ea96j8619bb43282735a9@mail.gmail.com>

> > > > 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?
> > > >
> > > > - Grant
> > >
> > > Would it be unreasonable to tell us who this host is?  I want to make
> > > sure I don't host any sites on their system; if they can't secure their
> > > work tickets, what makes anybody think they can secure anything else?
> >
> > I'm taking a guess it's these guys:
> > http://www.theregister.co.uk/2007/09/19/layered_technologies_breach_disclosure/
> >
> > - Noven
>
> Bingo.  They sent me another message with an offer that could be what
> I asked for.  It was vague.

So much for that.

"I understand sir. Unfortunately I'm about out of rope in this
situation. The only
thing I can really provide to you at this point, is the oppertunity to
flag this for
the management team, and allow them to speak with you directly.

I'll move forward and make sure this gets marked correctly for them.

Please understand that as they work M-F 9 AM - 5 PM CST, it could be some time
before you are able to get a response from them. Your patience and
cooperation is
greatly appreciated."

- Grant
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-09-24 23:36 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
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 [this message]
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=49bf44f10709241621i1d6bdd33p3baf918c163a6fdf@mail.gmail.com \
    --to=emailgrant@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