Differences between revisions 5 and 6
Revision 5 as of 2012-04-18 04:16:03
Size: 1368
Editor: c-76-126-113-81
Comment:
Revision 6 as of 2012-04-18 04:20:18
Size: 1368
Editor: c-76-126-113-81
Comment:
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
The executable entry defines the full path to the factotum binary. The mountpoint entry defines the path to the factotum file service. Lastly, the service entry controls the service name used when reading keys.
Line 30: Line 28:
The executable entry defines the full path to the factotum binary. The mountpoint entry defines the path to the factotum file service. Lastly, the service entry controls the service name used when reading keys.

Factotum extension

This extension is currently being distributed along with Mercurial.

Author: Steven Stallion

Overview

This extension allows the factotum facility on Plan 9 from Bell Labs platforms to provide authentication information for HTTP access. Configuration entries specified in the auth section as well as authentication information provided in the repository URL are fully supported. If no prefix is specified, a value of * will be assumed.

By default, keys are specified as:

proto=pass service=hg prefix=<prefix> user=<username> !password=<password>

If the factotum extension is unable to read the required key, one will be requested interactively.

Configuration

[extensions]
factotum =

[factotum]
executable = /bin/auth/factotum
mountpoint = /mnt/factotum
service = hg

The executable entry defines the full path to the factotum binary. The mountpoint entry defines the path to the factotum file service. Lastly, the service entry controls the service name used when reading keys.

While not explicitly supported, the plan9port version of factotum should provide a viable alternative for POSIX-compatible platforms.

Usage

This extension doesn't require user interaction to work.


CategoryBundledExtension

FactotumExtension (last edited 2012-05-04 16:11:06 by c-76-126-113-81)