Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Kerberos support (was: Coda development)
0 views
Skip to first unread message
u-m...@aetey.se
May 5, 2016, 3:55:59 AM5/5/16
to
On Wed, May 04, 2016 at 11:02:47PM -0400, Jan Harkes wrote:
> On Wed, May 04, 2016 at 11:44:35AM +0200, u-m...@aetey.se wrote:
> > The upstream version contains Kerberos-related hooks
> > but they are unfortunately insufficient for actual deployment.
> if the upstream hooks are insufficient for actual deployment,
> I guess they should be removed so that nobody has to bother trying to set
> up something that won't work anyway.
This sounds reasonable.
Their value was to show how Kerberos credentials could be transformed
to a Coda token, but not as a production code.
So unless/until the "modular clog" is merged upstream, you may wish
to disable this code but keep it for reference.
A mere notice in the documentation would do the job.
> Or is your code dependent on these insufficient hooks?
No, it is not.
Regards,
Rune
> On Wed, May 04, 2016 at 11:44:35AM +0200, u-m...@aetey.se wrote:
> > The upstream version contains Kerberos-related hooks
> > but they are unfortunately insufficient for actual deployment.
> if the upstream hooks are insufficient for actual deployment,
> I guess they should be removed so that nobody has to bother trying to set
> up something that won't work anyway.
This sounds reasonable.
Their value was to show how Kerberos credentials could be transformed
to a Coda token, but not as a production code.
So unless/until the "modular clog" is merged upstream, you may wish
to disable this code but keep it for reference.
A mere notice in the documentation would do the job.
> Or is your code dependent on these insufficient hooks?
No, it is not.
Regards,
Rune
0 new messages