similar to: [PATCH] Add per-listener and per-mount connection time limits.

diff -u --recursive icecast/src/admin.c icecast-new/src/admin.c --- icecast/src/admin.c 2003-07-18 16:29:23.000000000 -0400 +++ icecast-new/src/admin.c 2003-08-06 19:18:32.000000000 -0400 @@ -213,7 +213,7 @@ html_write(client, "HTTP/1.0 200 OK\r\n" "Content-Type: text/html\r\n" "\r\n"); - DEBUG1("Sending XSLT

I'd like to commit the following patch which adds a new option to the htpasswd client authenticator. This option <option name="allow_duplicate_users"> specifies wether or not the same username can connect to a mountpoint more than once. This is pretty much a required feature for any decent use of the listener authentication capabilities of icecast. thoughts ? comments ?

There are many ways to set up and manage a VPN. Tinc's roots are a "friend network", where there is a group of nodes that all trust each other, and there is no central authority. It also works well in situations where all nodes are controlled by the same authority, for example when a sysadmin configures several nodes, like within a company that wants to link together several

Hello, after the reply of Jerome Alet, I forward our questions to you. I hope it is now the right place to put it. Could you please send your answers, questions, comments to interopcast-general@nongnu.org so everyone in the group can get a copy of it. Thank you. ----- Original Message ----- From: "Jerome Alet" <alet@librelogiciel.com> To: <interopcast-general@nongnu.org>

On Friday 17 January 2003 20:17, Karl Heyes shaped the electrons to say: > I would suggest a slightly different approach. > > Instead of increasing the syscall overhead for all sockets, trapping > for uncommon cases. Try the sock_write_bytes and if that is > continuously having to queue (ie not all data can be sent) then display > the warning, maybe make it a run-time option

TL;DR: a proposal for a new tinc feature that allows nodes to filter ADD_SUBNET messages based on the metaconnection on which they are received, so that nodes can't impersonate each other's VPN Subnets. Similar to StrictSubnets in spirit, but way more flexible. BACKGROUND: THE ISSUE OF TRUST IN A TINC NETWORK In terms of metaconnections (I'm not discussing data tunnels here), one of