I came to Barcelona with a few other Igalians this week for LinuxCon, the Embedded
Linux Conference and the KVM Forum.

We are sponsoring the event and we have a couple of presentations this year, one about QEMU, device drivers and industrial hardware (which I gave today, slides here) and the other about the Grilo multimedia framework (by Juan Suárez).

We’ll be around the whole week so you can come and talk to us anytime. You can find us at our booth on the ground floor, where you’ll also be able to see a few demos of our latest work and get some merchandising.

Based on historic review, the following seems to be the only viable option for this process.

After confirming with the election rules, and historic precedent, the case for five Maemo Community Council candidates seems to be very clear.  The case for five is a "no election" scenario, granting the candidates full Council-ship.

This being said, it brings me great pleasure to announce the new, Q4 2012 Maemo Community Council:

• Alexander Kozhevnikov / Mentalist Traceur
• Iván Gálvez Junquera / ivgalvez
• Joerg Reisenweber / joerg_rw
• Michael Demetriou / qwazix
• Niel Nielsen / nieldk

As stated many times in the past month, these five maemo.org contributors have put in timeless hours supporting our community. They are all people who our community has expressed much support for and who will do what it takes to see this community through the tumultuous months ahead of us.  In speaking for the entire previous Council, I'd like to offer a warm welcome (or welcome back) and wish them a happy and productive term!  The formal hand-off will occur at the Council meeting, Friday at 18:00 UTC on #maemo-meeting (on IRC/freenode).

Remember, the position of Community Council member is completely voluntary and unpaid. These fine people are serving you, the Maemo Community, in their free time, out of the goodness of their hearts and a passion for what Maemo is and means.

Once again, thank you all for the ongoing support. This Council only exists because of you.

Minutes for first Hildon Foundation Board meeting. VoIP meeting held on Google Hangout. Attending: - Randall Arnold / texrat - Tim Samoff / timsamoff - Ivan Galvez / ivgalvez - Robert Bauer/ SD69 - Craig Woodward (intermittent) / woody14619

Hildon Foundation, Meeting 1 - November 3, 2012

====================================

+ Note:
- Technical Issues persisted via Google Hangout: only Randy, Ivan and Tim had voice capability. Others participated via chat.

+ Public Meeting Minutes?
- Tim: Yes
- Randy: Some private; some public
- Ivan: Are they required?
- Rob: n/a
- Craig: They should be public, with exceptions of criticalinformation/NDA.

+ Bylaws, version 7
- Bylaws unanimously approved by all Board members.

+ Board Officers
- Chair: Randall Arnold
- Secretary: Robert Bauer
- Treasurer: Currently, Tim Samoff
> Proposed to ask Cosimo Kroll/zehjotkah to occupy this role.
~ Cosimo has agreed to take the position and will be appointed at the next Board meeting.)

+ Bank account?
- Find out about bank account (ask Niel Nielsen/nieldk).

+ Meeting schedule
- VoiP every two weeks?
- IRC meetings (Board Business) every two weeks & VoiP meetings(Official Board Meetings) monthly?
- Will schedule regular meetings on Google Calendar (which will also create a permanent Hangout for the Board).

+ Transitioning tasks from Council to Board. Separation of current tasks.
- Ensure Council remains communication conduit for community.
- Board organizes operational decisions.
- Board needs an official statement for Board responsibility withcommunity.
> Ask Craig Woodward about maemo.org channel(s) of Board communication.
~ After the meeting, Ivan asked X-Fade to set up the same mechanism that Council is using for communication. In the meantime, Council account can be used.

+ Funding activities:
- Nothing to report at this time.

+ Private session concerning some NDA-protected issues (recorded elsewhere).

+ Infrastructure problems:
- To be discussed via email.

+ Meeting concluded.

By Tim Samoff, Hildon Foundation Board Member.

Dear Maemo Community,

Hey Aaron. I mostly agree with your post. I don’t fully agree, however, with “We needed Android because we couldn’t do it ourselves”:

Mostly Qt (and also KDE) developers, and some GNOME developers who where still left developing for Nokia since the N900 and earlier, made the Nokia N9 Swipe phone. Technically the product is a success; look at the N9′s reviews to verify that. Marketing-wise it’s sort of a failure due to, in my humble opinion, a CEO switch at the wrong time and because he didn’t have enough time to learn how good the phone actually was. But even without much marketing, the product is being sold as we speak.

