On 9/14/2012 9:00 AM, John Ward wrote:
John Ward gmail.com> writes:
I finally figured it out. It actually was a problem with a domain account that
I broke when I ran "mkpasswd -l > /etc/passwd" to make sure the new local
account existed in the passwd file (obviously removing the Domain account
On Fri, Sep 14, 2012 at 12:00 PM, John Ward wrote:
> John Ward gmail.com> writes:
(edit)
> Can anyone recommend a "cygwin for dummies" site, or a list of great resources
> to learn more?
>
> Thanks
>
> John Ward
Starting with the manual is always recommended. Handily contained on
site at cygw
John Ward gmail.com> writes:
I finally figured it out. It actually was a problem with a domain account that
I broke when I ran "mkpasswd -l > /etc/passwd" to make sure the new local
account existed in the passwd file (obviously removing the Domain account in the
process).
So I identified the is
Andrew DeFaria DeFaria.com> writes:
> It's hard to tell what you did wrong when you did not give us the exact
> steps of what you did.
I created a new local ID on a 2003 server. Then I logged in with that ID on the
server and started a Cygwin session. It gave the message "Your group is
curren
On 09/14/2012 06:11 AM, John Ward wrote:
I am very green with Cygwin and inherited a system where we had ssh passwordless
authentication working with dsa keys.
I needed to create a new ID that required a password and I was successfully able
to do that, but it appears I broke the passwordless aut
I am very green with Cygwin and inherited a system where we had ssh passwordless
authentication working with dsa keys.
I needed to create a new ID that required a password and I was successfully able
to do that, but it appears I broke the passwordless authentication in the
process, as those accoun
6 matches
Mail list logo