[OpenAFS] 1.3.6000 integrated logon?
Kevin Coffman
kwc@citi.umich.edu
Fri, 19 Mar 2004 08:32:00 -0500
This is a multi-part message in MIME format.
------=_NextPart_000_0077_01C40D8C.A7DF0550
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Jeff,
I've had two reports (myself and someone else) about very slow behavior =
in
the OpenAFS dialog. (Obtain tokens, drive mappings) I didn't see this =
with
the 1.3.5299 version that I installed two days ago. This is with KfW =
2.6
beta 7 and beta 8 installed on WinXP machines.
=20
K.C.
-----Original Message-----
From: openafs-info-admin@openafs.org =
[mailto:openafs-info-admin@openafs.org]
On Behalf Of Jeffrey Altman
Sent: Thursday, March 18, 2004 9:52 PM
To: Stephen Joyce
Cc: openafs-info@openafs.org
Subject: Re: [OpenAFS] 1.3.6000 integrated logon?
To be honest I have not even had time to look at afslogon.c
yet. I just took a look at it and it scared me. There=20
is a mixture of calls to LocalAlloc() followed by calls to
free() on the allocated memory which is sure to cause memory
corruption.
I do not know if it works or does not work. However, the=20
only changes to it since 1.2.10 are to the string used to
identify the module when logging Events.
Jeffrey Altman
Stephen Joyce wrote:
I'm testing the windows 1.3.6000 build--hoping it will solve several
outstanding problems I've seen with OpenAFS 1.2.11 on windows.
Can someone please confirm for me that obtaining tokens when logging =
into
Windows works on this build?
I have checked "Obtain AFS tokens when logging into Windows", and made =
sure
that "Fail Logins Silently" is "No", but I do not get tokens when
logging in. Neither is there any error message to indicate that the =
client
is even attempting to contact a server, nor any record in the server =
logs.
I've confirmed that toggling the "Obtain AFS tokens..." checkbox does
indeed toggle
HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\=
Log
onOptions.
I'm attempting standard AFS authentication, against krb5/fakeka. I can
obtain tokens manually on the client without problems and that shows up =
in
the server logs as expected.
Cheers,
Stephen
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info
------=_NextPart_000_0077_01C40D8C.A7DF0550
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D716002713-19032004>Jeff,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D716002713-19032004>I've=20
had two reports (myself and someone else) about <STRONG>very</STRONG> =
slow=20
behavior in the OpenAFS dialog. (Obtain tokens, drive =
mappings) I=20
didn't see this with the 1.3.5299 version that I installed two days =
ago. =20
This is with KfW 2.6 beta 7 and beta 8 installed on WinXP=20
machines.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D716002713-19032004></SPAN></FONT> </DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D716002713-19032004>K.C.</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
openafs-info-admin@openafs.org [mailto:openafs-info-admin@openafs.org] =
<B>On=20
Behalf Of </B>Jeffrey Altman<BR><B>Sent:</B> Thursday, March 18, 2004 =
9:52=20
PM<BR><B>To:</B> Stephen Joyce<BR><B>Cc:</B>=20
openafs-info@openafs.org<BR><B>Subject:</B> Re: [OpenAFS] 1.3.6000 =
integrated=20
logon?<BR><BR></FONT></DIV>To be honest I have not even had time to =
look at=20
afslogon.c<BR>yet. I just took a look at it and it scared =
me. =20
There <BR>is a mixture of calls to LocalAlloc() followed by calls =
to<BR>free()=20
on the allocated memory which is sure to cause =
memory<BR>corruption.<BR><BR>I=20
do not know if it works or does not work. However, the <BR>only =
changes=20
to it since 1.2.10 are to the string used to<BR>identify the module =
when=20
logging Events.<BR><BR>Jeffrey Altman<BR><BR><BR><FONT=20
face=3D"Bitstream Cyberbit">Stephen Joyce wrote:<BR></FONT>
<BLOCKQUOTE =
cite=3DmidPine.GSO.4.58.0403182042320.9459@titan.physics.unc.edu=20
type=3D"cite"><PRE wrap=3D""><FONT face=3D"Bitstream Cyberbit">I'm =
testing the windows 1.3.6000 build--hoping it will solve several
outstanding problems I've seen with OpenAFS 1.2.11 on windows.
Can someone please confirm for me that obtaining tokens when logging =
into
Windows works on this build?
I have checked "Obtain AFS tokens when logging into Windows", and made =
sure
that "Fail Logins Silently" is "No", but I do not get tokens when
logging in. Neither is there any error message to indicate that the =
client
is even attempting to contact a server, nor any record in the server =
logs.
I've confirmed that toggling the "Obtain AFS tokens..." checkbox does
indeed toggle
HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\=
LogonOptions.
I'm attempting standard AFS authentication, against krb5/fakeka. I can
obtain tokens manually on the client without problems and that shows up =
in
the server logs as expected.
Cheers,
Stephen
_______________________________________________
OpenAFS-info mailing list
<A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:OpenAFS-info@openafs.org">OpenAFS-info@openafs.org</A>
<A class=3Dmoz-txt-link-freetext =
href=3D"https://lists.openafs.org/mailman/listinfo/openafs-info">https://=
lists.openafs.org/mailman/listinfo/openafs-info</A>
</FONT></PRE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0077_01C40D8C.A7DF0550--