Openmoko

Photo courtesy Photos8.com

Ok, maybe not the killer but then at least the delayer.
But it did get your attention right?

As usual I am struggling just to get the phone working as a receiver of SMS messages.
Trying to figure out where gsm0710muxd writes it log files by default I fetched the source.

I know it is sort of deprecated but I’m trying to get my Debian based install up and running.
And the Debian dependency graph lists it as a dependency of fso-frameworkd…

gsm0710muxd states: THIS_IS_DEPRECATED_USE_LIBGSM0710MUX
libgsm0710mux states: DEPRECATED_PLEASE_USE_CORNUCOPIA
And of course there is also
fso-abyss.git the “GSM 07.10 Multiplexer (NG)” (which is deprecated in favour of cornucopia)

To sum it up we have 4 different implementations of a GSM multiplexer… no wonder I am a bit confused which to use.

But why not just “apt-get install cornucopia” and leave the past behind?
Well I would but unfortunately it seems that the bleeding edge phone software needs a bleeding edge “valac 0.9.3-3″
which even the vala developers consider a development release which prevents it from entering the Debian unstable distro.

Being a fan of C and C++ (if you can spare the “disks” space for the std. library)
I sure would have preferred if the more proven and stable platform  C were used than this new kid on the block valac
which I did not even know existed prior to its usage on the Neo/Freerunner.
It sure would make it easier to port it to other distros than SHR.

And then there is SHR and the whole home-grown Illume 1and 2 issue, focus bugs, all new bugs in V2 (I have not tried it as the mailing list scared me away).
Being slightly conservative with regard to this whole new software ting. What is wrong with say matchbox as far as I know it mostly just works.
Okay it is not thumb friendly per standard, but a little themeing seemed to do the trick for Nokia and the 770/800/810.
And GTK seems to do the trick for my desktop PCs, and it seems slightly more stable that the fancy Enlightenment tool kit.
At least I can not remember having any problems giving focus to a text input field.

But is  SHR not the  most advances phone distro?
It is, however it lacks the diversity of available packages of Debian, and I find the the build system beaks way to easily for my taste.

Why do I believe that all this may be harmful?

• If there are lots of things that do not work you are more tempted to not use the FSO phone this includes UI misfeatures.
  I once used it as my primary phone but have reverted back to an ancient Nokia 6100.
• Using new tools makes it harder to gain support from the community as less people know them.
• Lots of rewrites causes bad documentation, as no one has the time to write it.
  It also makes it harder for the occasional hacker to get anything done as everything is new at each rewrite.
  It also puts an increased strain on other distro maintainers as they have to keep up, not only with the new services but also the new dependencies.

Last but not least:
Remember the ones writing the code is always right.
If you don not agree with them do not write blog entries, write code.

To: Michael ‘Mickey’ Lauer, the SHR and Pkg-FSO team
Keep up the good work, I can not imagine how you get any real life activities done as well as coding this much.

I'm excited to be giving two presentations at Debconf 10, held this year on the Columbia campus in New York City.

The first is "FSF's Campaigns for Freedom" on Sunday, August 1st, from 14:00 to 15:00 in 414 Schapiro. I'll give an overview of some of the current FSF campaigns, like the GNU Project, Working Together for Free Software, Defective by Design, PlayOgg, Windows 7 Sins, and the High Priority Projects List; and resources like the Licensing & Compliance Lab, Free Software Jobs page, Hardware Directory, and the Free Software Directory. But I'm going to save plenty of time to talk with the room about things the FSF should or could be doing.

The second is "Patent Absurdity: How software patents broke the system" on Thursday, August 5th, from 14:00 to 15:00 in the Davis Auditorium. We'll be watching the Patent Absurdity film, chatting about what's happened since, and what the Bilski decision means for the future of free software.

I'll be around the conference all week, so drop me an email at johns@fsf.org or catch me in the #debconf channel (johns) if you want to chat about the FSF or GNU.

Dieter Spaar, who has been involved in various ways with both OpenBSC and OsmocomBB has just started a blog. This is good news and I hope this way he will get a bit more (much deserved) exposure on his great work.

At Blackhat US 2010, there was a Talk that (among other things) apparently included the subject of a RACH DoS on GSM base stations, implemented using my Layer1 of the OsmocomBB software.

