Thanks! We're looking for folks to help us in this effort as well - and we have a serious offer to any developer who helps out:
If you contribute code (a patch, a new feature, etc.) that goes into the standard release of the Sputnik Gateway, you get free roaming for life. (Whichever is shorter, yours or ours)
Join up on the developer list, which is what we've got until the full-blown developer site is finished.
It's in the compressed filesystem in lxcr-bbc-2_0.cloop in the root directory of the ISO/CD.
To get to it, do the following:
extract_compressed_fs lxcr-bbc-2_0.cloop >/tmp/myloopfs mkdir/tmp/fs mount -o loop/tmp/myloopfs/tmp/fs
The filesystem will be all there in/tmp/fs
Enjoy.
We'll put things up in a tarball (and we're working on debs and rpms as well) as soon as we get our developer site up, should be before the end of the month.
Yeah, but the problem is that you can only do Host-AP mode with the Prism 2 (and 2.5) cards. The Lucent and Cisco cards require proprietary firmware to enable this functionality.
Of course, you're free to your opinion, but we really are serious about working with ISPs to make sure that they make a profit on the additional bandwidth, if they are willing to change their AUPs. And we are just as serious in that we don't want people violating their AUPs and providing service that they are not allowed to provide.
We sat down with a number of ISPs before rolling this out, and we think we've worked out a reasonable business model to encourage ISPs to parter with us, or at least, to change their restrictive AUPs to allow Sputnik Gateways - the ISPs get a cut of the revenue stream in return.
We are always interested in hearing your feedback and comments as well - drop me an email at dsifry at sputnik dot com.
All the changes that we made are distributed on the ISO. We don't screw around with Open Source licensing, God knows we've been there, and we play by the rules.
Yup, they're on the ISO. We used a compressed filesystem to reduce the ISO size by about 75% - but you can extract and loopback-mount the filesystem on the CD. You can also boot the CD and see the Nocat changes on the running filesystem - they're in/usr/local/nocat/
That's exactly what happens. All the usernames and passwords (and unique tokens as well) are transmitted via SSL from the client direct to our authentication server and then only the token is sent back to the gateway.
All of the authentication communication is done via SSL to our servers. So, even if someone is sniffing the connection, they can't get any info from you.
Any, you have to reauthenticate (via a minimized pop-up window) every 10 minutes or you're auto-logged out, so the window for session hijacking is small.
That's right - we started with the great code that the NoCatAuth guys wrote, and made some patches to do things like tunneling and use a more secure SSL-based username/password token method, and re-released the code back to the community. Go check out the NoCatAuth project - they're doing some great stuff.
Slashdot Mirror
Thanks! We're looking for folks to help us in this effort as well - and we have a serious offer to any developer who helps out:
If you contribute code (a patch, a new feature, etc.) that goes into the standard release of the Sputnik Gateway, you get free roaming for life. (Whichever is shorter, yours or ours)
Join up on the developer list, which is what we've got until the full-blown developer site is finished.
It's in the compressed filesystem in lxcr-bbc-2_0.cloop in the root directory of the ISO/CD.
/tmp/myloopfs /tmp/fs /tmp/myloopfs /tmp/fs
/tmp/fs
To get to it, do the following:
extract_compressed_fs lxcr-bbc-2_0.cloop >
mkdir
mount -o loop
The filesystem will be all there in
Enjoy.
We'll put things up in a tarball (and we're working on debs and rpms as well) as soon as we get our developer site up, should be before the end of the month.
Yeah, but the problem is that you can only do Host-AP mode with the Prism 2 (and 2.5) cards. The Lucent and Cisco cards require proprietary firmware to enable this functionality.
Of course, you're free to your opinion, but we really are serious about working with ISPs to make sure that they make a profit on the additional bandwidth, if they are willing to change their AUPs. And we are just as serious in that we don't want people violating their AUPs and providing service that they are not allowed to provide.
We sat down with a number of ISPs before rolling this out, and we think we've worked out a reasonable business model to encourage ISPs to parter with us, or at least, to change their restrictive AUPs to allow Sputnik Gateways - the ISPs get a cut of the revenue stream in return.
We are always interested in hearing your feedback and comments as well - drop me an email at dsifry at sputnik dot com.
All the changes that we made are distributed on the ISO. We don't screw around with Open Source licensing, God knows we've been there, and we play by the rules.
Yup, they're on the ISO. We used a compressed filesystem to reduce the ISO size by about 75% - but you can extract and loopback-mount the filesystem on the CD. You can also boot the CD and see the Nocat changes on the running filesystem - they're in /usr/local/nocat/
That's exactly what happens. All the usernames and passwords (and unique tokens as well) are transmitted via SSL from the client direct to our authentication server and then only the token is sent back to the gateway.
All of the authentication communication is done via SSL to our servers. So, even if someone is sniffing the connection, they can't get any info from you.
Any, you have to reauthenticate (via a minimized pop-up window) every 10 minutes or you're auto-logged out, so the window for session hijacking is small.
That's right - we started with the great code that the NoCatAuth guys wrote, and made some patches to do things like tunneling and use a more secure SSL-based username/password token method, and re-released the code back to the community. Go check out the NoCatAuth project - they're doing some great stuff.