[OpenAFS] kaserver deperecation, OpenAFS future, etc...

[Sandesh V Chopdekar]

This is a multipart message in MIME format.
--=_alternative 004A41DC6525720C_=
Content-Type: text/plain; charset="US-ASCII"

> So can somebody in the know comment on why "ka5server"
> wasn't the answer (for those who use kaserver)?

 I guess, to avoid duplication of efforts. since kaserver is AFS 
customized kerberos(4) (right ?)
 and the developers would have to keep fixing bugs in ka5server. 

 
 -
 Sandesh 




John Hascall <john@iastate.edu> 
Sent by: openafs-info-admin@openafs.org
19/10/2006 17:53

To
openafs-info@openafs.org
cc

Subject
Re: [OpenAFS] kaserver deperecation, OpenAFS future, etc...







We've never used kaserver (we already were using Kerberos
when we started on AFS), but it seems to me that the one
really advantage of kaserver over a true KDC is that it
had real replication instead of a master/slave model.

So can somebody in the know comment on why "ka5server"
wasn't the answer (for those who use kaserver)?

Just curious,
john
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info


--=_alternative 004A41DC6525720C_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">&gt; So can somebody in the know comment
on why &quot;ka5server&quot;<br>
&gt; wasn't the answer (for those who use kaserver)?</font>
<br>
<br><font size=2 face="sans-serif">&nbsp;I guess, to avoid duplication
of efforts. since kaserver is AFS customized kerberos(4) (right ?)</font>
<br><font size=2 face="sans-serif">&nbsp;and the developers would have
to keep fixing bugs in ka5server. </font>
<br>
<br><font size=2 face="sans-serif">&nbsp;</font>
<br><font size=2 face="sans-serif">&nbsp;-<br>
 Sandesh </font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>John Hascall &lt;john@iastate.edu&gt;</b>
</font>
<br><font size=1 face="sans-serif">Sent by: openafs-info-admin@openafs.org</font>
<p><font size=1 face="sans-serif">19/10/2006 17:53</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">openafs-info@openafs.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [OpenAFS] kaserver deperecation,
OpenAFS future, etc...</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2><br>
We've never used kaserver (we already were using Kerberos<br>
when we started on AFS), but it seems to me that the one<br>
really advantage of kaserver over a true KDC is that it<br>
had real replication instead of a master/slave model.<br>
<br>
So can somebody in the know comment on why &quot;ka5server&quot;<br>
wasn't the answer (for those who use kaserver)?<br>
<br>
Just curious,<br>
john<br>
_______________________________________________<br>
OpenAFS-info mailing list<br>
OpenAFS-info@openafs.org<br>
https://lists.openafs.org/mailman/listinfo/openafs-info<br>
</font></tt>
<br>
--=_alternative 004A41DC6525720C_=--