Verizon (FiOS) (Off Topic?) I have it!

[Fred]

On Tuesday 24 January 2006 09:23, Ben Scott wrote:
> On 1/24/06, Fred <puissante at lrc.puissante.com> wrote:
> > Just got set up with Fios ...
>
>   First, thank you for posting that.  The technical details were very
> interesting, and the commentary on what Verizon said, and the on-site
> service they delivered, were equally so.  I'm frankly amazed to hear
> Verizon delivering such good service.
>
>   Next, I'm going to respond to a few of your statements that all
> ultimately fall under the category heading of "Information Assurance"
> -- what most people mean when they say "security".  There may be some
> mildly harsh words ahead.  Don't take it  too personally; I'm trying
> to offer an honest critique.

Go for it Scott, you security czar!
Besides, I have rather thick skin.

...
>   I've been told all sorts of things by all manner of sales reps over
> the years.  I'm sure you have, too.  Then when push comes to shove,
> they say, "I'm sorry, sir, the representative you were speaking to was
> mistaken."  Verbal assurances are not worth the paper they're written
> on.

I know. As I said, I don't trust them, but I'm willing to give then another 
chance for now.

>   You repeatedly state your Internet feed is of a critical nature.  If
> you really mean that, I suggest obtaining a written SLA (Service Level
> Agreement) guaranteeing what you need.  I'd be willing to bet Verizon
> will refuse to provide such.

Interesting idea, and you are probably correct. However, let me see.

>   Point being: Big nasty evil ugly companies like Verizon are
> notorious for pulling the rug out from under people.  If you're
> willing to take their word for it when their written documents say
> otherwise, you may well end up deserving what you get.

If they do, I can always go back to Crumcast with tail tucked under...

> > Comcast gave me
> > hell recently about having port 80 open on my line (I was running a test
> > web server and left it open) as well as spooking me out about knowing I
> > was running multiple ssh connections *on a different port other than 22*
> > and some other things as well. What, they were monitoring my connection
> > and sniffing my packets?????
>
>   More then likely, after they discovered an open listener for a
> well-known service they explicitly forbid.  ISPs run sniffers all the
> time.  This should not be a surprise.

That they do sniffing does not surprise me. That they singled me out in 
particular, especially since I had that port open for *years* does.

> > I am *so glad* my email goes out encrypted across
> > an ssl connection between my workstations and my dedicated servers.
>
>   Ummm.... yah.  Email.
>
> "Using encryption on the Internet is the equivalent of arranging an
> armored car to deliver credit card information from someone living in
> a cardboard box to someone living on a park bench." -- Gene "spaf"
> Spafford

Yes, I know, but at least I know no one at Verizon or Comcast will be able to 
see the packets. Why make it easy for them? If someone wants to see what I 
wrote they'll have to go out to California and intercept the packets there, 
or target the destination. They just won't be able to go to the local 
Verizon/Comcast office and grab them.

There are no perfect secure solutions other than not connecting to the 
Internet at all. And even then...

> http://en.wikipedia.org/wiki/Security_theatre
>
> > Besides I can download them with
> > BitTorrent if I must.
>
>   Given the current legal climate with the media cartel suing everyone
> they can find, you might want to think twice before posting about
> downloading pirated content in a public forum such as this one.  (But
> hey, at least the connection to your mail relay was encrypted before
> you broadcasted it to the entire world.)

Of course, I did not say it was illegal. For all you know I might be talking 
about something on NPR or the like. For shows, I usually go buy the DVD sets 
anyway, if available. Most of what I'm interested in is pretty obscure and 
eclectic and not always available in mainstream outlets.

>   There's paranoia, and then there is risk management.  Paranoia is
> thinking everyone is out to get you, and responding erratically in
> ways that don't really help.

Well, in those days where I were NOT paranoid and they DID come out to get 
me, they caught me unawares and I did not handle those instances properly. 
This time, I'm prepared, but don't know where or when they'll strike next.

> Risk management is thinking everyone 
> is out to get you, and taking appropriate countermeasures to defend
> against identified threats.  It appears you are doing more of the
> former then the latter.

Well, as always, I never tell the *whole* story in open forums except on rare 
occasions...

> -- Ben "Yah, I'm an asshole" Scott

I appreciate your candor.

-Fred