I do agree if you mean with your blog post that for example the N9 happened thanks to local leadership. The leadership that made it happen was employed at Nokia though, and not really a person in either the Qt or the GNOME camp. Rather a group of passionate leadership-taking people at Nokia.

It might have contributed that these technical leaders didn’t see how strong they could have been together during the CEO switch, at the time when Ari Jaaksi left Nokia as soon as Stephen Elop’s plans became clear. I’m not sure.

I think what we can learn from the episode is to put more trust in the person, and the leadership-taking people, who lead the next product developed the way the N9 was developed. Give those people more time onstage at open source conferences.

I’m also sick and tired of Free Software being inefficient and self-destructive due to internal schism. It’s one of the reasons why I’m not working much on Free Software nowadays. As I’m not much of a leader myself, I silently hope some local leader would change this. Maybe somebody at Digia? Jolla? If I can help, let me know.

Front Page

Open Letter from the Hildon Foundation Board

The newly elected Hildon Foundation Board have published an open letter to the community about the direction they have started to take. "At this point, the first Board meeting minutes have been published for public review. As we hope you'll see, it is nothing but the Maemo Community's best interests that we are concerned with. In fact, the entire reason for the Hildon Foundation to exist is so that the" The encouraging opening continues into a bit of the history behind the community starting with the community council and describing where the Hildon Foundation Board fits into the picture. The board maintains its roots, stating it will conduct business in "an open source manner" both in the board-specific meetings and communication with the community.

Read more (maemo.org)

In this edition (Download)...

1. Front Page
   • Open Letter from the Hildon Foundation Board
2. Community
   • UK Qt meetup in Birmingham this evening

In the back of my head I’m remembering something about how music can affect car drivers in traffic (sorry, I can’t be bothered to actually look for a reference at the moment). I’m curious if this might be true for testers as well!

So if there happen to be a project leader or similar out there that would like to try this little experiment I would be very happy to see the result from it. Try and play nice and calm music (like Enya and stuff like that) for a couple of days, then try a lot harder and faster music (any heavy metal will do I  guess). At the end of the experiment try and see if either music actually made the testers find more defects; broke the software/hardware more often or perhaps made the developers cry randomly…

I think this would be an awesome experiment!

Share/Bookmark

Cybercom has signed a partnership with Liaison technologies, a global provider of secure cloud-based integration and data management services and solutions. Cybercom will resell and deploy Liaison´s Tokenization solution, Liaison Protect, in the Nordics and Eastern Europe.

Here's something obvious (and I'm sure it has been discussed before, I just can't find the link right now), but it might be helpful if you haven't played around with SSH much yet, and your Wi-Fi Hotspot isn't working (the case for me right now). The goal is to get an internet connection over your N9/N950 from a PC (tested with Linux, expected to work with OS X and probably also works on Windows - on Windows you might need something like PuTTY).

1. Enable developer mode on your device
2. Connect your device to your computer via USB
3. Select "SDK mode" when asked for the USB connection type
4. Use the SDK connection utility, and select USB connection
5. Note the password displayed in the "Connectivity Details" screen
6. On your computer, use "ssh -D 9898 developer@192.168.2.15"
7. Accept the host key question, and enter the password from step 5
8. You should be greeted by a Busybox prompt "/home/developer $" - leave that open in the terminal window in the background
9. At this point, a SOCKS proxy server is running on port 9898, and you can use it in any applications supporting a SOCKS proxy (there are even utilities like socksify(1) (Debian package: dante-client) that make generic network applications work through a SOCKS proxy)
10. To use it in Firefox, go to Edit - Preferences - Advanced - Network - Settings..., then choose "Manual proxy configuration" and set "SOCKS Host:" to localhost and port to 9898 (be sure to disable the proxy again when you want to browse via a normal Wi-Fi/Ethernet connection)

Instead of doing steps 4 and 5, you can set up a permanent password for your "user" account on the N9, and even set up a SSH key on the N9 to avoid having to enter the password. You can make step 6 simpler by adding an entry to your ~/.ssh/config file (on your host) - see ssh_config(5) for details:

Host n9proxy
    HostName 192.168.2.15
    User developer
    DynamicForward 9898

