[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#611468: marked as done (release-notes: updating to squeeze requires manual configuration for kerberized nfs)



Your message dated Sun, 31 Mar 2013 11:36:11 +0200
with message-id <20130331093611.GA29197@hardeman.nu>
and subject line Re: Bug#611468: release-notes: updating to squeeze requires manual configuration for kerberized nfs
has caused the Debian Bug report #611468,
regarding release-notes: updating to squeeze requires manual configuration for kerberized nfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
611468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611468
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: important

As noted in bug #568771 and /usr/share/doc/libkrb5-3/NEWS.Debian.gz,
weak cryptos are disabled by default but necessary for kerberized NFS.

I just upgraded an entire network of 10 machines to squeeze, and on all
machines (NFS server, NFS clients, KDC), it was necessary to add
"allow_weak_crypto=true" to the [libdefaults] section in /etc/krb5.conf.

I think the issue is important enough to warrant a note in the release
docs since mounting a kerberized NFS share will fail with unhelpful
error messages until the above fix has been done on all machines.

-- 
David Härdeman



--- End Message ---
--- Begin Message ---
On Sat, Mar 30, 2013 at 02:28:08PM -0400, David Prévot wrote:
>Control: tags -1 moreinfo
>
>Hi,
>
>On Sat, Jan 29, 2011 at 06:41:04PM +0100, David Härdeman wrote:
>
>> As noted in bug #568771 and /usr/share/doc/libkrb5-3/NEWS.Debian.gz,
>> weak cryptos are disabled by default but necessary for kerberized NFS.
>
>> I think the issue is important enough to warrant a note in the release
>> docs since mounting a kerberized NFS share will fail with unhelpful
>> error messages until the above fix has been done on all machines.
>
>Is this issue still relevant for Wheezy? I suspect it isn’t and advise
>the RN wizard to close it (I may do so myself next time I come across
>this bug report unless more information is provided).

No, it probably isn't relevant any more. nfs-utils 1:1.2.3-1 added
support for strong encryption and no particular configuration should be
necessary when upgrading to wheezy.

-- 
David Härdeman

--- End Message ---

Reply to: