|
Size: 1141
Comment:
|
Size: 1369
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| 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. While not explicitly supported, the [[http://swtch.com/plan9port|plan9port]] version of factotum should provide a viable alternative for POSIX-compatible platforms. | 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. |
| Line 17: | Line 17: |
| The mountpoint entry defines the path for the factotum file service. The executable entry defines the full path to the factotum binary. Lastly, the service entry controls the service name used when reading keys. |
|
| Line 23: | Line 25: |
| mount = /mnt/factotum path = /bin/auth/factotum |
executable = /bin/auth/factotum mountpoint = /mnt/factotum |
| Line 26: | Line 28: |
| }}} | }}} While not explicitly supported, the [[http://swtch.com/plan9port|plan9port]] version of factotum should provide a viable alternative for POSIX-compatible platforms. |
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.
The mountpoint entry defines the path for the factotum file service. The executable entry defines the full path to the factotum binary. Lastly, the service entry controls the service name used when reading keys.
Configuration
[extensions] factotum = [factotum] executable = /bin/auth/factotum mountpoint = /mnt/factotum service = hg
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.