Conference bridge idiocy

Todd Radermacher todd at fofz.com
Thu Dec 13 15:41:17 PST 2001


As if that's not bad enough - the codes my latest vendor provided
were as follows:

Participant Code:		123456
Host Code:			123456n

obliviously, deducing the host code from the participant code
was a trivial task - even the sales guys figured it out!  :)

					--tr


> -----Original Message-----
> From: owner-baylisa at baylisa.org [mailto:owner-baylisa at baylisa.org]On
> Behalf Of Jim Hickstein
> Sent: Thursday, December 13, 2001 2:22 PM
> To: baylisa at baylisa.org
> Subject: Conference bridge idiocy
>
>
> I have a conference bridge where the "host" has a separate access
> code from
> the "participants", and the host code is supposed to be kept secret.
> Naturally, everyone sends both codes in the email announcing any meeting.
>
> Does this happen to you, too?  Does anybody have a cure for it?
> (Short of
> cutting off their hands, I mean.)  How about a shot at naming the root
> cause?
>
> I just got a piece of email from a Huge Telephone Company, from
> the guy who
> is _trying to sell me conference bridge service_, and he did this
> very same
> thing.  I had the nerve to point it out to him (vendors != people, after
> all), and he confirmed that he's not supposed to send the host code to
> everyone.  He _knew_, and he still did it.
>
> *sigh*
>
> -Jim,
> Looking at a pile of accounts-payable reports and slowly shaking his head.
>




More information about the Baylisa mailing list