Windows Server 2003 Security Question

From: Des Atkinson (Des_at_metron.co.uk)
Date: 10/06/05

  • Next message: Mike Sweeney: "Re: Problems acrossed platforms."
    Date: Thu, 6 Oct 2005 10:03:11 +0100
    To: <secureshell@securityfocus.com>
    
    

    Hi,

    I have a security question please concerning the use of OpenSSH server
    on a Windows Server 2003 system that acts as the ActiveDirectory/Domain
    Controller system (let us call the domain MYDOM).

    Both my client machine (running Windows 2000 Pro at Service Pack 5) and
    the server (Windows Server 2003 Enterprise Edition at Service Pack 1)
    are running OpenSSH_4.1p1. I wish to connect between the two using
    public key authentication, and the user I am using at both ends is the
    same one called usersrv. This user was set up on the Active Directory
    machine and is therefore a domain user. So ./usersrv (i.e.
    MYDOM/usersrv) is the logon user for the sshd service.

    Now to install the OpenSSH service initially on the AD/DC system
    requires local admin rights plus the other usual special permissions for
    ./usersrv so that the service can be installed and started.

    Our requirement is that ./usersrv be demoted as soon as possible from
    the local Administrators group on the AC/DC system. Ideally this would
    be once the service was installed. However what we have found by
    experimentation is that you must make an initial OpenSSH connection
    between the client and the server and that the connecting user must have
    Admin rights on the AD/DC system. Once that is done you can then demote
    the ./userv user from the local Admin group on the AC/DC system.
    Thereafter public key authentication will continue to work so long as
    you use the same user at both ends (which we are). You can also stop and
    restart the sshd service successfully.

    Is there a way around this, please? We know that after demoting the
    ./usersrv user connection using password authentication, or using public
    key authentication with a different user at each end will not work -
    however that does not worry us. However is there a way that we can get
    public key authentication to work first time using the same domain user
    at each end where that user does not have local admin rights on the
    AC/DC Windows Server?

    *************************************
    Des Atkinson
    Technical Director
    Metron Technology Ltd.
    Osborne House, Trull Road
    Taunton, TA1 4PX
    tel: +44 (0)1823 259231
    fax: +44 (0)1823 334502
    e-mail: desa@metron.co.uk
    www: http://www.metron.co.uk/
    **************************************
    Views expressed are those of the sender only
    & should not be taken as company policy.
    **************************************


  • Next message: Mike Sweeney: "Re: Problems acrossed platforms."

    Relevant Pages

    • Broken DC due to changes regarding privileges (OpenSSH)
      ... I am trying to get OpenSSH working on a Windows Server 2003 with public key ... I am trying to get OpenSSH to work on both. ... create a token object as well as replacing process level tokens. ... create a user account, put him into the administrators group and give him the ...
      (microsoft.public.security)
    • Re: OpenSSH Windows Security
      ... to windows server 2003. ... I have successfully setup OpenSSH via cygwin on ... You need to put them in a chroot jail. ...
      (alt.computer.security)
    • Re: sftp on Windows 2003 server
      ... openssh. ... That did the trick turning a windows server into a sftp server. ...
      (comp.security.ssh)
    • Re: GPO Software Restriction
      ... Windows Server 2003 and later do have software restriction policy but it is very difficult to implement. ... On the clients the users owner of the pc is inserted in the local admin group, this because we have some procedures that does not work as normal user o power user.... ... Or can we enable only a specific domain admin account to install software? ...
      (microsoft.public.windows.server.general)
    • RE: ASP.NET application woes running on Windows Server 2003 -- securit
      ... > Windows Server 2003 Enterprise Edition. ... but it fails on this 2003 box. ... > a local admin as well as an admin on a number of other boxes. ... > Windows security for the application but simply use the standard anonymous ...
      (microsoft.public.dotnet.framework.aspnet)