You Are Here : Forums Sunday, September 07, 2008
     
Activeworx.org Forums
 
  Forum  IDS Policy Mana...  IDS Policy Mana...  Problem using publickeys
Previous Previous
 
Next Next
New Post 9/3/2007 5:24 PM
  benh
3 posts
No Ranking


Problem using publickeys 
Trying to set Policy Manager (standalone) to talk to a sensor using SSH keys.

The key works if I use Putty, but using it in the application I get an error dialog box with:

Connect - System error: Error parsing PEM ASN.1 structure: Error decoding.

Error - System error: Error parsing PEM ASN.1 structure: Error decoding.

Any ideas why it's doing that, and more importantly, how to make it not do that?

cheers.
 
New Post 9/3/2007 6:36 PM
  Jeff Dell
233 posts
www.activeworx.com
1st Level Poster


Re: Problem using publickeys 
Please read the directions carefully. It is not exactly the same as using Putty, but uses Putty KeyGen. pay attention to the location, the key should be placed into the IDSPM application directory, and how the key is saved.

Cheers,
Jeff
 
New Post 9/3/2007 7:42 PM
  benh
3 posts
No Ranking


Re: Problem using publickeys 
I generated the key within the program. It's in the same directory as IDSPM. I know it's not the same as Putty, I was using that as an example of it not being a network issue or permissions issue. You use IP*Works SSH client libraries, I am aware of that.

it's saved in the right place, or it would generate a "Can't find keyfile" error, would it not.
 
New Post 9/4/2007 2:26 AM
  Jeff Dell
233 posts
www.activeworx.com
1st Level Poster


Re: Problem using publickeys 
Did you follow the directions in the documentation? specifically step 2? it is important that you select 'Export OpenSSH Key' to save the key.

Cheers,
Jeff
 
New Post 9/4/2007 9:54 AM
  benh
3 posts
No Ranking


Re: Problem using publickeys 
Bingo, it was in the wrong format. Thank you.
 
Previous Previous
 
Next Next
  Forum  IDS Policy Mana...  IDS Policy Mana...  Problem using publickeys
 
 
Copyright 2000-2007 by Activeworx, Inc.
All trademarks and copyrights on this page are owned by their respective owners.