If it helps, I believe the specific backports I created for kernel v3.3.8 and compat-wireless-2012-09-07 are generally independent of application layer within OpenWRT.<br><br>So, whenever the DR1 release candidate is assembled into a coherent whole, if the underlying OS doesn't already have the kernel and radio drivers from Attitude Adjustment, then these backports may work on that too:<br>
<br><a href="https://code.commotionwireless.net/projects/commotion-openwrt/repository/revisions/ath9k_new/changes/patches/backport_kernel_3.3.8.patch">https://code.commotionwireless.net/projects/commotion-openwrt/repository/revisions/ath9k_new/changes/patches/backport_kernel_3.3.8.patch</a><br>
<a href="https://code.commotionwireless.net/projects/commotion-openwrt/repository/revisions/ath9k_new/changes/patches/backport_compat_wireless_09-07-12.patch">https://code.commotionwireless.net/projects/commotion-openwrt/repository/revisions/ath9k_new/changes/patches/backport_compat_wireless_09-07-12.patch</a><br>
<br>My original motivation for creating the backports was that the
compat-wireless drivers included with the version of Commotion pinned to
trunk r31639 didn't work very well with the ath9k_htc USB wifi adapters
I'd been using. That, and the fact that I too had a personal copy of Attitude Adjustment that I had been toying around with for purposes vaguely tangential to Commotion.<br><br>Perhaps one day everyone's secret copies of Attitude Adjustment will be merged together . :)<br>
<br><div class="gmail_quote">On Mon, Jan 21, 2013 at 9:52 PM, Dan Staples <span dir="ltr"><<a href="mailto:danstaples@opentechinstitute.org" target="_blank">danstaples@opentechinstitute.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Right now a most of the new code for DR1 that we've been working on is<br>
in various repos on the OTI github account:<br>
<a href="https://github.com/opentechinstitute" target="_blank">https://github.com/opentechinstitute</a>. Everything has yet to be compiled<br>
into a single source tree, since plenty of it isn't finished yet.<br>
<br>
As for the backports, I really have no idea. I know Josh King has been<br>
working on bringing Commotion-OpenWRT up to Attitude Adjustment, and<br>
I'm not sure what kernel version that uses. I apologize that our DR1<br>
efforts haven't been well documented or announced. I think in the<br>
future, it would be good for us Commotion developers at OTI to be more<br>
transparent with what we're working on, at least for the reason that<br>
it's important for everyone to be on the same page...it would be crummy<br>
for someone to be working on something that is then made obsolete by<br>
something someone else is working on!<br>
<br>
We've been pretty good about tracking our DR1 efforts on the Commotion<br>
issue tracker. You can check out the DR1-specific stuff here:<br>
<a href="https://code.commotionwireless.net/projects/commotion/issues?set_filter=1&f[]=fixed_version_id&op[fixed_version_id]=%3D&v[fixed_version_id][]=2&f[]=&c[]=tracker&c[]=status&c[]=priority&c[]=subject&c[]=assigned_to&c[]=updated_on&group_by=" target="_blank">https://code.commotionwireless.net/projects/commotion/issues?set_filter=1&f[]=fixed_version_id&op[fixed_version_id]=%3D&v[fixed_version_id][]=2&f[]=&c[]=tracker&c[]=status&c[]=priority&c[]=subject&c[]=assigned_to&c[]=updated_on&group_by=</a>.<br>
<br>
Here are some highlights of what we've been working on for DR1:<br>
<br>
* A cross-platform Commotion daemon written in C, to manage all the<br>
Commotion components and handle configuration<br>
* Quick Start wizard to guide the user through setting up a node on<br>
first boot<br>
* Application advertisement and discovery (using mDNS/DNSSD) and<br>
OpenWRT application web portal<br>
* Enhanced security features, such as AuthSAE and a OLSRd-secure plugin<br>
to sign routing traffic with Serval keys<br>
* A new LuCI theme to match <a href="http://commotionwireless.net" target="_blank">commotionwireless.net</a><br>
* A Commotion-OpenBTS live distro with Serval integration<br>
<br>
Dan<br>
<div class="im"><br>
On Mon 21 Jan 2013 09:29:28 PM EST, Ben West wrote:<br>
> This is encouraging to hear. Is the code base for DR1 RC somewhere on<br>
> the git repo at <a href="http://code.commotionwireless.net" target="_blank">code.commotionwireless.net</a><br>
</div>> <<a href="http://code.commotionwireless.net" target="_blank">http://code.commotionwireless.net</a>> at present, or is that also<br>
<div class="im">> pending release soon too?<br>
><br>
> At any rate I won't commit anything to the master branch for a default<br>
> root password.<br>
><br>
> (Also, I hope the back ports for the newer kernel and compat-wireless<br>
> drivers mentioned in the other thread are still of use. Or maybe<br>
> they're now already obsolete ...)<br>
><br>
> On Monday, January 21, 2013, Dan Staples wrote:<br>
><br>
> We actually have an entire quick start wizard in the works now for the<br>
> Commotion DR1 release candidate, which should be released shortly.<br>
> This<br>
> will walk the user through all the steps of configuring a device,<br>
> including root password, or uploading a configuration file, upon first<br>
> boot. So I would say setting a default password would probably not be<br>
> needed in this case.<br>
><br>
> Dan<br>
><br>
> On Mon 21 Jan 2013 07:10:24 PM EST, L. Aaron Kaplan wrote:<br>
> ><br>
> > On Jan 21, 2013, at 11:34 PM, Ben West <<a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a><br>
</div><div><div class="h5">> <javascript:;>> wrote:<br>
> ><br>
> >> This is why I ask. What is preferred method for letting users<br>
> specify a root password?<br>
> ><br>
> > Yeah, a hard problem.<br>
> ><br>
> > Ideally you generate one initially and display it on some LCD<br>
> once ;-)<br>
> ><br>
> > The problem that I see with having the password a well known<br>
> default password is that usually people forget to change it.<br>
> Search engines then find those devices on the internet. And they<br>
> are sort of p0wned by definition then :)<br>
> ><br>
> >><br>
> >> OpenWRT by default has no root password set, expecting you<br>
> first telnet in to set the password. This doesn't seem to play<br>
> nicely with the automated configuration that the meshconfig tool<br>
> tries to do. I had thought that compiling in a default root<br>
> password into images did not change the (lack of) security of this<br>
> arrangement any all, while at least letting meshconfig run to<br>
> completion.<br>
> >><br>
> > Well.... I did discover some openwrts in the wild which are<br>
> default, unconfigured and once you greet them with a telnet login<br>
> attempt, they will greet you back with a prompt ("#") sign. No<br>
> password required. Yikes.<br>
> ><br>
> ><br>
> > Personally I recommend the following:<br>
> > Step 1: an unconfigured mesh node generates a random password<br>
> > Step 2: it connects to some central server and fetches its<br>
> configuration.<br>
> > Step 3: It reconfigures itself based on the configuration stored<br>
> in the nodeDB. The user can change the pwd from a nodeDB/dashboard.<br>
> ><br>
> > (I know this conflicts with the totally distributed approach of<br>
> commotion, but that's how we will do it initially with our new<br>
> nodeDB at Funkfeuer)<br>
> ><br>
> > That's one way to do it. ssh keys are a different one. X509<br>
> certificates also come to mind.<br>
> > I am open to better suggestions.<br>
> ><br>
> > a.<br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Commotion-dev mailing list<br>
</div></div>> > <a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a> <javascript:;><br>
<div class="im">> > <a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
> ><br>
><br>
> --<br>
> Dan Staples<br>
><br>
> Open Technology Institute<br>
> <a href="https://commotionwireless.net" target="_blank">https://commotionwireless.net</a><br>
> _______________________________________________<br>
> Commotion-dev mailing list<br>
</div>> <a href="mailto:Commotion-dev@lists.chambana.net">Commotion-dev@lists.chambana.net</a> <javascript:;><br>
<div class="im">> <a href="https://lists.chambana.net/mailman/listinfo/commotion-dev" target="_blank">https://lists.chambana.net/mailman/listinfo/commotion-dev</a><br>
><br>
><br>
><br>
> --<br>
> Ben West<br>
> <a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br>
</div>> <a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a> <mailto:<a href="mailto:ben@gowasabi.net">ben@gowasabi.net</a>><br>
> <a href="tel:314-246-9434" value="+13142469434">314-246-9434</a><br>
<div class="HOEnZb"><div class="h5">><br>
<br>
--<br>
Dan Staples<br>
<br>
Open Technology Institute<br>
<a href="https://commotionwireless.net" target="_blank">https://commotionwireless.net</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ben West<div><a href="http://gowasabi.net" target="_blank">http://gowasabi.net</a><br><a href="mailto:ben@gowasabi.net" target="_blank">ben@gowasabi.net</a><br>
314-246-9434<br></div>