After that, a "ssh n9proxy" (possibly followed by the developer password) is all you need to set up the proxy. This method is arguably easier (and definitely safer) than using the Wi-Fi hotspot, and instead of using up battery on your N9, it gets charged via the USB port while you are using it.

By the way: You will have to manually connect your N9 to your mobile internet connection, this won't happen automatically.

Attending:

• Tim Samoff / timsamoff
• Iván Gálvez Junquera / ivgalvez (via chat only)
• Rob Bauer / SD69 (via chat only)
• Cosimo Kroll (zehjotkah)

Appoint maemo.org administrators (or, if someone steps in):

• Possibly ask Reggie to take over admin of maemo.org.
  • How much would he charge?
  • Other NDA-restricted info discussed pertaining to transfer and administration of maemo.org infra from Nokia to the community (recorded elsewhere).

Further maemo.org infra:

• Other NDA-restricted info discussed pertaining to maemo.org infra(recorded elsewhere).

Bank account and fundraising:

• Cosimo will research banking options for the Board/community.
• Iván has received an email offering to put ads on maemo.org.
  • It could be a possible solution for TMO if Reggie wants to keep it independent of maemo.org.
• Cosimo: Opinion that the community should run on donations; so no ads.
  • Others agree: no ads on maemo.org.
• Will investigate possibility of commercial “sponsors” (preferably OSS companies).
• Other NDA-restricted info discussed pertaining to community funding (recorded elsewhere).

Foundation website/servers/hosting:

• We need administrators (volunteers).
• Still need to get domain from Niel Nielsen (nieldk).
  • This has since been resolved.
• Some discussion about who should “own” or “hold” the domain name(s) and hosting.
  • Tim will take care of gaining domain and setting up hosting/website in Foundation’s name.
  • Hildonfoundation.org site will point point to maemo.org.

Meeting concluded.

“I’ve been circumventing antivirus systems today.” His eyes glistened when my colleague Mattias told me this during the latest after-work get-together. It’s not as strange as it sounds. All our clients have antivirus systems, and they are a natural part of penetration tests.

Traditional antivirus systems collect large numbers of so-called signatures of malicious code, which they then compare with the files on your computers. This approach is called blacklisting. It worked reasonably well in the past, but is becoming increasingly difficult for several reasons.

Firstly, the number of known viruses is increasing exponentially. As soon as they are modified just slightly a new signature is needed. Secondly, there are more and more black hats hacking for a living. When they discover new security holes or develop their own code, they use the information in targeted attacks. In the old days they manufactured viruses that were dispersed on a large scale and could be captured and analysed. Now they keep the knowledge to themselves. This means there is more and more malware circulating on the black market.

Most antivirus systems nowadays look not only for signatures but also for suspicious patterns and behaviours. The result is better, but the fact remains that they are still looking for things they know about.

In summary, traditional antivirus systems can only ward off script kiddies and viruses that make use of known methods. They are important for hygiene, but cannot prevent advanced hacker attacks. Moreover, different antivirus systems are good at different things but do not always work if installed together on the same machine.

More recently, a method called whitelisting has come into focus. Instead of trying to find every malicious program, only a certain number of programs that do the right things are accepted. The downside of this technology is that it requires a finely tuned database that suits precisely your system without interfering with business operations. The advantage is the much lower chance of targeted attacks being successful.

Unfortunately there is no single antivirus program that solves the problem of malware. First you have to decide what information is worth protecting. Then, you need a well thought out strategy that includes several different types of protection: antivirus programs, firewalls, intrusion detection systems and possibly whitelisting of applications. Nor is it wrong to have several types of anti-virus software installed on different computers. Since a large proportion of corporate information is held on mobile devices, extra thought must be given to these.

But above all, we must remember that security is so much more than just antivirus software. An individual security mechanism can always be circumvented. It is the whole picture that really matters.

Share/Bookmark

People told me many times that I complain a lot (maybe even too much sometimes). But this is who I am and you have to live with it.

When I get new device I usually blog about it — like I told during recent conferences: “give me a device and I will find something to complain about, but also will usually tell something positive as well”. Sometimes those posts even got presented by other people at management meetings as an example of what is good/wrong in described products.

But so far I never got an email with ask to remove any blog post — there were comments outside of blog sometimes but never request to take my opinion down. I edited two posts — first one was before publication because I sent it for review (it was not requested by company), second time when I got some information about product in public space but device had to be announced week later at big event during one of trade shows.

