[Wifidog] Version 1.0

[Mina Naguib]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Good stuff Philippe

I don't know if you're familiar with this or not, but CVS has something 
called "tags"

A "tag" in CVS is a snapshots of all the files in time.  It would 
alleviate the need for all the diff's and tarballs you've been worrying 
about.

See:
http://www.google.com/search?num=100&hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&q=CVS++tags&btnG=Search

Tags are great for milestones (such as software releases) as well as 
before and after major changes.  Typically before a major change 
affecting many files is done, the tree will be tagged like 
"majorchangename_PRE" and after done, "majorchangename_POST"

Philippe April wrote:
>>	This was the essence of my original idea and the main reason behind
>>the code as it stands. I'd rather have the AP download UserClass
>>definitions
>>from the Auth Server then have the Auth Server make decisions.
> 
> 
> We just need to make sure this is really what we want, and design exactly
> how we want to do it and what we want to achieve.
> 
> So for now, I took out your userclasses, because we would not use them in
> version 1.0.
> 
> Also, the way I had originally done the profiles and the tagging in the
> firewall is tricky, and I don't think it's what we should aim for.
> 
> Now, since nobody but me has a working testbed or is willing to play with
> iptables, it's tough.
> 
> I have questions regarding classes and groups, like:
> 
> - how many classes do we want to have?
> - what information is in a class?
> - how can a hotspot owner manage the classes?
> - how would groups be implemented and how would we use them?
> 
> So for now, I did a tarball of something that works, I took out the
> userclasses, etc. so it's really simple.
> 
> There are some features we want for 1.0 that are now implemented, but they
> are tricky, you will see by looking at the code or by making it work
> (again, nobody makes it work fully but me, that's a problem).
> 
> My opinion is that I think it'd be great to commit in CVS and say "ok this
> is version 0.9.0" or something, and then build up and fix until we're at
> 1.0.
> 
> Go get the tarball, look at it, I stripped down stuff, implemented some
> other things, etc.
> 
> You can get it at http://www.philippeapril.com/wifidog/wifidog-0.2.0.tar.gz
> 
> I'm running it right now and it seems to work fine. I'm able to create a
> new account if I don't have one (some code had to be implemented on the
> auth server which is not in the tarball but will be soon, sorry).
> 
> Please all let me know what you think as soon as you can. I'll be testing
> at home.
> 
> Philippe April
> 
> 
> _______________________________________________
> Wifidog mailing list
> Wifidog at isf.waglo.com
> http://isf.waglo.com/mailman/listinfo/wifidog_isf.waglo.com
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAiFEyeS99pGMif6wRAg6xAJ4lPfQ8lZ6lXv3ShsB4RmfIICgXSACeJ87l
M+uDpOxaA/sjFJkviUWgU/Y=
=CJaV
-----END PGP SIGNATURE-----

-------------- next part --------------
_______________________________________________
Wifidog mailing list
Wifidog at isf.waglo.com
http://isf.waglo.com/mailman/listinfo/wifidog_isf.waglo.com