This is an automated email from the git hooks/post-receive script.
rharwood pushed a commit to branch master
in repository gssproxy.
Author: Robbie Harwood <rharwood(a)redhat.com>
Date: Wed Mar 8 11:28:35 2017 -0500
Add mailing list and IRC links to README
Also migrate README to rich text
Signed-off-by: Robbie Harwood <rharwood(a)redhat.com>
Reviewed-by: Simo Sorce <simo(a)redhat.com>
README => README.md | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/README b/README.md
similarity index 69%
rename from README
rename to README.md
index c936ea9..98d749c 100644
@@ -1,12 +1,11 @@
This is the gss-proxy project.
The goal is to have a GSS-API proxy, with standardizable protocol and a
-[somewhat portable] reference client and server implementation. There
+(somewhat portable) reference client and server implementation. There
are several motivations for this some of which are:
- Kernel-mode GSS-API applications (CIFS, NFS, AFS, ...) need to be
- able to leave all complexity of GSS_Init/Accept_sec_context() out of
+ able to leave all complexity of GSS\_Init/Accept\_sec\_context() out of
the kernel by upcalling to a daemon that does all the dirty work.
- Isolation and privilege separation for user-mode applications. For
@@ -18,3 +17,7 @@ are several motivations for this some of which are:
gss-proxy uses libverto for dealing with event loops. Note that you need to
have at least one libverto event library installed (e.g. libverto-tevent).
+We have a
+and an IRC channel (#gssproxy on [Freenode](https://webchat.freenode.net)).
To stop receiving notification emails like this one, please contact
the administrator of this repository.