[Systers-dev] dev machine

[Meryll Larkin]

Hi Kathy,

http://nic.phys.ethz.ch/news/1210776776/index_html

It is my understanding that "weak ssh" means that the keys are comparitively
easy to guess, like weak passwords.  It is highly recommended that you don't
use "weak ssh".

I am not using "weak ssh".  I am using ssh version 2, and I can still login
to my personal dev machine using PuTTy.  I don't have an account on
dev.systers.org.

ssh is something I DO know, very well.  Can I help you with this?

I'm not sure what "shared keys" are - you shouldn't be using the same keys
for different accounts.  I know how to set up security for ssh.  I know how
to set up (and explain in documentation) logins using public and private
keys (without passwords).

Meryll Larkin
(206) 931-9493

 

-----Original Message-----
From: systers-dev-bounces at systers.org
[mailto:systers-dev-bounces at systers.org] On Behalf Of Kathy Richardson
Sent: Wednesday, April 28, 2010 3:22 PM
To: systers-dev+devmachine at systers.org
Subject: [Systers-dev] dev machine

This discussion should really be on the list.
The machine being set up for this summer is dev.systers.org
Right now, it is set up so that folks with accounts on it can use 
weak/negotiated ssh (I'm sure that isn't the right term). This means you 
can login using putty and plain ssh. Or from any linux flavor: ssh -l 
<username> dev.systers.org
(Svaksha - see additional comments below)

Currently there are accounts for: simone, terri, gloriaw, svaksha, jason 
and myself.
Anyone that wants an account now can let svaksha, jason or I know, and 
we will set you up.
Ultimately everyone will have an account.

At present there are 3 goals for getting this machine up and running:
get standard email working on the machine, get machine set up like 
current production server,
talk with others about what they need added to support work this summer.

We did the whole basic mailman install, but it fails, and then went back 
and figured out that base mail doesn't work on the machine.
-Kathy

Svaksha,

I think the ssh weirdness is because it probably only likes having the 
unknown host in one place, and once you have it there with a key (and a 
shared key at that) things get weird. I think you should remove 
dev.systers.org from your known hosts. I think it will then set up the 
right thing when you do the say yes to the ssh w/o key pairs. I don't 
know that if weird things will happen once you set up key pairs or not.

We just missed each other on chat this morning.
-Kathy

?????? wrote:
> On Wed, Apr 28, 2010 at 17:10, ?????? <vid at svaksha.com> wrote:
>> On Mon, Apr 26, 2010 at 22:38, Kathy Richardson 
>> <kjr at casaveracruz.com> wrote:
>>> It is encouraged that you set up key ssh, but not required - or at 
>>> least at
>>> this point.
>>>
>>> My base machine is a PC, so it is always a extra level of pain to 
>>> get the
>>> ssh-keys working. I think if you want to be able to export x-windows 
>>> you
>>> probably need keys set up.
>>>
>>> For now, you can just use ssh to login.
>> I tried with: $ ssh -i .ssh/id_rsa -vvv svaksha at dev.systers.org, which
>> asked me if i wished to continue and i typed "yes" but it would not
>> accept the password you mailed me. See the following error:
>>
>> svaksha at dev.systers.org's password:
>> debug3: packet_send2: adding 64 (len 58 padlen 6 extra_pad 64)
>> debug2: we sent a password packet, wait for reply
>> debug1: Authentications that can continue: publickey,password
>> Permission denied, please try again.
>> svaksha at dev.systers.org's password:
>> debug3: packet_send2: adding 64 (len 58 padlen 6 extra_pad 64)
>> debug2: we sent a password packet, wait for reply
>> debug1: Authentications that can continue: publickey,password
>> debug2: we did not send a packet, disable method
>> debug1: No more authentication methods to try.
>> Permission denied (publickey,password).
>
> Furthermore, trying to ssh into your machine sans ssh keys broke the
> existing key as i had to add it to .ssh/known_hosts file and it locked
> me out of another machine which I access with the same key. That's
> super odd.
>
> Currently i copied my key from the backup BUT that is not very elegant
> routine :( Any ideas?
>


To unsubscribe from this conversation, send email to
<systers-dev+devmachine+unsubscribe at systers.org> or visit
<http://systers.org/mailman/options/systers-dev?override=113&preference=0>
To contribute to this conversation, use your mailer's reply-all or
reply-group command or send your message to
systers-dev+devmachine at systers.org
To start a new conversation, send email to <systers-dev+new at systers.org>
To unsubscribe entirely from systers-dev, send email to
<systers-dev-request at systers.org> with subject unsubscribe.