Re: SSC Advisory TSA-051 (T-mobile wireless and Verizon Northwest)

To: joe@xxxxxxxxxxxxxx
Subject: Re: SSC Advisory TSA-051 (T-mobile wireless and Verizon Northwest)
From: Lance James <lancej@xxxxxxxxxxxxxxxxx>
Date: Thu, 12 Aug 2004 16:34:44 -0700
Cc: bugtraq@xxxxxxxxxxxxxxxxx
In-reply-to: <3d91e7f90408112133fbd6c54@xxxxxxxxxxxxxx>
List-help: <mailto:bugtraq-help@securityfocus.com>
List-id: <bugtraq.list-id.securityfocus.com>
List-post: <mailto:bugtraq@securityfocus.com>
List-subscribe: <mailto:bugtraq-subscribe@securityfocus.com>
List-unsubscribe: <mailto:bugtraq-unsubscribe@securityfocus.com>
Mailing-list: contact bugtraq-help@xxxxxxxxxxxxxxxxx; run by ezmlm
Organization: Secure Science Corporation
References: <411A8B3A.8040202@xxxxxxxxxxxxxxxxx> <3d91e7f90408112133fbd6c54@xxxxxxxxxxxxxx>
User-agent: Mozilla Thunderbird 0.5 (X11/20040208)

Joe Eversole wrote:

On Wed, 11 Aug 2004 14:10:18 -0700, Secure Science Corporation
Advisory Notice <bugtraq@xxxxxxxxxxxxxxxxx> wrote:

Solution:
- ---------
Add 2-factor authentication (passcode requirement) by default and cease
implicit trust of Caller-ID information.



T-Mobile's messaging system (in Indianapolis, at least. I do not know
if they have migrated to a single VM system) has a setting the user
can specify to require passcode when calling from mobile phone.


Hence, by default! It is not on by default.


--je



--
Best Regards,
Lance James
Secure Science Corporation
www.securescience.com

References:
- SSC Advisory TSA-051 (T-mobile wireless and Verizon Northwest)
  - From: Secure Science Corporation Advisory Notice
- Re: SSC Advisory TSA-051 (T-mobile wireless and Verizon Northwest)
  - From: Joe Eversole

Prev by Date: Advanced usage of system() function.
Next by Date: MDKSA-2004:081 - Updated gaim packages fix remotely exploitable vulnerabilities
Previous by thread: Re: SSC Advisory TSA-051 (T-mobile wireless and Verizon Northwest)
Next by thread: Re: SSC Advisory TSA-051 (T-mobile wireless and Verizon Northwest)
Index(es):
- Date
- Thread