22 messages in ru.sysoev.nginxRe: Access key module
FromSent OnAttachments
Evan MillerDec 29, 2007 7:19 pm 
Cliff WellsDec 30, 2007 12:53 am 
Manlio PerilloDec 30, 2007 7:41 am 
Cliff WellsDec 30, 2007 3:47 pm 
Grzegorz NosekDec 31, 2007 12:32 am 
Manlio PerilloDec 31, 2007 3:43 am 
Manlio PerilloDec 31, 2007 3:55 am 
Grzegorz NosekDec 31, 2007 5:31 am 
Manlio PerilloDec 31, 2007 6:46 am 
Evan MillerDec 31, 2007 8:00 am 
Grzegorz NosekDec 31, 2007 8:07 am 
Manlio PerilloDec 31, 2007 8:32 am 
Manlio PerilloDec 31, 2007 8:49 am 
Grzegorz NosekDec 31, 2007 9:06 am 
Adrian PerezDec 31, 2007 9:52 am 
Evan MillerDec 31, 2007 12:12 pm 
Evan MillerDec 31, 2007 12:41 pm 
Grzegorz NosekDec 31, 2007 1:06 pm 
Cliff WellsDec 31, 2007 3:34 pm 
Manlio PerilloJan 1, 2008 9:03 am 
Manlio PerilloJan 1, 2008 9:07 am 
Adrian PerezJan 4, 2008 8:13 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Access key moduleActions...
From:Cliff Wells (clif@public.gmane.org)
Date:Dec 30, 2007 12:53:42 am
List:ru.sysoev.nginx

On Sat, 2007-12-29 at 22:19 -0500, Evan Miller wrote:

In October, Mykola Grechukh announced his new ngx_http_accesskey_module to the Russian listserver.[1] The module lets you give access keys to specific IP addresses, which is useful for restricting downloads to certain clients. I packaged his patch into a stand-alone module and translated the documentation. You can find installation instructions and usage notes on the wiki:

http://wiki.codemongers.com/NginxHttpAccessKeyModule

This is now the 10th third-party, open-source module that I know of. Cool!

And this makes me wonder if we want to implement some sort of "clearing house" for 3rd party modules. Specifically, I think the following would be useful:

1) A secure, centralized place (RCS system or even just tarballs) to download from (wiki is too open: even links to outside source code make me nervous since they could be altered by a malicious editor to lead to poisoned source code).

2) Issue tracking. Might be handy for module authors to not have to maintain their own Trac (or whatever) instance.

3) Perhaps adding some feature to the Nginx build process that allowed 3rd party modules to be easily downloaded and installed (from site listed in item 1) via configure/make flags (or is this just wishful thinking?).

Anyway, ideas welcome. I'm happy to setup and maintain whatever is decided upon.

Regards, Cliff