Re: Why not barrage of security updates for WM 2003 OS
- From: "Steve Maillet \(eMVP\)" <nospam1@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 25 Aug 2005 17:56:19 -0400
Well there's the fact that Windows Mobile 2003 devices are effectively
unsecured devices in the first place. Any application can call
SetKMode(TRUE) and SetProcPermissions(0xFFFFFFFF) and party on. But you
probably don't want to tell your client that, eh?
--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com
.
- Follow-Ups:
- Re: Why not barrage of security updates for WM 2003 OS
- From: Harry Simpson
- Re: Why not barrage of security updates for WM 2003 OS
- References:
- Why not barrage of security updates for WM 2003 OS
- From: Harry Simpson
- Re: Why not barrage of security updates for WM 2003 OS
- From: Paul G. Tobey [eMVP]
- Why not barrage of security updates for WM 2003 OS
- Prev by Date: Re: clearcommerror native exception?
- Next by Date: Apps For Creating Help Files?
- Previous by thread: Re: Why not barrage of security updates for WM 2003 OS
- Next by thread: Re: Why not barrage of security updates for WM 2003 OS
- Index(es):
