lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date: Fri Dec 16 11:36:08 2005
From: xyberpix at xyberpix.com (Xyberpix)
Subject: Moderated lists

Implementing it could be quite easy actually.

Setup a PHP voting booth, where someone adds the names of all the current FD
subscribers, with the length of time that they've been subscribed for, and then
set this to update itself, via cron or whatever means you prefer.

Have the voting booth require username(email addy)/passwd verification, and then
check against peoples subscription time, if they have been subscribed for x years
they can vote, if they haven't they can only view the current results, and not vote.

The voting booth should be linked into the mailman list manager, and then once
voting season is over, it will either leave the e-mail addy on the list if people
voted to keep the person, or if the vote went the other way, then the e-mail addy
is automatically removed.

I'm no PHP programmer, but I know that there are people on here who could set
this up. I can offer webspace/PHP/MySQL if it's needed, and would be willing to
help ouyt where I can on this one.
Also I'm in the UK, so it makes it a bit easier as well.


Just my 2p's worth

xyberpix

On Fri Dec 16  2:20 , 'Aditya Deshmukh'
<aditya.deshmukh@...ine.gateway.strangled.net> sent:

> 
>> Why not do a self-regulating list?  Something along the lines 
>> of keeping
>> track of signup dates and IP addresses, then when a yahoo starts
>> spouting crap, put it to a vote on list. (only members older then xyz
>> date have a vote) If the list's wish is to have the user 
>> banned, then so
>> be it... 
>> 
>
>This is all so good in principle but how do you implement it ? And how
>Does voting take place ? By email to the list ? This way anytime we have 
>To remove someone from the list it will generate a whole lot of useless 
>mail....
>
>
>_______________________________________________
>Full-Disclosure - We believe in it.
>Charter: http://lists.grok.org.uk/full-disclosure-charter.html
>Hosted and sponsored by Secunia - http://secunia.com/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