Opened 6 weeks ago

Closed 43 hours ago

#3280 closed help (answered)

MonSOON not accepting RSA keys since Jasmin mandatory change

Reported by: langtont Owned by: ros
Component: Monsoon Keywords:
Cc: Platform: Monsoon2
UM Version:

Description

Hi,

Since the RSA key change was mandated on Jasmin, monsoon also hasn't been able to load my new RSA key into the keychain, rendering me unable to connect to Jasmin via monsoon. The issue cites 'bad password' but this cannot be the case, as the identical key on my local machine accepts the password/key, and it's composed only of alphanumeric characters.

Change History (6)

comment:1 Changed 6 weeks ago by ros

  • Owner changed from um_support to ros
  • Status changed from new to accepted

Hi Tom,

What do you mean by keychain? You can't run ssh-agent on Monsoon is this would you mean? Are you trying to log into JASMIN interactively or as part of the UM workflow (ie. pptransfer)?

Regards,
Ros.

comment:2 Changed 6 weeks ago by langtont

Hi Ros,

I can run $(ssh-agent) and it returns a process PID, but then when running ssh-add, it asks for the passphrase and then rejects it every time I type it in (even though the passphrase is correct). I'm trying to connect interactively, so I can scp files from the monsoon group workspace to the Jasmin one. As mentioned, this was working fine prior to the Jasmin RSA key change.

Cheers,
Tom

comment:3 Changed 6 weeks ago by ros

Hi Tom,

ssh-agent aside for the moment. If you simply ssh to JASMIN on the command line does it accept your passphrase? If not please ssh with ssh -vvv to get verbose output and confirm that it is picking up the correct jasmin key. Don't post the output here; there will be a lot of output if you can't see the key pickup please email the output to me or the cms-support at ncas.ac.uk email address and I'll take a look.

Regards,
Ros.

comment:4 Changed 6 weeks ago by langtont

Hi Ros, I've attached the output as a .txt file. As far as I can see nothing too wrong with it until it tries to request the passphrase, which it then says is wrong.

Tom

comment:5 Changed 6 weeks ago by ros

Hi Tom,

Thanks. (I've just removed the output file from this ticket for security reasons).
If you can't login to JASMIN using that key then it must either be corrupt or not your new key. I I suspect the former due to lines in the trace like:

debug3: Not a RSA1 key file 
...
debug2: key_type_from_name: unknown key type '-----BEGIN'
...
debug2: key_type_from_name: unknown key type '-----END'

I suggest removing that key file from Monsoon and then recopying your JASMIN key over from a machine from which you can successfully log in from with.

Regards,
Ros.

comment:6 Changed 43 hours ago by ros

  • Resolution set to answered
  • Status changed from accepted to closed

Hi Tom,

I assume you have sorted this out now and so will close the ticket.

Regards,
Ros.

Note: See TracTickets for help on using tickets.