What do you think? Should I write more about devices or rather not?

Related posts:

1. Tizen: first impressions
2. ARMology
3. It is 10 years of Linux on ARM for me

Hello all,

TodayLast week I finally joined the Wikimedia Foundation, with my US visa renewed and all the bureaucratic requirements in place. I work at the Platform Engineering team, reporting to Sumana Harihareswara and having other (remote) neighbors like Guillaume Paumier, Chris McMachon and Andre Klapper (of GNOME & Maemo/MeeGo fame, what a coincidence!). I feel happy. I feel honored. I’m ready to do my best contributing to the Wikimedia (with m) movement, one of the most impressive collaborative projects nowadays.

The compatibility layer for applications packed as .apk (that are running natively and use OpenGL ES) has seen its source code released yesterday. Supports Maemo 5 (Fremantle) and MeeGo 1.2 (Harmattan), which means your N900, N950 and N9 are covered. Documentation is provided in the source, and the wrapper generator scripts are also released. Looking forward to contributions and new modules from the community. Details can be found on the apkenv website.

Somehow it hurts.

I remember back in 2002 when we were debating the proposed Anglican-Methodist Covenant, I was the awkward bugger who stood up in our local District Synod and voiced the question "If this were about entering into Covenant with a denomination in which black men were forbidden to become Bishops, would we be having the debate at all?"

After a suitable pause for the very audible gasp, and time for one or two to recover from the vapours, I stepped down: point made. Two things followed in the debate. One was that in entering this covenant it was recognised that we were asking our Methodist women to make some sacrifice. The other was a loud reassurance that our brothers and sisters in the Church of England were on a journey, and we should walk with them rather than stand aloof. On that basis, our synod duly voted in the Covenant.

Today we have seen that enough of those brothers and sisters have no intention of travelling anywhere to cause the journey for all of them to come to a standstill.

A small (Methodist) part of me wants to say "Ok, can we cancel the Covenant now until they get their act together?".

But the greater, more caring part of me weeps for the pain this decision has caused and will continue to cause those wonderful women - and men - who have been called by God and who faithfully serve Him in the church every day. Those no-voters probably don't even realise that in refusing certain areas of service to women they are denigrating the service of all those faithful women, ordained and lay, by indicating that in the Official Opinion of the church they are somehow 'lesser'.

There will be a lot of pain and a fair few tears in the Church of England tonight. But tomorrow those hurt priests and their congregations will be back doing what they do best, trying to serve God in the communities in which they're set. It is all those faithful brothers and sisters that we're in Covenant with. And those brothers and sisters we sit with tonight as they come to terms with a vote that brings a long process to an end, at least for now. Maybe the subject can be raised again in a few years, but tonight we, your Covenant partners will sit down beside you, hold your hands, share your pain and wait. And we will pray with you and for you.

Somehow it hurts.

I remember back in 2002 when we were debating the proposed Anglican-Methodist Covenant, I was the awkward bugger who stood up in our local District Synod and voiced the question "If this were about entering into Covenant with a denomination in which black men were forbidden to become Bishops, would we be having the debate at all?"

After a suitable pause for the very audible gasp, and time for one or two to recover from the vapours, I stepped down: point made. Two things followed in the debate. One was that in entering this covenant it was recognised that we were asking our Methodist women to make some sacrifice. The other was a loud reassurance that our brothers and sisters in the Church of England were on a journey, and we should walk with them rather than stand aloof. On that basis, our synod duly voted in the Covenant.

Today we have seen that enough of those brothers and sisters have no intention of travelling anywhere to cause the journey for all of them to come to a standstill.

A small (Methodist) part of me wants to say "Ok, can we cancel the Covenant now until they get their act together?".

But the greater, more caring part of me weeps for the pain this decision has caused and will continue to cause those wonderful women - and men - who have been called by God and who faithfully serve Him in the church every day. Those no-voters probably don't even realise that in refusing certain areas of service to women they are denigrating the service of all those faithful women, ordained and lay, by indicating that in the Official Opinion of the church they are somehow 'lesser'.

There will be a lot of pain and a fair few tears in the Church of England tonight. But tomorrow those hurt priests and their congregations will be back doing what they do best, trying to serve God in the communities in which they're set. It is all those faithful brothers and sisters that we're in Covenant with. And those brothers and sisters we sit with tonight as they come to terms with a vote that brings a long process to an end, at least for now. Maybe the subject can be raised again in a few years, but tonight we, your Covenant partners will sit down beside you, hold your hands, share your pain and wait. And we will pray with you and for you.

This week has been a busy one for a hacker-nomad. Weekend in Paris for the JS.everywhere conference, then on Monday a talk at the Hamburg JavaScript meetup. And now I'm in Helsinki. Slush, the conference I'm attending, is the biggest start-up event in Nordic countries. But even at that, it seems the Jolla announcements of today have been able to hijack most of the buzz around the event.

I hosted a workshop regarding web security tonight where the main objective was to actually hack into something (a demo app). A part from actually letting the group investigate/test the site for XSS vulnerabilities, bad implementations and overall horrible architecture the idea was to show how easy a small “flaw” can become a major problem. Very few people will be worried by seeing some demo page just showing some “alert window” displaying the word test or something. I think/hope my approach by actually showing how all these “small” flaws together actually made it so the “evil hacker” could perform a session hijacking and get complete access to the demo app highlighted that even the smallest flaw could end up being something very serious.  I’m pretty sure quite a few of these flaws would only make the usual web developer (or tester for that matter) shrug their shoulders and move on saying, “nothing serious…”, this while the “evil hacker” stand on the other side of the fence saying “just smile and wave boys, just smile and wave” (bonus points if you know the movie reference! ).

The group did very well and even though most of them had no previous experience of these things the group together identified all the flaws needed to actually do the session hijacking. Well done!

Share/Bookmark

Half year ago I got Tizen development platform device. Played a bit with it and then put in a drawer due to other things to do.

Today I looked again at Tizen. Nothing changed. Git repositories still scream “****@#$!$ *** *** you developers!” due to lack of any commits other than code drop bombs.

So if someone (from Europe) wants this device — be first to comment. Sending with DHL and you pay for posting.

Related posts:

1. Tizen: first impressions
2. Complaining
3. ARMology

I’m a bit puzzled. I think anyone that works in the IT business today know how vital the testing is, and that it takes all shapes and forms. You have everything from actually poking the 1’s and 0’s with an oversized stick until it breaks to from afar analyzing the “if’s and the maybe’s”. My point is that testing is a whole lot more than just “that stuff that happens just before the code is delivered”.  With that in mind I’m a bit puzzled on how many fresh out school workers, and still in school for that matter, I meet that has almost no clue that testing even exists. Usually the only experience from testing they have is that they made some attempt on unit testing in a java school project or similar. I must say I have kind of the same experience from school, apart from writing very few and extremely simple unit tests I can’t remember ever hearing anything about it.

I hope I’m wrong and the schools actually got kickass courses within all areas of testing, someone please prove me wrong!

Share/Bookmark

Cybercom is adapting its operations in Sweden, Singapore and Finland to improve the efficiency. Actions include cuts of the group overhead costs and reductions in the number of employees. The measures are expected to provide annual cost savings of approximately SEK 45 million.

Front Page

Jolla reveal strategy, UI and Qt Creator-based SDK at Slush 2012

Jolla is once again foremost in the minds of many mobile OS enthusiasts and open-source aficionados with more information being revealed regarding their strategy and future. The launch of their official website and a slick video partway between a teaser and a product video give a definite sense of progress and should inspire confidence in everyone holding their breath for a product launch.

Meeting held on FreeNode, channel #maemo-meeting (logs)

Attending: DocScrutinizer05, qwazix, MentalistTraceur.
Absent: NielDK, ivgalvez

Summary of topics (ordered by discussion):
- IRC Account for ivgalvez
- Infrastructure
- CC Devices Situation
- Misc topics

Notes

• Before the meeting, ivgalvez was able to give us an update from the Board, saying that next week the board has a conference with both Nemein and Nokia, and that hopefully this helps unblock the current situation.

Topic 1 (IRC Account Requirement for Councilors):

• DocScrutinizer brought up that community councilors are supposed to have registered IRC accounts on FreeNode IRC, and ivgalvez currently doesn't have one.
• Significant reasons for this mentioned were:

