Skip to content

Commit b737477

Browse files
Add mailing list and IRC links to README
Also migrate README to rich text See-also: https://pagure.io/pagure/issue/2085 Signed-off-by: Robbie Harwood <[email protected]> Reviewed-by: Simo Sorce <[email protected]> PR: 167
1 parent fefd2e6 commit b737477

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

README README.md

+6-3
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,11 @@
1-
21
This is the gss-proxy project.
32

43
The goal is to have a GSS-API proxy, with standardizable protocol and a
5-
[somewhat portable] reference client and server implementation. There
4+
(somewhat portable) reference client and server implementation. There
65
are several motivations for this some of which are:
76

87
- Kernel-mode GSS-API applications (CIFS, NFS, AFS, ...) need to be
9-
able to leave all complexity of GSS_Init/Accept_sec_context() out of
8+
able to leave all complexity of GSS\_Init/Accept\_sec\_context() out of
109
the kernel by upcalling to a daemon that does all the dirty work.
1110

1211
- Isolation and privilege separation for user-mode applications. For
@@ -18,3 +17,7 @@ are several motivations for this some of which are:
1817

1918
gss-proxy uses libverto for dealing with event loops. Note that you need to
2019
have at least one libverto event library installed (e.g. libverto-tevent).
20+
21+
We have a
22+
[mailing list](https://lists.fedorahosted.org/archives/list/[email protected]/)
23+
and an IRC channel (#gssproxy on [Freenode](https://webchat.freenode.net)).

0 commit comments

Comments
 (0)