As some news sites are covering this as "news": This vulnerability has been long known in the field and was - to the best of my knowledge - first demonstrated to a public audience by Dieter Spaar at the Deepsec 2009 conference in November 2009. You can get his slides.

The difficult part for many years has not been to know about the possibility of this weakness. Anyone who has read the GSM air interface specification will inevitably see that there is a limited number of RACH slots and a limited number of dedicated channels. Once you fill more RACH slots than the cell has dedicated channels, and you keep re-filling them at a higher rate than the cell can expire those dedicated channels, you have a DoS.

So rather, the difficult part was to implement it in practise, as traditionally all GSM baseband chipsets have been extremely closed, just like the very software (firmware) running on them. Today, starting from Q2/2010, it is very easy to do a proof-of-concept implementation, as we have created OsmocomBB: An Open Source baseband firmware.

Dieter Spaar's implementation predates OsmocomBB development by the better part of a year. At that time, he had to resort to binary-patching existing proprietary (binary-only) baseband firmware. So I think people should recognize his effort in doing the first practical implementation of that attack.

I can only hope that the author of the Blackhat presentation has given proper credits and shown that neither OsmocomBB, nor the RACH DoS attack, nor the IMSI DETACH attack he has presented have been discovered or first published by him.

At Blackhat USA 2010, Karsten Nohl has been presenting on a practical real-world A5/1 cracking attack. For recent years, Karsten, myself and others have been speaking at various opportunities, indicating that a practical attack using readily-available information and tools from the Internet is very possible, and that it is only a matter of time for somebody actually does it.

While Karsten has focused on the actual cryptographic attack, I've been putting in some time in projects like airprobe (a GSM receiver/decoder).

Now finally, a team of friends at the new Security Research Labs (founded by Karsten) in Berlin has put the pieces of the puzzle together.

Airprobe has been extended to fully support decoding of TCH/F (FACCH, SACCH and traffic), as well as SDCCH/SACCH control channels, and to specify the timeslot and physical channel configuration from the command line. Using this, you can

• decode the AGCH, wait for an IMMEDIATE ASSIGNMENT of a SDCCH
• decode that very SDCCH and wait until encryption is turned on
• dump an encrypted burst where you have sufficient known plaintext
• use a different program to actually recover the A5/1 ciphering key
• feed that key into airprobe and decrypt+decode the ASSIGNMENT COMMAND of the TCH
• use airprobe to decrypt+decode that assigned TCH/F

The external program to recover the A5/1 ciphering key is called Kraken and is also available from the SRLabs website.

So what are the limitations? Well, so far this only works on non-hopping cells with a single ARFCN. The limitations are those of the receiver hardware (and SDR software), and not really limitations of the airprobe GSM decoder or the actual software tools.

In the past I would have assumed that non-hopping and/or single-ARFCN cells are rare, but in fact we can find them even inside a big city like Berlin, from at least two of the four German GSM operators. So that's why this attack is very practical, no matter what the GSMA might say.

Damien, Neil and I gave our joint talk about doing interesting and unusual things in Clutter yesterday. I think it went down alright, hopefully we can give more of this kind of talk in the future, showing people how you can use Clutter in cool ways.

For my part of the talk, I spoke about developing small, fun games. I intended the advice I gave to apply to developing any small game with anything, though it definitely applies to making games in Clutter. You can find the text and slides for my talk here. Like Neil and Damien (and the rest of the Intel OTC crew), I wrote my talk in pinpoint, pippin's excellent, new, Clutter-based presentation tool.

I wrote two games before the talk:

