From owner-freebsd-security Fri May 4 9:56:15 2001 Delivered-To: freebsd-security@freebsd.org Received: from mdma.playboy.com (mdma.playboy.com [216.163.140.20]) by hub.freebsd.org (Postfix) with ESMTP id 3AD8137B43F for ; Fri, 4 May 2001 09:56:08 -0700 (PDT) (envelope-from jamie@playboy.com) Received: by mdma.playboy.com (Postfix, from userid 100) id C0AFD12794; Fri, 4 May 2001 11:56:03 -0500 (CDT) Date: Fri, 4 May 2001 11:56:03 -0500 From: jamie rishaw To: freebsd-security@freebsd.org Cc: jamie@playboy.com Subject: SecurID Message-ID: <20010504115603.C21698@playboy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-No-Archive: yes Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm looking to chat either on- or off-list with people that have successfully integrated RSA's SecurID into FreeBSD. Specifically, the client side. There are no official clients, and when I try to compile commercial SSH with SecurID support, I get "File format not recognized" when the ssh daemon tries to link sdiclient.a symbols (sdiclient.a being the file that the ACE server generates/holds for clients to link in and talk/authenticate with). SSH.com has still yet to reply to my open ticket with them... I have searched high and low for real answers, yet I cannot find anyone that's been able to say, "Yes, I've done it, here's how". URLs, Pointers, etc., are all appreciated. thanks in advance, jamie -- jamie rishaw sr. wan/unix engineer/ninja // playboy enterprises inc. opinions stated are mine, and are not necessarily those of the bunny. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message