Cygwin: doc: remove "faq.using.sshd-in-domain"

This FAQ entry has been commented out for quite some time.
Drop it.

Signed-off-by: Corinna Vinschen <[email protected]>

winsup/doc/faq-using.xml

@@ -987,75 +987,6 @@ create symlinks are just not available.
 </para>
 </answer></qandaentry>
 
-<!--
-<qandaentry id="faq.using.sshd-in-domain">
-<question><para>How do I setup sshd in a domain?</para></question>
-<answer>
-
-<para>
-If you want to be able to logon with domain accounts to a domain member
-machine, you should make sure that the "cyg_server" account under which
-the sshd service is usually running, is a domain account.  Otherwise you
-might end up with weird problems.  For instance, sshd might fail to load
-the child process when trying to login with a domain account.  A potential,
-confirmed error message is
-</para>
-
-<screen>
-  *** fatal error - unable to load user32.dll, Win32 error 1114
-</screen>.
-
-<para>
-Here's how you set up a sshd with a domain service account.
-</para>
-
-<para>
-First of all, create a new domain account called "cyg_server".  This
-account must be an administrative account, so make sure it's in the
-"Administrators" group.  Now create a domain policy which is propagated
-to all machines which are supposed to run an sshd service.  This domain
-policy should give the following user rights to the "cyg_server" account:
-</para>
-
-<screen>
-  Act as part of the operating system (SeTcbPrivilege)
-  Create a token object               (SeCreateTokenPrivilege)
-  Replace a process level token       (SeAssignPrimaryTokenPrivilege)
-</screen>
-
-<para>
-Now to install sshd on the member machine, logon to that machine as
-an admin.  Make sure the aforementioend global policy has been propagated
-to this machine.  Examine the Local Security Policy settings and, if
-necessary, call gpupdate.
-</para>
-
-<para>
-If everything looks ok, run bash.  Starting with Windows Vista, make
-sure you're running bash elevated.
-</para>
-
-<para>
-Then run ssh-host-config.  Answer all questions so that "cyg_server" is
-used to run the service.  When done, check ownership of
-<literal>/var/empty</literal> and all <literal>/etc/ssh*</literal>
-files.  All of them must be owned by "cyg_server".  If that's ok, you're
-usually all set and you can start the sshd service via
-</para>
-
-<screen>
-  $ cygrunsrv -S sshd
-</screen>
-
-<para>or</para>
-
-<screen>
-  $ net start sshd
-</screen>
-
-</answer></qandaentry>
--->
-
 <qandaentry id="faq.using.ssh-pubkey-stops-working">
 <question><para>Why does public key authentication with ssh fail after updating to Cygwin 1.7.34 or later?</para></question>
 <answer>