All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel Thimm <Axel.Thimm@ATrpms.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Submitting motherboard-specific support? (w/
Date: Tue, 21 Aug 2007 14:38:48 +0000	[thread overview]
Message-ID: <20070821143848.GE6770@puariko.nirvana> (raw)
In-Reply-To: <46C997B4.50509@dolbeau.org>


[-- Attachment #1.1: Type: text/plain, Size: 1661 bytes --]

On Tue, Aug 21, 2007 at 02:53:31PM +0200, Hans de Goede wrote:
> Let me check if I understand you correctly, you want to have a registration 
> module, for users to register themselves as trac user, which has some spam bot 
> prevention methods, like sending a confirmation mail and maybe also such a 
> picture with bad readable text? (which has a name I know, but not right now :)
> 
> But wouldn't it be better to write such a thing in python and submit it for 
> upstream trac inclusion? Has anyone already searched the web to see if such a 
> thing exists?

Yes, there are some attempts at a trac specific solution, but I was
thinking of a generic one, e.g. one that feeds an LDAP server and then
trac/mediawiki/moin/apache/you_name_it can simply query the login
credentials. That way this solution will be usable by far more than a
trac instance.

The LDAP part is dealt with at CLI level. What is missing is the Web
interface. I envision it as such:

 o User gives in data required, this would be Name (but split in
   first/last), email & password. This is protected by a
   (re)captcha. There is already a lib for PHP for recaptcha.
 o The system stores a cookie and sends the authentication code to the
   email specified (just like mailman)
 o The user clicks on the web authentication URL and the web app calls
   a cli app that creates the account

In our case the cli app will be pushing the credential data to an LDAP
server, another implementation could use htdiegst files, /etc/passwd,
(l)useradd etc.

It is not much different from what mailman does other than adding a
captcha.
-- 
Axel.Thimm at ATrpms.net

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2007-08-21 14:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 13:31 [lm-sensors] Submitting motherboard-specific support? (w/ attached Romain Dolbeau
2007-08-20 16:25 ` [lm-sensors] Submitting motherboard-specific support? (w/ Juerg Haefliger
2007-08-20 17:27 ` Juerg Haefliger
2007-08-20 17:58 ` Jean Delvare
2007-08-20 20:44 ` Hans de Goede
2007-08-20 21:12 ` Ivo Manca
2007-08-21  8:45 ` Jean Delvare
2007-08-21 10:35 ` Axel Thimm
2007-08-21 11:10 ` Romain Dolbeau
2007-08-21 14:38 ` Axel Thimm [this message]
2007-08-21 14:50 ` Jean Delvare
2007-08-21 17:17 ` Jean Delvare
2007-08-21 17:38 ` Axel Thimm
2007-08-22 19:45 ` Sebastian Flothow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070821143848.GE6770@puariko.nirvana \
    --to=axel.thimm@atrpms.net \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.