X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=R3cSaO8mTFdWOmYrhy4l7WhqDHDEKq3fwHmiAJUZ28w NENfsNIWqPkvJDuCfiGGL1lkNbzKM51POOS66QaaYwm7ujqIrLC5MefP6EpWlnCn j5YBalEnvfRWMg6JXhrsT3djn3hIHaBK2f4W1SSga7xxdbLy8cUF1OXkPa+1twc4 = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=T7nTG4ODcf2edV7cZhBDJdAlrFg=; b=ZhC9Ub5iQB0oL7uK7 KEgQ6SRfdCg5o2Vd3S7NQ9lipBGxzeXaMw3puW5uyjef0o2beoz25fj8Q732HiAw 4yPAN/R+5+1zfYebZseuPBSn0CHNPdmZcsN9gH/626b3U/Ai/zPk6Pj/vpsAUM1D P12oUpvm63itu3blPBK+W7YhLw= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_50,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: etr-usa.com Message-ID: <5390204E.2050300@etr-usa.com> Date: Thu, 05 Jun 2014 01:46:22 -0600 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Cygwin-L Subject: Re: CYGWIN - As admin setup other users SSH for them? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 6/4/2014 16:05, Roger Vicker, CCP wrote: > 3) deliver the private key to the user along with the rest of the > instructions on how to use it in the provided apps. How were you planning on delivering these sensitive private keys? Via insecure email, perhaps? Use ssh as it was designed: have the users generate their own local keypairs, and have them email the public key to you. The words we use here mean something. The *public* key goes out over the public link, and the *private* key stays at home. It's not like the commands are difficult. They set up a local Cygwin, add the openssh package, then say: $ ssh-keygen ...press Enter a bunch of times... $ cat ~/.ssh/id_rsa.pub > /dev/clipboard ...compose email to rvicker, paste > With out their passwords I can't login to establish their $home > directory structure, Take a look at /etc/profile, starting at line 75. See the stuff about /etc/skel? That's how the user's home directory gets set up. Nothing magic here. You could cut those couple-dozen lines into a new script and tweak it for your purposes. The only trick is that if you do all this as administrator, you'll have to say something like # chown -R otheruser.otheruser ~otheruser after you get done setting up the user's home directory. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple