RE: Windows Vista current flaws

Lance.Druger_at_wellsfargo.com
Date: 09/27/05

  • Next message: Lance.Druger_at_wellsfargo.com: "RE: Antivirus Comparison" 
    Date: Tue, 27 Sep 2005 12:10:30 -0500
To: <security-basics@securityfocus.com>

    Considering the small user base and that this is almost a complete
    rewrite of windows there probably aren't too many active exploits. I'd
    allow it with the following caveats:

    1. He must run a local bi-directional firewall (Windows Vista firewall I
    believe is bi-directional)

    2. If exploits are uncovered he'll have to re-image the machine to the
    standard.

    3. You offer no support or assistance

    4. If you see suspicious traffic on the machine you'll kill the
    connection

    If he knows what he's doing he could just set up dual boot and you may
    or may not be able to tell what he's running. Better to be upfront than
    to push him to work around the system.

    No offence, but an un-patched XP machine is probably riskier at this
    juncture, but I'm assuming the security standards aren't that high. This
    is just my opinion.

    Lance Druger

    -----Original Message-----
    From: Jon Lawhead [mailto:samurai@berkeley.edu]
    Sent: Monday, September 26, 2005 9:01 PM
    To: security-basics@securityfocus.com
    Subject: Windows Vista current flaws

    Greetings all,

    I work in Network Security for UC Berkeley's residence halls. We have a
    list of several "minimum
    security standards" that we require all connected computers to meet
    before being allowed access to
    the network (stuff like having a firewall program, antivirus, etc). One
    of the standards involves
    having the latest patched version of a secure operating system. I have
    a user on the network who
    wishes to run a (legitimately acquired, or so he says) version of
    Windows Vista beta version.
     Before I decide on this, I wanted opinions on whether or not this is a
    good idea. My first
    instinct is to disallow any beta operating systems simply on the grounds
    that they'll be buggy by
    definition and may potentially have serious security flaws, but I can't
    find anything to back this
    up. Just wondering if I could get a few opinions on whether or not this
    is a good idea. Thanks!

    Jon Lawhead
    Network Security Coordinator
    Residential Computing
    University of California, Berkeley

  • Next message: Lance.Druger_at_wellsfargo.com: "RE: Antivirus Comparison"

    Relevant Pages

    • Re: Win98 programs compatible with WinXP?
      ... A lot of older programs DO NOT meet today's security standards, ... They are fully compatible with Windows 98, which ALSO does not meet today's ... > I play a lot of Windows 95/98 games and a lot of them will not play on xp, ... and xp is by far the worst for games. ...
      (microsoft.public.windowsxp.general)
    • Re: PID 1212 slowly maxing out?
      ... Windows 2003 servers, but could it affect Windows XP as well? ... I'm on a home network running on wireless. ... Logical Disk Manager service ...
      (microsoft.public.windowsxp.help_and_support)
    • RE: Printing from Win9x clients stops
      ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
      (microsoft.public.windows.server.sbs)
    • Re: Cant print to my Windows 98 shared printer from my XP compute
      ... >>>I can't print from the printer attached to my Windows 98 machine using my XP ... >>>Add Printer wizard and has a pipe attached, indicating a network printer. ... >>>98 machine and I can successfully ping the 98 machine from my XP laptop. ... >>>driver name showed up as UNIDRV.DLL on my XP test page when it last worked. ...
      (microsoft.public.windowsxp.network_web)
    • Re: Slow file copy to network shares Windows 7
      ... The problem is that Windows 7 copys and pastes the test ... folder containing folders and files from a network share to a network share ... performed to demonstrate that copying the test folder from a network share to ... When copied from a network location and pasted back to a network location ...
      (microsoft.public.windows.file_system)