From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_00EC_01C3ED7D.40BE3CD0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Windows Update downloads are signed.  The individual files within the =
packages may or may not be.  You haven't given enough info to identify =
what warning you saw and what component presented it.  For example, were =
the ones you saw presented when installing DirectX?

Rich

  "Jan van Hoek (NL)"  wrote in message =
news:VA.000001d1.0037db9f{at}xs4alldot.nl...
  >> (...) the official statement is
  >> that all SUS downloads are checked
  >> as being signed (...)

  I've seen several counter examples, of which DirectX comes to mind=20
  immediately as a relatively recent one. Admittedly, this one was=20
  not among the critical security patches. It appeared under the=20
  "recommended downloads" heading of Windows Update.

  It took me 2 to 3 popup messages that I had to confirm, before the=20
  install proceeded. It struck me as odd (to say the least) since=20
  the popup texts explain all the "not certified by MS" reasons that=20
  one could have to refuse unsigned download of whatever source.
  --=20
  -- Jan van Hoek (NL)
  -- Sat 7 Feb 2004 07:42 CET


------=_NextPart_000_00EC_01C3ED7D.40BE3CD0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Windows
Update downloads =
are=20
signed.  The individual files within the packages may or may not =
be. =20
You haven't given enough info to identify what warning you saw and what=20
component presented it.  For example, were the ones you saw =
presented when=20
installing DirectX?
 
Rich
 

  "Jan van Hoek (NL)" <janvanhoekAT{at}xs4allDOT.nl&g=">mailto:janvanhoekAT{at}xs4allDOT.nl">janvanhoekAT{at}xs4allDOT.nl&g=
t;=20
  wrote in message news:VA.000001d1.0037db9f=
{at}xs4alldot.nl...>>=20
  (...) the official statement is>> that all SUS
downloads are =

  checked>> as being signed
(...)I've seen several =
counter=20
  examples, of which DirectX comes to mind immediately as a =
relatively=20
  recent one. Admittedly, this one was not among the critical =
security=20
  patches. It appeared under the "recommended
downloads" heading of =
Windows=20
  Update.It took me 2 to 3 popup messages that I had to
confirm, =
before=20
  the install proceeded. It struck me as odd (to say the least) =
since=20
  the popup texts explain all the "not certified by MS"
reasons that =
one=20
  could have to refuse unsigned download of whatever source.-- =
-- Jan=20
  van Hoek (NL)-- Sat 7 Feb 2004 07:42 =
CET

------=_NextPart_000_00EC_01C3ED7D.40BE3CD0--

--- BBBS/NT v4.01 Flag-5