Difference between revisions of "Miscellaneous bazaar issues"
m |
m |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[Versioning tools]] > [[Bazaar]] > [[Miscellaneous bazaar issues]] | |||
==Storing authentication information in configuration files== | ==Storing authentication information in configuration files== | ||
| Line 18: | Line 17: | ||
Steps have been learned using information from http://doc.bazaar.canonical.com/developers/authentication-ring.html | Steps have been learned using information from http://doc.bazaar.canonical.com/developers/authentication-ring.html | ||
[[Main Page|Home]] > [[CentOS]] > [[CentOS 6.x]] > [[Versioning tools]] > [[Bazaar]] > [[Miscellaneous bazaar issues]] | |||
Latest revision as of 15:44, 24 August 2022
Home > CentOS > CentOS 6.x > Versioning tools > Bazaar > Miscellaneous bazaar issues
Storing authentication information in configuration files
If bazaar repository is hosted over http protocol then supplying username and password for every access of repository takes considerable time. To reduce effort in authenticating with server, at cost of additional security risk, one can use following steps for storing authentication information in configuration file:
- Create '~/.bazaar/authentication.conf' file with following contents
- [RAs]
- scheme=http
- host=ras.virtual-labs.ac.in
- user=saurabh
- password=<secret-password>
- Now test connection to given server by using bzr pull, bzr log, etc.
Note that this is considerably safer than supplying password in URL itself as 'bzr pull http://saurabh:<password>@ras.virtual-labs.ac.in/vlead-ras/ras' which would lead to password being captured in shell history.
Steps have been learned using information from http://doc.bazaar.canonical.com/developers/authentication-ring.html
Home > CentOS > CentOS 6.x > Versioning tools > Bazaar > Miscellaneous bazaar issues
