[OpenAFS] Password transition to krb5 - your methods?
Derrick Brashear
shadow@gmail.com
Thu, 25 Oct 2007 12:11:26 -0400
------=_Part_1815_9375091.1193328686821
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
i disagree about distribution. i do think we should have a page with
instructions and resources we provide a reference to.
On 10/25/07, Jeff Blaine <jblaine@kickflop.net> wrote:
>
> IMO, it should be distributed with it and referenced
> in a new README.kaserver (which also should include
> the elders EOL statement regarding kaserver).
>
> It doesn't have to be referenced by the build process.
>
> I wouldn't surprise me to find that nobody agrees with
> me again.
>
> Jeffrey Altman wrote:
> > Derrick Brashear wrote:
> >>
> >> On 10/25/07, *Jeff Blaine* <jblaine@kickflop.net
> >> <mailto:jblaine@kickflop.net>> wrote:
> >>
> >> You had me wondering.
> >>
> >> The only reference to afs2k5db I could find in source was
> >>
> >> src/packaging/RedHat/openafs.spec.in
> >>
> >> Which then leads me to:
> >>
> >> Are the RedHat builds getting preferential treatment with
> >> regard to this? Is there a reason? What's up?
> >>
> >>
> >> in the sense that warlord made the rpms ship the entire afs-krb5 kit,
> >> and no other set of packages does, yes.
> >> technically that wasn't part of openafs. i think it's in 1.4.5 now
> though.
> >
> > afs2k5db is not part of openafs 1.4.5. Building it requires access to
> > private MIT krb5 headers. We would distribute it if we could build it
> > using the public headers but we can't.
> >
> > Jeffrey Altman
> >
> >
>
------=_Part_1815_9375091.1193328686821
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
i disagree about distribution. i do think we should have a page with instructions and resources we provide a reference to.<br><br><div><span class="gmail_quote">On 10/25/07, <b class="gmail_sendername">Jeff Blaine</b> <
<a href="mailto:jblaine@kickflop.net">jblaine@kickflop.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">IMO, it should be distributed with it and referenced
<br>in a new README.kaserver (which also should include<br>the elders EOL statement regarding kaserver).<br><br>It doesn't have to be referenced by the build process.<br><br>I wouldn't surprise me to find that nobody agrees with
<br>me again.<br><br>Jeffrey Altman wrote:<br>> Derrick Brashear wrote:<br>>><br>>> On 10/25/07, *Jeff Blaine* <<a href="mailto:jblaine@kickflop.net">jblaine@kickflop.net</a><br>>> <mailto:<a href="mailto:jblaine@kickflop.net">
jblaine@kickflop.net</a>>> wrote:<br>>><br>>> You had me wondering.<br>>><br>>> The only reference to afs2k5db I could find in source was<br>>><br>>> src/packaging/RedHat/openafs.spec.in
<br>>><br>>> Which then leads me to:<br>>><br>>> Are the RedHat builds getting preferential treatment with<br>>> regard to this? Is there a reason? What's up?<br>>><br>
>><br>>> in the sense that warlord made the rpms ship the entire afs-krb5 kit,<br>>> and no other set of packages does, yes.<br>>> technically that wasn't part of openafs. i think it's in 1.4.5
now though.<br>><br>> afs2k5db is not part of openafs 1.4.5. Building it requires access to<br>> private MIT krb5 headers. We would distribute it if we could build it<br>> using the public headers but we can't.
<br>><br>> Jeffrey Altman<br>><br>><br></blockquote></div><br>
------=_Part_1815_9375091.1193328686821--