login about faq

I'm using safeword authentication on Solaris, but the authetication via Tectia server is failing. It seems the pam_safeword busyloops, and that is the cause for the authentication failure. But e.g. via telnet I'm able to authenticate without issues.

Is this a known compatibility issue? Is there a fix for this?

asked Jan 11 '11 at 13:48

SSH%20KB's gravatar image

SSH KB ♦
509249246237


On Solaris 9 and/or Solaris 10 platforms, it seems that pam_safeword busyloops when using its default protocol EASSP2. However, when using EASSP1 protocol, we have discovered that it does not busyloop anymore.

pam_safeword does NOT busyloop if EASSP1 protocol is used.

An example of the lines that should be added to the pam_safewod.cfg to use the EASSP1 protocal is below:

02 Authen. Server (host weight connects port): 10.1.102.229 0 0 5030 55 Eassp Version: 101

and authentication will work on Solaris 9 and Solaris 10.

link

answered Jan 11 '11 at 13:50

SSH%20KB's gravatar image

SSH KB ♦
509249246237

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×11
×1
×1

Asked: Jan 11 '11 at 13:48

Seen: 2,511 times

Last updated: Mar 08 '11 at 17:22

All user contributed content licensed under the cc-by-sa license.
Powered by OSQA.