1. An unregistered username can be used by anyone, and impersonating councilors has significant potential for community disruption.
2. An unregistered username cannot receive special permissions for IRC channels, such as being able to change the topic of the council meeting channel.
3. Unregistered users can't receive cloaks.
4. Thus, DocScrutinizer cannot proceed with the cloak/permissions changes request until ivgalvez has registered his IRC nick.

Topic 2 (Infrastructure):

• Wiki (still) has edit error.The error comes from /usr/share/mediawiki/includes/EditPage.php
• Thus, Council decided to request that X-Fade publishes that, and perhaps other *.php files, or the entire /usr/share/mediawiki/includes* subdirectory, excluding any secret/sensitive files, to maemo.org, so that the community could take a look at them and perhaps someone could figure out where the error is coming from.

Topic 3 (CC Devices Situation):

(Note: DocScrutinizer did not actively participate in this topic)

• qwazix sent e-mail to the contact that sent the DHL tracking information for the CC devices, to ask about the two CC devices that have not yet been delivered. He has not received a response yet.
• Recipient of the slightly malfunctioning N950 has sent e-mail to the same person, but has not followed up since then.
• There is another contact that handled the previous wave(s) of device giveaways, it was decided to try them next, after a full week of no reply has elapsed.

Topic 4 (Misc topics):

Jolla Relations:

• qwazix noted he has introduced himself to the Jolla community relationship chief, as a Council Member.

IRC Cloaks:

• DocScrutinizer will just make a blanket request to set all current IRC "maemo/community/council*" cloaks to "maemo/community/contributor", before giving the new councilors council cloaks - to make sure there's no straggler "council" cloaks left.
• Anyone wishing to keep a "maemo/community/council" cloak for some reason even though they are not a current council member, may contact the council explaining their reasons, to have their case considered.

Action Items:

• qwazix will send ivgalvez an e-mail to request that he register his FreeNode IRC nick.
• DocScrutinizer will send the IRC cloak/permission change requests to X-Fade when ivgalvez does the aforementioned.
• qwazix will send X-Fade a request to publish the relevant wiki pages as per above.
• qwazix will wait until Monday, then e-mail the fallback contact for the CC devices.

Working with open hardware

Some weeks ago at LinuxCon EU in Barcelona I talked about how to use QEMU to improve the reliability of device drivers.

Firefox for Mobile Firefox for Android: Running on Android x86 - http://starkravingfinkle.org/blog... November 28, 2012 from Mark Finkle's Weblog » Mozilla - Comment - Like

Continuous Integration is such a great idea: it works as a trainee that constantly downloads/builds/tests/deploys you application and notifies you whether something goes wrong or nice. I really do believe that (of course, besides several other advantages) it improves the project overall quality and also helps you to keep the application ready to be reviewed by a stakeholder.

If you are still skeptical about it, please take a look that this marvelous post here [Martin Fowler] .

Let´s discuss how you can set up a environment for a more complex project. So, unfortunately, this is tutorial for beginners (for basic/how-to-install-and-run instructions, check it on internet).

Introduction

The system consists of one server located in a external environment (for example, AWS services) and several mobile clients (iOS, Android and QT clients). Basically, the mobile applications fetch content/data from the server.

We need to constantly build/deploy the server and build all mobile clients. One very interesting point in this scenario is the amount of platforms: iOS (to build iOS client), Linux (to build Android/QT client - I´d rather use Linux for Android projects) and Windows (to build the server).

Besides svn checking-out + building + testing + deployment, we will also use QA solutions, such as Sonar and some static analysis tools for different platforms.

We will use Jenkins as CI server.

Proposed design


As I said, the system consists of several components: mobile clients (iOS, Qt and Android) and also servers. In this case, I´d rather use master-slave approach. You can create one slave for each mobile platform and also another one for for servers. To the given example, the solution is defined as it follows:


You might ask me why this is too complicated! But believe on me. If you have complex systems to build, this approach works a lot better: it´s easier to organize and to maintain, and each component on its own environment. In my next post, I describe how we set up all of this :-)

Outotec and Cybercom have signed an agreement on the delivery of a new IT-solution to support Outotec's Virtual Experience Training service. The project has started and will be delivered in spring 2013.

Well, a short break on continuous integration posts!

As a consequence of the rights issue resolved by the board of directors on 29 August 2012 and approved by the extra general meeting on 1 October 2012, the number of shares and votes in Cybercom has increased by 144,351,596.