Skip Menu |
 

History Show all quoted text — Show full headers
# Sat Jul 12 22:41:18 2008 <peter.wolfe@hp.com> - Ticket created
From: "peter wolfe" <peter.wolfe@hp.com>
To: <kfw-bugs@mit.edu>
Subject: Bug in MIT Kerberos for Windows Version 3.2.2
Date: Sat, 12 Jul 2008 19:22:53 -0400
Download (untitled) / with headers
text/plain 847B
I have windows home premium 54-bit.
The secure endpoints site:
http://www.secure-endpoints.com/#kfw
says to install BOTH the 32 bit and 64 bit MSI files on 64 bit windows...
I installed the 32 bit one first and then the 64 bit one.
The 64 bit install detects the 32 bit one and *removes* it
before proceeding. So is the web site just wrong? Or should
the installation order be 64 bit then 32 bit (which I haven't
tried yet). Either way, both installs will try to install
the same service, no? Which one should win?

pete

--
+----------------------------------------------------------------------------+
|Peter Wolfe, Manageability Solutions Lab Peter.Wolfe@hp.com |
|Hewlett-Packard Co. (732) 577-9207 |
+----------------------------------------------------------------------------+
# Sat Jul 12 22:52:16 2008 jaltman (Jeffrey Altman) - Status changed from 'new' to 'open'
# Sat Jul 12 22:52:17 2008 jaltman (Jeffrey Altman) - Given to jaltman (Jeffrey Altman)
# Sat Jul 12 22:52:17 2008 jaltman (Jeffrey Altman) - Correspondence added
Download (untitled) / with headers
text/plain 1.4KiB
[peter.wolfe@hp.com - Sat Jul 12 22:41:18 2008]:

Show quoted text
> I have windows home premium 54-bit.
> The secure endpoints site:
> http://www.secure-endpoints.com/#kfw
> says to install BOTH the 32 bit and 64 bit MSI files on 64 bit
> windows...
> I installed the 32 bit one first and then the 64 bit one.
> The 64 bit install detects the 32 bit one and *removes* it
> before proceeding. So is the web site just wrong? Or should
> the installation order be 64 bit then 32 bit (which I haven't
> tried yet). Either way, both installs will try to install
> the same service, no? Which one should win?
>
> pete

Pete:

64-bit KFW is not supported by MIT. Secure Endpoints provides support
for 64-bit Windows. Support is available to paying clients.

http://www.secure-endpoints.com/support/kfw.html

KFW does not install any services so there are no conflicts. 32-bit KFW
is required if you are using 32-bit applications that make use of the
Kerberos or GSS libraries. 32-bit KFW is also required if you need
identity management for Kerberos v4 credentials.

If you can provide an installation log that shows the unintended
uninstall to Secure Endpoints, a fix can be produced.

The Upgrade Codes for the 64-bit and 32-bit KFW packages are different
so they really should not be affected one another.

AMD64:
<?define UpgradeCode="6DA9CD86-6028-4852-8C94-452CAC229244"?>

X86:
<?define UpgradeCode="61211594-AAA1-4A98-A299-757326763CC7"?>

Jeffrey Altman
Secure Endpoints Inc.
# Sat Jul 12 23:28:10 2008 jaltman (Jeffrey Altman) - Correspondence added
Date: Sat, 12 Jul 2008 23:29:33 -0400
From: Jeffrey Altman <jaltman@mit.edu>
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #6027] Bug in MIT Kerberos for Windows Version 3.2.2
RT-Send-Cc:
Download (untitled) / with headers
text/plain 123B
Are you absolutely sure that you did not have the 32-bit NSIS installation?
That will be removed by the 64-bit KFW MSI.
# Sun Jul 13 16:48:30 2008 <peter.wolfe@hp.com> - Correspondence added
From: "peter wolfe" <peter.wolfe@hp.com>
To: <rt@krbdev.mit.edu>
Subject: RE: [krbdev.mit.edu #6027] Bug in MIT Kerberos for Windows Version 3.2.2
Date: Sun, 13 Jul 2008 16:48:14 -0400
RT-Send-Cc:
Download (untitled) / with headers
text/plain 1.3KiB
Yes. I downloaded:
http://www.secure-endpoints.com/binaries/mit-kfw-3-2-2/kfw-i386-3-2-2.msi
and
http://www.secure-endpoints.com/binaries/mit-kfw-3-2-2/kfw-amd64-3-2-2.msi

from here:

http://www.secure-endpoints.com/#kfw

When you install each of theses, each asks:

Autostart the Network Identity Manager each time you login to Window

That's what I meant by a common service. I assumed this was a Windows
service (and am not sure if it's supplied with the Kerberos install
or part of Windows). I was thinking it was a kerberos supplied
component and it seemed wrong that both 64 bit and 32 bit would
have the same service.

pete


--
+----------------------------------------------------------------------------+
|Peter Wolfe, Manageability Solutions Lab Peter.Wolfe@hp.com |
|Hewlett-Packard Co. (732) 577-9207 |
+----------------------------------------------------------------------------+

Show quoted text
> -----Original Message-----
> From: 0000-Admin [mailto:daemon@MIT.EDU] On Behalf Of Jeffrey Altman via RT
> Sent: Saturday, July 12, 2008 11:28 PM
> To: peter.wolfe@hp.com
> Subject: Re: [krbdev.mit.edu #6027] Bug in MIT Kerberos for Windows Version 3.2.2
>
>
> Are you absolutely sure that you did not have the 32-bit NSIS installation?
> That will be removed by the 64-bit KFW MSI.
>
>
# Sun Jul 13 17:21:53 2008 Jeffrey Altman <jaltman@secure-endpoints.com> - Correspondence added
Date: Sun, 13 Jul 2008 17:22:45 -0400
From: Jeffrey Altman <jaltman@secure-endpoints.com>
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #6027] Bug in MIT Kerberos for Windows Version 3.2.2
RT-Send-Cc:
Download (untitled) / with headers
text/plain 625B
peter.wolfe@hp.com via RT wrote:
Show quoted text
> When you install each of theses, each asks:
>
> Autostart the Network Identity Manager each time you login to Window
>
> That's what I meant by a common service. I assumed this was a Windows
> service (and am not sure if it's supplied with the Kerberos install
> or part of Windows). I was thinking it was a kerberos supplied
> component and it seemed wrong that both 64 bit and 32 bit would
> have the same service.
>
NetIdMgr is not a service. It is a per-session application. Only one
instance, 32-bit or 64-bit,
will execute. First one wins. Shouldn't matter which one does.
Download smime.p7s
application/x-pkcs7-signature 3.2KiB

Message body not shown because it is not plain text.