By RobinMonks on

It's time for some old school open source! Here is the very basic source code to a securesite.module, the idea is to create a full module by the end of this thread.
And, yes, this is the $500 module mentioned elsewhere on the forum. I, personaly, don't think it's right to pay some volenteers to..um..volenteer. So, hence my idea for old school open source. (hey, if they still want to give away the money then get some t shirts to pass around :o)

The first randition of the module is at http://paste.lisp.org/display/7493 , and probably dosn't work right. But it a start.

Here are the rules:
Each person contributes something to the module in each post
Use paste.lisp.org's annotation features to add the changes
The finished module will be submitted to the Core (and added at Dries' descression

Let show the real spirit of Open Source!

Comments

boris mann’s picture

boris mann commented

That's the whole point of a "reverse bounty". These are NOT volunteers: a Drupal developer has the skills to develop a module, but has a day job/other paying gigs. If they could get paid to work on a module, they could set aside the time to build it. The bounty system matches the desire/skill to build a module with a community of people that don't code, but also want the functionality

But in any case, I'll consider this a "donation" to the code. If you want to finish the entire thing, I'll be happy to transfer the money to you.

I put a link to this thread from the original discussion.

RobinMonks’s picture

RobinMonks commented

Nah, I understand that. But I think haveing a community built module in this way is better, especialy on a simple module like this.
I'd rather see rasied money go to a newspaper ad, or some sort of other promotion. But it's up to the donators, of cource ;)

Robin

RobinMonks’s picture

RobinMonks commented

For those who don't understand HTTP Auth, a good tutorial is on the Zend site at:
http://www.zend.com/zend/tut/authentication.php

Come on! Time to see those contributions!

Robin

RobinMonks’s picture

RobinMonks commented

Here is a near-workable version of the module.

http://paste.lisp.org/display/7493#2

There are still kinks which I'm sure someone could easily fix.

dikini’s picture

dikini commented

The last paste will probably work. I have a few comments though.

Authentication and login can be done in many ways, like the drupal default login box, httpauth, using js challenge-response, using other transport credentials like ssl/tls... An 'authentication method' hook might be calling.

So a true good solution, should facilitate method independance. Ultimately should go in core, after being tested, of course.

I like the use of menu, but in order for http-auth to be transparent, i.e. not issued when not requested or required, menu will need to do some url manipulation. For example, let's take an auth/node path. This can be interpreted as "I want to authenticate myself, I want to have my node list".

  ....
  //in a menu callback somewhere
  ...
   {do the authentication}
  //hackish, but nessesary - if we are here the ?q=auth/....
  $arg = explode('/', $_GET['q']);
  array_shift($arg);
  $path = implode($arg);
  drupal_goto($path);
  ....

And an off-topic comment, I still think bounties - whether user initiated or developer can be a good thing. Boris's experiment is worthwhile, since it can encourage developers spend time on drupal.