Both of these games are available from my git repository. Pill-popper works with any recent version of Mx and Clutter, Happy Wombats currently requires master clutter-box2d and the 'kinetic-scrolling' branch of Mx (which should shortly be merged - I'll update this post when it is). When these games are more complete, I hope to submit them to the MeeGo garage, and perhaps suggest their inclusion for gnome-games.

Happy Wombats includes an editor, so I'd love to receive some levels at some point. I'll be improving things soon, but it's already quite easy to use. Guadec has been great so far, I hope we can keep up the momentum of awesome developments until the next one :)

Už je tomu tři čtvrtě roku, co Openmoko Inc. uvedlo WikiReader. Se svolením Sean Moss-Pultze, ředitele společnosti Openmoko Inc. publikuji náš krátký rozhovor ohledně úspěšnosti WikiReaderu na trhu a budoucnosti Openmoko. > May I have a question? How is it going with WikiReader? Are WikiReader > sales satisfactory? Much better than expected. We're getting into major US retailers this summer. And launching in Japan tomorrow. We've...

EDIT: USB network je s těmito verzemi mapováno na usb0, pozor na to! EDIT 2: Kernel pro SHR s WS fix: http://www.bsdmn.com/openmoko/glamo/242/shrkernel_nows/ Gennady Kupava (aka gena2x na irc) zveřejnil výsledky svého testování a ladění nastavení sběrny Glama. Zkuste sami, flešujte buďto u-boot nebo qi: http://www.bsdmn.com/openmoko/glamo/242/u-boot_glamo242.udfu http://www.openmobile.nl/modules/download_gallery/dlc.php?file=53

After traveling a bit too much in the past weeks, I’m back in Taiwan, well rested and super inspired to resume this weekly book club.

In the air, I read an interview with one of my heros, Sir James Dyson:

PHOTO: DEREK HUDSON / GETTY

Dyson is best known for his colorful bagless vacuum cleaners, which work on the principles of cyclonic separation. When asked about his most important lesson in life, he replied:

It can take a very long time to develop interesting products and get them right. But our society has an instant-gratification thing. We admire instant brilliance, effortless brilliance. I think quite the reverse. You should admire the person who perseveres and slogs through and gets there in the end.

I love this quote! Yes, it’s wisdom that – 50 years ago – would have been taken as common sense. But things are different now. Instant gratification is getting the better us. It’s seeping into our industries, destroying our economies, and wrecking havoc on our core values. So many of us succumb to the unfortunate idea that we live in a time where the rules of the past don’t apply. I, too, have been convinced that changes like the Internet mean real value can be created overnight. But I cannot accept this anymore. I do not believe in instant or effortless brilliance. Behind every lasting success is an immense amount of hard work, failures, and above all, a relentless desire to go forward, no matter what happens. It takes an enormous amount of time and courage to reach a “breakthrough”.

Dyson built 5,127 prototypes before he got his vacuum cleaner right. And then he was rejected by all the major manufacturers when he tried to license them his invention. Discouraged but not distraught, he decided to start his own company. That took him 15 years and nearly his entire savings. But he persevered. Today, he has the best selling vacuum cleaner (by revenue). One of the most popular brands in the market. And is one of the richest individuals in the UK.

Read the daily news and seldom will you hear the true story of success. You’ll find the overnight wonder. The company that came out of nowhere. The business person who made a billion dollars – entirely with their own hands. Worse than untrue, I believe propagating these myths does real damage to the values of our society. Convinced that this is reality, we become disillusioned by anything slower than real-time. We take failure as a sign to change jobs instead of an opportunity to learn and grow. We loose our tenacity and ability to concentrate for extended periods of time on difficult problems. We choose to enter professions where trading is rewarded far more than building long-term value for society.

Thinking about all of this reminded me of a book I read a while back, entitled, “Outliers: The Story of Success“, by Malcolm Gladwell:

Outliers is Gladwell’s study of success. It’s a story told, in my opinion, the right way. From the Beatles to Bill Gates, New York Lawyers to Silicon Valley Billionaires, Gladwell argues that hard work and the right environment, is far more important that just plain intelligence and ambition in explaining success.

Central to the book’s theme is the following question: “Why do some people succeed, living remarkably productive and impactful lives, while so many more never reach their potential?”. Gladwell lays out a convincing case for how successful people rise in our society. His book is fun and insightful. Definitely worth reading. Today, I just want to share one quote with you, since I believe it best captures Gladwell’s point, without spoiling the plot:

The lesson here is very simple. But it is striking how often it is overlooked. We are so caught in the myths of the best and the brightest and the self-made that we think outliers spring naturally from the earth. We look at the young Bill Gates and marvel that our world allowed that thirteen-year-old to become a fabulously successful entrepreneur. But that’s the wrong lesson. Our world only allowed one thirteen-yar-old unlimited access to a time sharing terminal in 1968. If a million teenagers had been given the same opportunity, how many more Microsofts would we have today? To build a better world we need to replace the patchwork of lucky breaks and arbitrary advantages that today determine success – the fortunate birth dates and the happy accidents of history – with a society that provides opportunities for all.

We study the sciences to better understand our universe. We’re required to read the classics to experience humanity’s prowess. Why aren’t we taught the journeys of success to learn how to repeat them? Why don’t we elevate those, as Dyson so bluntly states, that “persevered and slogged” and got there? Why don’t we work to provide the environments that mold and shape outliers? Like Gladwell and Dyson, I believe our future depends on it.

If any of this interests you, and you would like to read this book, tell three people about my company’s latest project, WikiReader, and then send me an email. Before next week, I’ll chose a name from random, and send the winner my book.

Shipping, anywhere in the world, is on me.

On my Debian box the following were used:

/etc/ssl/certs/dovecot.pem and /etc/ssl/certs/dovecot.pem were the default locations check your /etc/dovecot/dovecot.conf before running.

openssl req -new -x509 -nodes -out /etc/ssl/certs/dovecot.pem -keyout /etc/ssl/private/dovecot.pem -days 3650

/etc/init.d/dovecot restart

I got tired of renewing the certificate so I issued one that lasts 10 years.
(apparently it does not take that much to make me tired)

向大家介绍一个 Ben NanoNote 平台下的开源项目：

1. IRIS
Iris 是以 Ben NanoNote 为平台的 微内核 系统，主要目的是发挥硬件的最大性能。 IRIS 是用 python 格式的C++语言写的（我喜欢）。用户可以在不刷机的情况下测试使用这个系统。它是由 Bas 从 0 开始写的一个专门在 Ben NanoNote 上运行的系统。对想学习操作系统的人来说是一个很好的例子。这里是所有的源代码。
（我们总是公开源代码，因为我们相信共享总是激发创造力）

2. GPS
这里是英文的介绍，教大家如果将 GPS 模块连接到 Ben NanoNote 上。
并使用 TangoGPS 和 Jlime 系统如果使GPS工作。 （Jlime 在我的上一个文章里已经介绍过了），对GPS感兴趣可以参考一下。

另外一个关于GPS 的软件项目叫 NanoMap. 是以QT + Openstreetmap.org 写成的。

3. setfont2
Neil 给写了一个补丁。可以让FBCONSOLE 支持 32bit color 字体，setfont2 一个有意思的小程序。字休文件格式是 pnm。
一种图片格式。

4. 新的软件包
最近在 nanonote 很多人一起努力，移植了很多的软件包，包括 jfbterm， 这样我们就可以在 Ben NanoNote 的终端下使用中文了。这里凡是以 [new package] 开头的都是新的软件包。

happy hacking

In recent days, the story about Motorola locking out its users (and developers) from their more recent Droid phones has made big news. As it seems, the exact functionality implemented by eFuses remains unclear, and the behavior of Motorola might thus not be too different from what has more or less become the industry standard.

For those of you who are not following the mobile world as close on a technical level as people like me do: In the last five years, more and more cellphone manufacturers have used cryptographic code signing to lock-down the software that you can run on the phone. Major parts of the system including the software update mechanism and the bootloader on the device contain a verification process of those cryptographic signatures to ensure that you can only software signed by the phone manufacturer.

I have seen this with the MotoMAGX phones like the ROKR2 v8, various Windows Mobile handhelds from HTC, The non-developer (non-ADP) version of the Google/Android G1 and many other phones.

This puts the user into a strange situation where he buys some hardware from the manufacturer, but yet doesn't have control over what this device does. Just imagine buying a computer, but being limited to run Windows 98 and Office 97 on it. You could not update to a later version of the operating system, and you could not install an alternative operating system such as a version of GNU/Linux. If the computer vendor decides that he will drop support for it, you will not even be able to install security updates to the operating system.

From my point of view, this is an abusive, anti-competitive behavior by the manufacturer. For no reason but his ever-growing hunger for power he makes you completely dependent on his decision. It is not in the control of the user, what operating system or even applications you can install. It is under the control of the manufacturer.

I would accept this if the phone was rented. In this case, I would only pay a small rental fee, but the phone is the property of the manufacturer and I am only using it. But the manufacturer actually sells the device. He wants to be paid the full price, but still not actually hand control over to the buyer.

Compare this with buying a CD-player that has arbitrary restrictions so it would only play CDs from one of the major music labels/distributors like EMI, but not CDs from any of the other publishers, for no technical reason whatsoever. Or buying a TV set that is locked down so you can only watch one TV channel, while you need to buy another TV for a different channel.

I actually think the antitrust authorities should investigate this behavior of the mobile phone industry. Simply compare it with the PC situation and look at the fact how often Microsoft has been judged in some kind of anti-competitive behavior in the PC world. In the mobile phone industry, the situation is worse than it ever was in the PC world, yet we do not see big antitrust cases being brought forward.

And please don't buy those pseudo-arguments that this has any relation to regulatory/FCC approval or the safety of mobile networks themselves. The entire software stack interacting with the mobile network runs on a separate processor (the baseband processor) anyway. It doesn't matter what you install on the application processor. Once again, compare it to laptops: You can insert a 3G miniPCI, expressCard or USB dongle. Inside this dongle you run the communications stack on a processor that is completely different from your main processor that runs your regular OS (be it GNU/Linux, OS X, Windows, Solaris or whatever makes you happy).

There are plenty of reports in recent days about the level of locking-down that Motorola is apparently doing on their most recent Android products, the Droid 2 and the Droid X.

This goes as far as to an (I believe unconfirmed) slashdot.org report claiming that not only there is the more or less typical DRM on software (i.e. cryptographic signature validation chain), but there also is an eFuse that that is blown if something happens wrong during the booting process.

To the best of my knowledge (and I'm doing mobile phone reverse engineering for about 6 years now), this is the first time I hear of something like this. If true, it sounds pretty dangerous to me. What if something goes wrong during an update (such as a power failure during software update)? What if you really have a non-correctable multi-bit error in your NAND Flash? In that case, cryptographic verification of the firmware fails and the eFuse would be blown, resulting in your device being a brick. This could eventually backfire massively to Motorola.

The best comment from the slashdot.org thread:
You can legally buy a gun that only shoots in the direction of the person pulling the trigger, but it doesn't mean it's a good idea.

Reading something like this almost makes me very depressed. Motorola is benefitting from the billions-of-dollar-worth development of existing Free Software projects like the Linux kernel, but they now want to take away the fundamental right to run modified versions of that very software. Somebody needs to slap them with a very large trout.

I'm not really surprised that they are doing it, though. Motorola has shown that direction even years ago when they first used SELinux as part of their later pre-Android Linux phones (EZX and MAGX). They didn't use it to enhance the security of the user, but to enhance the security _from_ the user.

Please also note this great post by Bradley M. Kuhn on the subject matter. If you don't know Bradley, he's been doing GPL enforcement for the last 12 years - for the Free Software Foundation and the Software Freedom Law Center. In his post, he actually thanks Motorola to publicly state that they actually want to lock their phones down (as opposed to Apple).

What's even more interesting though is his elaboration on the scripts to control compilation and installation clause of GPLv2. This is indeed something that most people tend to overlook when it comes to GPL[v2] compliance and we see this a lot during our gpl-violations.org work.

And in fact, for a very long time, I have been teaching and educating this fact during my GPL related talks and trainings: In software specific for embedded devices, the scripts to control installation are incomplete, if you do not provide a means to install the software onto the actual device. Where else would you be reasonably install the Linux kernel image that is made specifically to work on such a particular mobile phone model? Due to the custom nature of Linux kernels for embedded targets, it wouldn't even run anywhere else.

I've never taken any such issue to court so far - but it was a frequent dispute in out-of-court GPL enforcement we've been doing at gpl-violations.org. I'm definitely curious to see what will be the first court case addressing that issue. The ever power-hungry manufacturers of mobile phones seem like they deserve it.

UPDATE:
Apparently Motorola has released some statement that denies they use eFuses to brick the device. All it does is to render the device unable to boot until some Motorola-certified/signed/authorized software is loaded on the device again. They did not specify how that could be done, though. Still, even without the eFuse bricking, I find it outrageous that the Industry (including Motorola) expect their customers pay hundreds of dollars for a device that is then still owned by Motorola rather than that very customer. It's like selling something but still retaining ownership of it. Doesn't that make you feel strange, too?

内容：无限复制的资源。不受物理限制。我们可以很轻意的复制数字内容。只需要[ cp /your/* /me/]，这不像自行车，如果你有一个自行车，我拿了它。你就没有了。但是如果我复制了 “自行车”，这样每个人就有了一辆自行车。“内容” －－ “文化” 就像是水源。有水的地方就有生命。

容器：有限的物品。像：书，DVD，硬盘等等，这些不是免费的。没有愿意免费发放这些东西。而且人们也习惯了付钱买这些东西。

版权：禁止人们共享知识，文化就像是给“内容”（信息，文化）建了一个水库，不让水自由，开放的流动。时间长了，大家可想而知。

人们喜欢艺术家的作品。喜欢这个程序员的代码。也愿意花钱买装有这些“内容”的“容器”，出版商和网站也可以发布这些发布这些资源。来让更多的人共享这些知识。艺术家和程序员需要鼓励，最大的鼓励就是人们喜欢他，支持他，这样才能创造出更多的作品。这样艺术家和程序员就可以卖出更多的”物品“（我的意思是”容器“）。所以我们必须和保证出版商，网站没有把作者的名子隐藏。

所有我们使用 [知识共享“署名] 协议。这样任何出版商，网站都可以公开发行。但是要把作者的信息让大家知道。这样喜欢这些作品的人们就可以直接联系到作者。

更多信息：

http://questioncopyright.org/understanding_free_content

http://blog.ninapaley.com/2010/01/15/the-revolution-will-be-animated/

（很多公司使用或是修改了 “自由软件” 但是不公开其中的源代码。他们认为这是他们的成果。是一种技术。就好像“教会徒弟，饿死师傅”，但是这些人们有没有想过，你认为你的代码中的技术比 GCC 还要先进？比Linux Kernel 还要先进？ GNOME？EMACS？，这些公司不明白 “自由软件” 的文化而且还要面临法律问题。）

（看看这个新闻：绿坝软件北京项目组因缺乏经费关张 所有人员遣散）

The protocol by which traditional GSM core network components interact is called MAP (Mobile Application Part). MAP itself is a user of the TCAP (Transaction Capabilities Application Part) protocol, which in turn runs on a SS7 protocol stack (i.e. SCCP over MTP or M3UA or SUA over SCTP).

For those users of OpenBSC who have a need to interoperate with other GSM networks (roaming), the circuit-switched part of OpenBSC has so far relied on the use of a proprietary MSC (by means of the A interface). This closed MSC then talks MAP/TCAP/SS7 to roaming partners.

However, on the GPRS front, we now have OsmoSGSN. However, as opposed to the BSC on the circuit switched side, the SGSN directly interacts with the core GSM network components (both of the home network and the roaming partners).

So in order to run OsmoSGSN interacting with existing HLRs, we need to add a MAP/TCAP/SS7 interface to it. Once this has been done for the SGSN, we of course can do the same for the MSC-part that is currently integrated with OpenBSC.

As there are existing implementations of SCTP (inside the Linux kernel) and SUA (sualibrary), TCAP is the next step in the protocol stack that needs to be implemented. I've been digging into TCAP for the last week(s), and believe I finally understood every part of its operation.

You can think of TCAP as something that facilitates the transport of request-response type transactions over a datagram oriented transport layer. It intends to have lower overhead than a connection-oriented service (e.g. establishing TCP sessions) and supports features such as aggregating multiple user-messages (called components) in a single actual transport-layer message. The idea is to reduce the overhead of message headers and routing.

TCAP is (unfortunately) specified in ASN.1 and thus requires significant effort to parse and construct. Right now I'm using Lev Walkin's asn1c ASN.1 C code generator to generate the parser and constructor functions. The actual TCAP protocol logic is once again implemented in plain C, using the various concepts and utility functions established in OpenBSC (and now part of libosmocore).

The implementation is making good progress and I hope I can do some early testing in about a week from now, and successively move straight to the MAP protocol, implementing at least those parts that we need for GPRS authentication and attach / routing area updates.

Červnové vydání Community Updates je poměrně obsáhlé, hlavně díky velkému množství novinek v sekci Community. Toto je jen shrnutí, v žádném případě se nejedná o překlad celého vydání, které doporučuji každému si přečíst. Na začátek se dozvíte o vývoji distribucí Debian a SHR. Vývojáři Debianu informují o tom,...

Aujourd'hui commencent les 11èmes Rencontres Mondiales du Logiciel Libre.

Un des thèmes de cette année est : Systèmes Embarqués et Matériel Libre.
Quelques événements s'annoncent incontournables :

• Le 06/07 à 15h40 : Logiciel libre, Hackers et matériel libre avec Pierre Arlais et Olivier André
• Le 06/07 à 14h40 : Noyau Linux : architecture des drivers et device model avec Thomas Petazzoni
• Le 07/07 à 14h : Enlightenment Foundation Library avec Carsten Haitzler et Cédric Bail
• Les 06, 07 et 08/07 vers 14h : Atelier soudure et introduction aux microcontrôleurs par le fun ! (ça peut servir !) avec Hackable-devices.org

Pour tout savoir sur le programme, consultez les thèmes et l'agenda.

Voilà maintenant 2 ans que le Neo Freerunner a fait son entrée dans la cour des grands.

C'est également à cette même date que s'est formée la communauté francophone de openmoko-fr.org car c'est dans la nuit du 4 au 5 juillet 2008 qu'a été créé le forum.
J'ai été le premier surpris par son succès immédiat et j'avoue qu'encore aujourd'hui je suis étonné de voir qu'il ne se passe pas un mois sans nouveaux inscrits !

Cependant avec l'été et les vacances, il faut s'attendre à une baisse générale de l'activité du site, en espérant que tout reparte de plus belle à la rentrée.

Comme l'année dernière, j'invite tous les amateurs de logiciels libres en général et d'Openmoko en particulier à se rencontrer en juillet autour d'un apéritif ou de quelques grillades.
Ce sera l'occasion pour discuter du chemin parcouru, des projets en cours et de l'avenir.

J'ouvre le bal en proposant un barbecue dans la région de Grenoble.
Pour les intéressés, ça s'organise ici sur le forum.

Du côté de Bordeaux, certains ont déjà prévu de se retrouver aux Rencontres Mondiales du Logiciel Libre.
Pour les autres régions, n'hésitez pas à lancer des idées sur le forum et je pourrait relayer l'info sur le blog.

Voici venu l'heure du billet mensuel.

En plus, nous sommes un 4 juillet, ça ne vous rappelle rien ?

Actualités

Désolé mais il n'y a pas vraiment d'actualités ce mois-ci donc grand chose à se mettre sous le blog !
D'ailleurs si vous avez des informations à faire passer, n'hésitez pas à me le signaler. 

Je me suis donc contenté de raconter mon expérience d'un mois avec Android.
J'ai également signalé mon enthousiasme à la découverte du projet SixthSense : une interface révolutionnaire.

L'activité du forum s'est quelque peut ralentie ces derniers temps.
Mais il totalise tout de même un nombre élevé d'échanges, ce qui en fait une source d'information importante :

• 14534 messages
• 1270 discussions
• 621 inscrits

Souhaitons la bienvenue à : lgel, Le Filou, crl, synhedionn et xau.

Voici une sélection des discussions du mois.

Communauté :

• RMLL à Bordeaux. (4 messages)
• HackerSpace Lille : Soirée Communication. (2 messages)
• Braderie de Lille (1 messages)

Logiciels :

• qi-bootmenu, un bootloader graphique (16 messages)
• [RESOLU]SSH sous debian mot de passe non null (15 messages)
• Soucis avec le vibreur & la gestion des profils (10 messages)
• Qtmoko et voip avec Free (9 messages)
• [Androïd] Récupérer version Koolu (9 messages)
• [Android] version 0.2 (7 messages)
• [SHR-U] Grosses Evolution - kernel 2.26.32 (7 messages)
• QTMoko v24 est là ! (6 messages)
• [SHR-U]:Maj du (faite le) 6 juin (6 messages)
• Demande d'avis (6 messages)
• sms enlever T9 (5 messages)
• Une nouvelle distribution, neophysis (4 messages)
• OpenMoko uniquement en CLI (4 messages)
• [SHR] pymail : Notifier de mail (4 messages)
• Midori n'existe plus? (3 messages)
• [Pymail-gtk] Pymail (client mail) pour Hackable:1 et interface gtk (3 messages)
• [SHR] Lenteur de l'affichage (2 messages)
• [QtMoko] Traduction française (1 messages)
• Faire apparaitre le FR comme smartphone quand on utilise le bluetooth (1 messages)

Matériels :

• [Resolu] WOSD(??)- white screen of the dead + reparation de l'ecran (9 messages)
• GSM défectueux? (8 messages)
• Palm pré (6 messages)
• [GPS] NMEA / BT protocol RFCOMM (5 messages)
• de l'intérêt d'une debugBoard ? (2 messages)
• [Récapitulatif]Buzz Fix (1 messages)
• Buzz sur un A6-fixed? (1 messages)
• vend openmoko FR sur Bruxelles et périphérie (3 messages)

Projets :

• [rendering] Automatisation (1 messages)
• Sleepytux : Une application android pour définir des profils. (10 messages)

Divers :

• Le FR combiner avec Arduino (5 messages)
• Geek'sPhone one un concurrent du FreeRunner? (1 messages)
• [WANTED] Mokoïste Grenoblois (1 messages)

Bonne lecture !

Comme souvent, le wiki a été très calme.

En fait, il n'y a eu qu'une seule page créée : PymailGtk.
Celle-ci est très complète et parle du logiciel éponyme inspiré de pymail mais porté sous Hackable:1 avec la librairie python-gtk2.

Statistiques du site

• Graphique des visites : 

• Nombre de visites par mois : 

(Cliquez sur l'image pour l'agrandir)

• Répartition par pays : 

• Visites par jour : 

• Statistiques du forum : 

• Les statistiques du wiki : 

Bilan

Aujourd'hui nous fêtons un double anniversaire .

C'est en effet le 4 juillet 2008 que OpenMoko lançait le Neo Freerunner.
Dans la même soirée, j'installais le forum qui marquait la naissance de la communauté francophone.

Deux années se sont écoulées et la communauté est toujours présente.
C'est vous qui faites vivre le Neo Freerunner et qui défendez l'idée qu'un matériel libre est possible, même dans le domaine de la téléphonie mobile.

Je partage cette conviction et je vous remercie chaleureusement.
Pour ma part, je regrette que les changements dans ma vie professionnelle depuis décembre ne me laissent que si peu de temps pour contribuer à mon projet favori.

Mais malgré cela et malgré la baisse d'activité générale je persiste et signe !
Cela dit, quelques bonnes nouvelles de la part d'Openmoko seraient de bonne augure.
Sean, si tu nous entends ...

Through the last couple of days, I've been in extreme bug-squashing mode for the GPRS/EDGE code base in OpenBSC (mostly the OsmoSGSN program). I'm now at a point where I can reliably establish PDP contexts and access the Internet from a variety of different phones with different baseband chipsets and GPRS protocol stack implementations. All so-far-known bugs regarding fragmentation/reassembly, sequence numbering and other issues have been fixed. There definitely are plenty more, but we first need to find them.

Since it's working reliably now, it's quite fascinating what the various phones do after connecting to the GPRS network. Like Windows Mobile phones sending Netbios Name Service updates (and requests), which I think is funny considering that they are sent to a network that is typically considered to be the public Internet.

But to be fair and not anti-Windows, my Google/Android G1 also makes some https connections back to Google - and I don't know what they are for [yet].

In any case, with OpenBSC, OsmoSGSN and OpenGGSN anyone interested in doing true security (and privacy) research with mobile phones is now able to do so. Using those programs, you can run your own GPRS+EDGE network and can see first hand what your phones are doing on a cellular network, what kind of data they are sending back home. In this setup, there is no packet filtering, NAT, deep packet inspection and no intrusion detection systems between your PC and the IP stack on your phone.