[OpenAFS] The removal of afscreds.exe and afs_config.exe on Windows Vista and Windows 7: Seeking Opinions
Fri, 2 Oct 2009 13:32:55 -0400
Can this proposed configuration be simulated with the current release by =
setting the registry key:
sableafscreds to 1
and deleting or renaming afscreds.exe and afs_config.exe?
> From: email@example.com [mailto:openafs-info-
> firstname.lastname@example.org] On Behalf Of Jeffrey Altman
> The Proposal:
> I propose that beginning with 1.5.66 (whenever that is) that the
> afscreds.exe and afs_config.exe tools not be installed at all on any
> Windows version Vista or beyond and that on 2000, XP and 2003 that
> tools not be installed as part of the default configuration.
> The Impact:
> The afscreds tool provides three sets of functionality:
> * token acquisition (and renewal if MIT KFW is present)
> * drive mapping
> * start/stop the afsd service
> Network Identity Manager has long been available as a replacement for
> the token acquisition functionality and it is available on any system
> which MIT KFW is present. The only systems that wouldn't have it are
> clients of cells that are still using kaserver.
> The drive mapping functionality has been documented as deprecated =
> the addition of the loopback installation permitted the use of a
> standard \\AFS UNC server name. The recommended method for a user to
> create a drive mapping is the Windows Drive Mapping user interface
> provided as part of "[My] Computer" and the Explorer Shell.
> Starting and stopping the afsd service is an administration function
> that can be performed using the Windows Service MMC.
> The afs_config.exe tool provides:
> * configuration management including cell name, server preferences,
> cellservdb editing,
> cache size, and advanced tuning parameters
> * start/stop functionality
> * drive mapping