Thus said Ron Wilson on Fri, 27 Dec 2013 16:30:43 -0500:
I don't know how Fossil's SSH support works, but I'd be surprised if
it doesn't support use of SSH-Agent.
The nice thing about ssh-agent is that Fossil doesn't need to support
it. As long as Fossil supports SSH, ssh-agent comes for
On Mon, Dec 30, 2013 at 5:10 PM, David Rush northwoodlo...@gmail.comwrote:
If ssh-agent can work it's probably the way to go. It seems to be the most
standardized amongst all the popular pass-phrase managers, at least on
non-[apple|microsoft] platforms. But, as far as I can tell it only stores
If ssh-agent can work it's probably the way to go. It seems to be the most
standardized amongst all the popular pass-phrase managers, at least on
non-[apple|microsoft] platforms. But, as far as I can tell it only stores
decrypted private keys and not any pass phrases and I don't have the
resources
PAM programming is kind of tricky and depending on the user database that's
been configured, the application calling into PAM either needs to be
running as root or there needs to be a helper application running as root
(saslauthd is an example of this) that the real application has permission
to
Those are all good ideas but they address the other end of my issue. My
immediate need is with respect to fossil as a client that implements a
somewhat standardized, but platform specific, way to store and retrieve the
credentials that fossil sends in the Authorization http header so the
HTTP
On Fri, Dec 27, 2013 at 11:56 AM, David Rush northwoodlo...@gmail.comwrote:
Those are all good ideas but they address the other end of my issue. My
immediate need is with respect to fossil as a client that implements a
somewhat standardized, but platform specific, way to store and retrieve the
On Fri, Dec 27, 2013 at 4:30 PM, Ron Wilson ronw.m...@gmail.com wrote:
There is a platform independent tool that does this for SSH: SSH-Agent. In
theory, it could store other credentials. It is open source, so the client
API is readily available.
One of the versions for OSX, SSHkeychain,
On 12/24/13, Andy Bradford amb-fos...@bradfords.org wrote:
Rather than making Fossil aware of different user databases, why
not simply make a Fossil interface for passing user/authentication
information onto an external program.
That is what PAM is about. PAM provides a
Hi,
I'm wondering if optional password manager support would be a welcomed
addition to fossil. It does a good job of managing its own passwords
internally but I have a setup where the users / passwords are actually
system accounts and the remote HTTPS server hosting the repository uses a
PAM
On Tue, Dec 24, 2013 at 5:17 PM, David Rush northwoodlo...@gmail.comwrote:
locked when not in use. I realize not everybody uses the Gnome Desktop.
But, the concept could be extended to support OSX Keychain, KDE Wallet, of
the Windows equivalent.
Hi!
i've got no experience with programming
The nice thing about running fossil as a CGI behind a web server is
you automatically get for free any authorization mechanism supported
by the web server. In my case it's just 1 machine and I wanted to use
PAM directly so ssh and http access is the same. For this I wrote a
custom patch against
On Tue, Dec 24, 2013 at 6:06 PM, David Rush northwoodlo...@gmail.comwrote:
The nice thing about running fossil as a CGI behind a web server is you
automatically get for free any authorization mechanism supported by the web
server.
Facepalm. Of course! If things were always so simple...
Thus said David Rush on Tue, 24 Dec 2013 10:17:59 -0600:
I'm wondering if optional password manager support would be a welcomed
addition to fossil.
Rather than making Fossil aware of different user databases, why
not simply make a Fossil interface for passing user/authentication
Thus said David Rush on Tue, 24 Dec 2013 11:06:50 -0600:
The nice thing about running fossil as a CGI behind a web server is
you automatically get for free any authorization mechanism supported
by the web server.
What you don't get for free is the Fossil assignment of capabilities.
14 matches
Mail list logo
