public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Nicolas Williams <Nicolas.Williams@ubsw.com>
To: krbdev@mit.edu, cygwin@cygwin.com
Subject: MIT Kfw SDK w/ Cygwin? Trying to build OpenSSH w/ GSS-API on Cygwin...
Date: Thu, 03 Jan 2002 10:25:00 -0000	[thread overview]
Message-ID: <20020103132435.I20045@wdr.com> (raw)

I'm trying to build OpenSSH (2.9p2, for now) with Simon Wilkinson's
patches that implement the external-keyx / GSS-API extensions.

Specifically I wish to use Kerberos V as the GSS mechanism.

That means picking Heimdal or MIT krb5 as the Kerberos V implementation.

I started with MIT krb5, specifically Kfw (Kerberos for Windows).

Kfw is compiled with MSVC++ (all C).

*FAQ check: it is supposedly ok to mix Cygwin with MSVC++ built (C only) DLLs*

After writing the necessary autoconf checks for Kfw (library names
differ) and dealing with making sure that _WIN32 is defined where the
Kfw headers are included, I've gotten as far as getting a successful
link of ssh.exe. But it crashes with SIGSEGV and I'm still trying to
get a stack trace.

Looking at the dependencies of the Kfw DLLs I see that there is a
dependency on MSVCRT.DLL.

*FAQ check: MSVCRT.DLL and cygwin1.dll are mutually exclusive*

But the dependency on MSVCRT.DLL by the MIT Kfw DLLs is indirect.

QUESTION: Does the MSVCRT.DLL/cygwin1.dll mutual exclusivity apply in
          this case?

If so, then I'll give up on Kfw now and try Heimdal - unfortunately that
probably means giving up on Leash32.

QUESTION: Does the MIT krb5 stuff build on Cygwin? Kerbnet appears to
          have died some time ago...

Thanks,

Nico
--
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2002-01-03 18:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-03 10:25 Nicolas Williams [this message]
     [not found] ` <01e401c19491$4d1d9e40$1b011212@mit.edu>
2002-01-03 12:18   ` Nicolas Williams
2002-01-03 12:24     ` Nicolas Williams
2002-01-03 12:38     ` Douglas E. Engert
2002-01-03 12:52       ` Nicolas Williams
2002-01-03 10:42 Jeffrey Altman
2002-01-03 10:49 ` Nicolas Williams
2002-01-03 10:56 Jeffrey Altman
2002-01-03 12:10 Jeffrey Altman
2002-01-03 12:32 Jeffrey Altman
2002-01-03 12:37 ` Nicolas Williams
2002-01-03 13:38 Jeffrey Altman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020103132435.I20045@wdr.com \
    --to=nicolas.williams@ubsw.com \
    --cc=cygwin@cygwin.com \
    --cc=krbdev@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).