ORINDA, CA – February 3, 2016 – The GNOME Foundation is pleased to announce that Endless, creator of the Endless computer and operating system, has joined the GNOME Foundation advisory board. The Advisory Board is a body of stakeholder organizations and companies who support the GNOME Project by providing funding and expert consultation. The board includes Google, Intel, the Linux Foundation, and the Free Software Foundation, among others.
“We are very excited to join the GNOME Foundation advisory board,” said, Jonathan Blandford, VP Engineering at Endless and GNOME advisory board member. “The goals of the GNOME Foundation are perfectly aligned with the goals of Endless; to create a technology platform for the general public that is designed to be elegant, efficient, and easy to use.”
The Endless computer is the world’s first fully functioning desktop PC designed to bring the next four billion people into the information age.
“Endless is using GNOME in innovative ways to help close the digital divide. We’re excited to have them share their vision on the GNOME advisory board.” said Shaun McCance, President of the GNOME Foundation Board of Directors.
The nonprofit GNOME Foundation is an independent organization committed to supporting the advancement of the GNOME Project and software freedom. It provides financial, organizational and legal support to the GNOME Project and helps determine its vision and roadmap. GNOME software is used by millions of people around the world.
More information about GNOME and the GNOME Foundation can be found at www.gnome.org
WordPress 4.4.2 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. WordPress versions 4.4.1 and earlier are affected by two security issues: a possible XSS for certain local URIs, reported by Ronni Skansing; and an open redirection attack, reported by Shailesh Suthar. Thank you […]
Google Code In is our annual project to give tasks to school pupils to contribute to KDE projects. One task this year is to write a Dot article and top Code In student Stanford L has interviewed WikiToLearn contributor and Sysadmin Luca Toma.
Please tell us a little about yourself
What do you do for a living?
What do you do for KDE?
At this time my contribution in KDE is WikiToLearn, my role is the system administrator. I take care of the maintenance of the infrastructure and server project.
How did you get into computer programming?
Do you have any advice for people who would like to pursue computer programming as a major?
Who is your role model, and why?
What are some ways you motivate yourself?
Do you have a vision, like where do you want KDE in general to be in 5 years and sysadmin in particular?
One of the most important lessons of 2015 for the Engineering Team here at the Drupal Association is that we need better ways to engage with you, the community. We realized we need better tools and ways to communicate with you about our current priorities, how you can influence those priorities, and how you can help make Drupal.org and the Drupal project better than ever.
All of the work we do stems from the mission of the Drupal Association. It’s our duty and responsibility to unite a global open source community to build and promote Drupal. As the home of that community, and the codebase, Drupal.org is perhaps the most critical piece of that mission, and at the most basic level all of the initiatives we prioritize must support that goal.
As part of reviewing our work in 2015, and in the interests of being transparent with the Drupal Community, we revamped the Drupal.org Roadmap. As you can see, we chose to focus on the few, most important initiatives that we have the capacity to execute on in the near term. We’re also including upcoming initiatives that we will move into as the active work is completed, but not as many as we had previously displayed. An important lesson of the past year is that we have to be Agile on the macro scale as well as on the micro. The needs of the community can change rapidly and we need to be able to respond.
These are the initiatives the Drupal Association technology staff is focused on now.
These are the initiatives the Drupal Association staff will work on or support once the Current initiatives are completed. The order of these initiatives may change.
We’ve also added some new iconography to indicate where some of these initiatives come from.
Initiatives with the tools ( ) icon represent essential support and maintenance work. This can mean paying down technical debt in the Drupal.org codebase, performing server maintenance, or implementing cost saving measures to help fund the rest of our mission driven work.
Initiatives with the community ( ) icon represent initiatives that were directly proposed by members of the community and/or are being supported by volunteer work from the community.
Don’t all the initiatives come from the community?
Yes, all of our priorities come from the needs of the community – but the community is a loose collective of many different groups of people with many different needs and priorities.
The needs of Drupal newcomers are vastly different from those of the Drupal Core Maintainers. The needs of our documentation editors are different from the needs of those providing support on the forums. And all of these needs must cohere with a larger product and design vision for Drupal.org to make this home of the community a cohesive, efficient, and beautiful place to be.
The Drupal Association Engineering Team can be thought of as the maintainers for Drupal.org and the sub-sites. It’s our duty to synthesize these diverse needs and to prioritize the major initiatives that will have the highest impact for the community. It’s also our job to make the architectural decisions for Drupal.org to ensure that every aspect of the site is functional/useable, consistent, and maintainable.
Most of our priorities, therefore, we set ourselves by bringing all of these factors together and doing the best we can to have the biggest impact, not just on the most vocal parts of the community, but also on those parts that are sometimes siloed or overlooked.
All that said, the community is absolutely a vital part of creating our initiatives. The maintainers for any other project on Drupal.org do not act alone – they accept feedback and contributions from other contributors, while at the same time making key architectural decisions, reviewing patches, and ultimately deploying that work in the form of new releases. We do the same with our initiatives.
Community Volunteers and Community Initiatives
There are two ways that members of the community can have a direct influence on the Roadmap for Drupal.org. These methods have existed informally in the past, but in 2016 we’d like to beta test some new ideas to make these processes more formal, consistent, and transparent.
The first way is to volunteer your expertise to help with one of the existing initiatives we already have prioritized, or even to offer your expertise without a particular contribution in mind. There is a strong record of community volunteers helping to improve Drupal.org, just a few examples from the last year include: u/mlhess and u/nnewton helping with infrastructure; to u/michelle helping to clean up spam; to u/dddave and others in the webmasters queue; or u/mshmsh5000 who helped with Drupal Jobs feature development.
If you have expertise (and not just in code!) and are ready for guidance from the Drupal Association engineering team as to how you can help, you can offer your assistance as a volunteer.
I should also note – we strongly encourage most volunteers to first consider giving back to the Drupal project itself, but we are certainly happy for help with Drupal.org
The second way to influence the Drupal.org roadmap is to develop a community initiative. If you (and perhaps a small team of others in the community) have some expertise in a particular area, and have a particular initiative in mind that you would like to work on, you can propose a community initiative.
Community initiatives come in all shapes in sizes: from documentation audits with the help of u/dead_arm; to adding two factor authentication to Drupal.org with u/coltrane; to a much larger task like building and deploying DrupalCI with the help of u/jthorson, u/nickscuch, u/ricardoamaro, u/bastianwidmer and several others. Some initiatives affect a subset of the community, project maintainers, for example, whereas others may affect almost every user.
Why this new process?
The hard lesson we’ve learned over the course of the past year is that we need to be involved early. Even in cases where the community volunteers driving an initiative forward are experts in their area – if Association staff are not involved early in the architectural and planning decisions then what should be a positive, collaborative effort is often slowed down by architectural refactoring and design decision backtracks. That is not fun for anybody, and our immense respect for our community collaborators requires that we set them up for success by getting involved early.
As such, our new community initiatives process has several steps:
This process is time intensive – and so in general we expect to be able to run only one or maybe two community initiatives at a time, in parallel with our other work. We realize this may be frustrating, but the last year has shown that our most successful initiatives required this close coordination.
This process is new, and will evolve
Finding a good process for working closely with such a diverse and passionate community is not easy—and we aren’t assuming that this new process will be perfect. We’re going to trial this new community initiative process in 2016 with the goal of increasing the transparency of how we prioritize our work, and how the community can help us build a better Drupal.org. We are committed to making this process better.
We are aware that there have been references online claiming that the GNOME Foundation was bankrupted in 2013 along with accusations about who was responsible.
To clarify the matter, the Foundation was never bankrupt. Quite a while ago, there was a temporary cash flow issue which is now completely resolved. Funds that were committed by sponsors and earmarked for the Outreach Program for Women (OPW) were delayed in payment. GNOME Foundation’s board temporarily froze expenditures while it collected the funds and revamped its financial procedures to adjust for the additional cash flow going forward. Every cent of the funds was ultimately received. Additionally, GNOME collected administrative fees which covered the program’s expenses.
Karen Sandler, our former Executive Director, made certain there were firm financial commitments from OPW sponsors prior to authorizing outgoing payments and she further ensured that all funds were ultimately recouped. While we were disappointed when Karen chose to leave the Foundation for a new position at the Software Freedom Conservancy, she has the full support of the GNOME community who elected her onto the Board of Directors in 2014. We are grateful for her continued involvement with Foundation activities on a voluntary basis after her term on the Board, as well as being a Free Software advocate and pro-bono lawyer for us and other projects.
While OPW has transferred to another home which is more suited to the program’s size and breadth, we remain an active partner of the program and are proud to support it.
It’s a great time to be part of the Drupal Association. We’ve done some amazing work in the last few years, and we’re in a great position to work with the community to continue to improve and grow fully into our mission. As a Drupal Association At-Large Director, you’d be in the center of the action. The At-large Director position is specifically designed to ensure community representation on the Drupal Association board and we strongly encourage anyone with an interest to nominate themselves today.
The Board of Directors of the Drupal Association are responsible for financial oversight and setting the strategic direction of the Drupal Association. New board members will contribute to the strategic direction of the Drupal Association. Board members are advised of, but not responsible for matters related to the day to day operations of the Drupal Association, including program execution, staffing, etc. You can learn more about what’s expected of a board member in this post and presentation.
Directors are expected to contribute around five hours per month and attend two in-person meetings per year (financial assistance is available if required). All board members agree to meet the minimum requirements documented in the board member agreement.
Today we are opening the self-nomination form that allows you to throw your hat in the ring. We’re looking to elect one candidate this year to serve a two-year term.
How to Nominate Yourself
To nominate yourself, you should be prepared to answer a few questions:
We’ve also made a few changes to the process based on community feedback from the 2015 election:
We will also need to know that you are available for the next step in the process, meet the candidate sessions. We are hosting 3 sessions:
Meet the Candidate Web Conferences:
The nomination form will be open February 1, 2016 through February 20, 2016 at midnight UTC. For a thorough review of the process, please see the elections home page.
If you have any questions, please contact Holly Ross, Drupal Association Executive Director. For the sake of keeping conversational threads in one place, the comments on this news item have been closed. Please comment on the original post on the Drupal Association website.
Flickr photo: Clyde Robinson
Front page news:
At FOSDEM this weekend KDE is announcing our newest project, KDE neon. Neon will provide a way to get the latest KDE software on the day its released.
Nomad’s Elegy is the tip of the action-packed February iceberg!
Walmart on Tuesday announced that it has posted the code for its OneOps cloud application life cycle management platform on GitHub. The company developed OneOps for building and launching cloud applications across frequently changing storage environments. It lets e-commerce vendors deploy apps on platforms from Microsoft, Rackspace and CenturyLink to OpenStack private or hybrid environments.
UPDATED TO CLARIFY HOW TO MANAGE PUSH NOTIFICATIONS Firefox for Windows, Mac and Linux now lets you choose to receive push notifications from websites if you give them permission. This is similar to Web notifications, except now you can receive … Continue reading
= Minutes for Tuesday, January 12th 2016, 20:00 UTC =
Next meeting date Tuesday, 19 January, 20:00 UTC
== Attending ==
* Jeff F.T.
== Regrets …
= Minutes for Tuesday, January 5th 2016, 20:00 UTC =
Next meeting date Tuesday, 12 January, 20:00 UTC
== Attending ==
* Jeff F.T.
= Minutes for Tuesday, December 22nd, 2015, 20:00 UTC =
Next meeting date Tuesday, 5 January, 20:00 UTC
== Attending ==
* Allan Day
== Regrets ==
* Shaun M…
Security researchers at Dr.Web on Tuesday revealed details of the Trojan Linux.Ekoms.1, which takes screen shots and records audio to acquire sensitive and personal information, mostly from Linux servers. Malware for Linux is becoming more diverse and includes spyware programs, ransomware and Trojans designed to carry out distributed denial-of-service attacks, according to Dr.Web.
GNOME 3.19.4 is out. This is a development snapshot, so use it with caution.
To compile GNOME 3.19.4, you can use the jhbuild  modulesets 
You can also test the latest code…
Tens of millions of Linux PCs and servers, as well as 66 percent of all Android mobile devices, are vulnerable to a zero-day flaw that could allow users with lower-level privileges to gain root access, according to Perception Point, which announced its discovery last week. The local privilege escalation vulnerability, which affects Linux Kernel v3.8 and higher, has existed since 2012, the firm said.
The combination of Google’s Summer of Code program and students working on numerous KDE projects during it has served as a long and successful tradition for KDE. KDE, being a big organization with a large community associated with it and hosting many projects of different facets provides a lot of opportunities for students to participate in this program and to contribute to an open-source project that they are interested in.
Hence it is no surprise that this year also many students decided to be a part of the world of KDE.
Be prepared for a long, detailed post about many interesting projects and the great results achieved during the season of GSoC ’15.
1. Porting activities
Many KDE projects are still in the process of porting the code to the new frameworks Qt5/QtQuick and KDE Frameworks 5 (KF5) – the next generation of KDE libraries, modularized and optimized for easy integration in other applications. This year several students helped to make this transition smoother and complete.
Aroonav Mishra ported a considerable portion of Amarok to Qt5/KF5 and the porting of the media player is in continuation. R. Harish did this for Kopete.
GCompris consists of several activities, wherein each activity is aimed to teach children a different educational lesson. This year Sagar Chand Agarwal and Siddhesh Suthar helped port a couple of GCompris’ activities to QtQuick. Almost all the work has been integrated to the master branch and will be available in the next release.
The educational entertainment software GCompris welcomes any form of help to finish this move.
Mohamed Anwer did his project on digiKam. In digiKam, the communication with the database was done in KIO-slaves, running in separate process. To increase the portability of the application and to reduce the serialization of data between different processes, the decision was made to change the architecture and to move it to Qt5’s threads. The new thread-based implementation done during this summer resulted in a much better performance. Also, in numerous other segments of the source code a wrapper for all KIO-related stuff was provided. The implementation behind this wrapper, which optionally doesn’t use KIO anymore, now allows compilation of digiKam as a pure Qt-application without any dependency on KIO. For more information,visit: https://mohamedanwer.wordpress.com/tag/gsoc15/
Vyacheslav Matyushin ported KSystemLog,a utility showing different system protocols to KF5. While porting the code, he also fixed many bugs and memory leaks. In addition to that, many new features were added like the support for local and remote journald, filtering of the log entries by priority, improved configuration dialog and more.
Main window showing log entires colored according to their priority. By default, all priorities are displayed. User can select priorities to be displayed
Journald mode configuration widget allows to add remote journals
A porting project of a different kind was taken up by Gábor Péterffy who ported Marble to Android. Marble Maps is available now in Google Play and provides navigation and routing functionality using OpenStreetMap’s content. Distance measurements, interactive route planning are available in the first version of Marble on Android.
KDevelop got a new “checker framework” contributed by Laszlo Kis-Adam who you might also know as dfighter. The idea behind this project was to provide a general framework for different static code analysis tools and profilers that can be used in KDevelop. This framework aims to unify and simplify the code infrastructure and to provide a consistent and user-friendly GUI for using such tools in KDevelop. Some existing plugins for cppcheck, Valgrind and Krazy were ported to this framework. The support for code analysers clang-check and pylint was added. The final report contains a lot of detailed information on this as well as a video demo of this amazingly useful functionality.
During GSoC2014 clang was integrated into KDevelop in order to use it for source code indexing, syntax checking and highligting instead of KDevelop’s own complex implementations for these tasks. Despite the ginormous progress attained last year, there was and is still a lot to do in the area of kdev-clang plugin for KDevelop – bug fixing, adding features, stabilizing the code. This year Sergey Kalinichev worked on the project “Further Clang integration in KDevelop” and extended the feature-set of this plugin with regard to code parsing, syntax highligting, code completion and refactoring. See his final report with couple of examples on this https://sklin0.wordpress.com/2015/08/23/gsoc-2015-final-status-report/.
This plugin is a must try for all KDevelop users!
Gurjot Singh worked on extending the animation capabilities of Kdenlive to allow smoother animations as opposed to the traditional keyframes technology. Before this, Kdenlive had support for only linear interpolation of keyframes for few effects and transitions. With the support for animation properties in the open-source multimedia framework MLT, which is used by Kdenlive, and with the integration work done during this GSoC by Gurjot, almost any entity can be now be animated in Kdenlive. Gurjot added configuration widgets for different interpolation types used for animations – which can be discrete, linear, smooth spline or a mix of them. Read more here: https://kdenlive.org/node/9443
Krita got a new tangent normal brush engine. Read more on Wolthera van Hövell tot Westerflier‘s blog http://wolthera.info/?p=770 who was the GSoC student working on Krita. Wolthera also addressed Krita’s widget for picking a colourspace (http://wolthera.info/?p=783).
Veaceslav Munteanu continues to contribute to digiKam for the third GSoC-program in row. This year, he implemented Advanced Metadata Hub – a new component that gives the user more control over the metadata management in digiKam. With this component it is possible now to define in addition to digiKam’s default namespaces new user-specific namespaces. It is also possible to edit new namespaces, disable them temporarily and to change their order which influences the search results in digiKam. Furthermore, lazy metadata synchronization was introduced to digiKam. When changing the metadata (applying a tag, rating or comment to an image), the synchronization process could slow-down the system for bigger image collections on slower (or remote) hard-disks. With the new lazy method the synchronization can be optionally postponed to a later point and the user doesn’t experience any immediate slow-down on metadata changes.
KStars, the outstanding open-source astronomy software, is now able to display artistic drawings for all modern constellations (https://en.wikipedia.org/wiki/88_modern_constellations_by_area) – thanks to the work done by M.S. Adityan during this summer. One of the main parts of the project was to understand how to map the image onto the sky map. The screenshot below shows art images for all 88 modern constellations that can be optionally switched on and off.
Daniel Leu contributed a job scheduler to KStars that will help automate astrophotography sessions. A job is specified as per the information provided by the user such as the object under observation, altitude, angular distance to the moon and the execution starting and finishing times and the job triggered by the scheduler communicates with the teleskop via the Ekos interface (http://api.kde.org/4.x-api/kdeedu-apidocs/kstars/html/namespaceEkos.html) and performes a slewing of the teleskop, loading of the sequence and its execution. To simplify the selection of the object to be observed, the user can now provide a FITS image and the object coordinates are determined out of the information stored in the FITS file.
David Kolozsvari joined the Marble team this summer and implemented a couple of nice features. He improved rendering of labels (street names, building names etc.) that are now drawn along the curved street paths. Before this, the labels were just shown “somewhere” on the map. As a result of his work:
Besides this, some smaller improvements and bug fixes were made by him. He has started working on improving Marble’s Print support as an extension to his contribution to Marble during GSoC. Check out his blog for demos and more (http://koldavidgsoc.blogspot.de/2015/08/gsoc-2015-summer-with-marble.html).
The second Marble-related GSoC-project was about the handling of OpenStreetMap (OSM) files. Marius Stanciu added support for opening OSM-files, viewing, editing and exporting them. The main part of the project was to provide an OSM editor for Marble. Plenty of features can be implemented in such an editor and Marius implemented it for tags and relations. Tags allow annotation of the placemarks to provide information on them beyond the location coordinates. With the help of relations, logical relationships between different points on the map can also be modeled. Take a look at Marius’ blogs for more screenshots and examples.http://mariusoc.blogspot.de/2015/08/wrapping-things-up.html
LabPlot, the data plotting and analysis tool for KDE had 3 students this year.
Minh Ngo added visualization of 3D-data to LabPlot by utilizing the very powerful library VTK. Different data source sources are supported – external files with 3D-data, LabPlot’s spreadsheets with column-based organisation of data and LabPlot’s matrices with matrix-like data structure. The data can be visualized as points in 3D-space, curves and surfaces. A lot of options for the 3D-plots are availble and can be adjusted by the user in a user-friendly GUI. Furthermore, several zooming functions were implemented that allow a comfortable navigation through the data. Because of the huge complexity of this topic, not everything could be implemented in such a short period of time. Minh is eager to contribute further to the projects and continues working on 3D-part of LabPlot with the aim to push LabPlot’s 3D-functionality to much higher level.
Ankit Wagarde added a very useful tool to LabPlot that allows to extract data from images – the Datapicker. After import of an image and setting the reference points, the user start to select the data points on the image that get automatically converted into numbers. Those numbers can be used in your own plots where you can e.g. combine your own results with results of another work where the imported image was taken from. Different scalings are supported as well as data point with error bars. Arbitrary number of curves on the plot from the imported image is supported whereas different symbol styles can be used to differentiate the appearance of the curves
Currently, LabPlot is lacking any scripting functionality and has a very limited set of features to generate new data. On the other hand, Cantor – another KDE-education software – unifies the usage of different open-source computer algebra systems (CAS) like Maxima, Octave, etc. in a single program. Garvit Khatri integrated Cantor into LabPlot. This allows now to perform calculations, to produce and to analyze data with the CAS of your choice, to plot the generated data and to modify the appearance of the plot directly in LabPlot. The user benefits now from the very powerful CAS languages and from the numerous editing features for plots in LabPlot. The screenshot below shows a simple calculation done in python3 with scipy/numpy and the visualization of the calculated data in LabPlot’s manner.
All in all – a very nice example for how two open-source projects can collaborate and bundle the man-power and the available features two produce software of much greater value.
KDE’s universal document viewer Okular was extended by Saheb Preet Singh to support PDF tags, layers and linearized documents. PDF tags allow to add additional description to different structures in a PDF document. Information can be stored on different layers of a PDF file – a feature allowing to make some content visible or invisible in the document. In Okular, tags and layers are shown in a tree-like view and can be searched and filtered for. The third new feature in Okular, the support for linearized PDF documents, make viewing over the internet faster – the document is streamed over the network and the user can start to read the document without the need to wait until the complete file is downloaded.
balooctl, the command line tool to control Baloo, KDE’s indexing and search framework, got a lot of useful features allowing to get a better overview of the current state of Baloo. The main part of the project taken by Pinak Ahuja was the Baloo Monitor – a GUI tool showing Baloo’s current state, file being indexed, total progress and estimated remaining time
and a button to suspend/resume indexing. On the way to these results, Baloo’s architecture needed to be partially redesigned and re-factored to make the interaction of this tool with Baloo’s back-end possible.
This work went far beyond the original proposal and was done in close collaboration and with the help of the project mentor. The monitor has been added as a KCM to KInfoCenter.
Aleksandr Mezin improved the KDE System Settings by adding a new configuration module for pointing devices. This module unifies now the functionality that was previously spread between Mouse and Touchpad KCMs.
With the help of KDE’s visual designers Aleksandr was able to create a nice looking UI where the pointing devices can be configured at the same place. Currently, all properties of libinput driver can be configured in this new module for X11 as well as for Wayland (with patched version of KWin), whereas a better and more complete support for evdev and synaptics drivers is to be expected in the near feature.
Ranveer Aggarwal worked on the implementation of an interface for installing 3rd party plugins for different KDE applications like additional codecs for k3b, KIPI-plugins for Gwenview, etc.
3rd party plugins can be fetched from the system packages manager, the installation is handled with the help of PackageKit that unifies the handling of different package management systems.
Ranveer’s final report exemplifies the usage of this new interface for couple of KDE applications:
KDE Connect https://albertvaka.wordpress.com/ is a very useful application for KDE and smartphone users that allows to control your KDE desktop with the smartphone, to receive the phone notifications on your computer or to interchange data between different devices. This year Vineet Garg improved the secure communication over the network and added the support for TLSv1.2 to KDE Connect. By the way, the first version of KDE Connect was written during GSoC2013.
The KDE infrastructure got a new very nice service – KDE Reportshttps://reports.kde.org/. In this web app, contributed by Ahmed AbouElhamayed, graphical reports for KDE related statistics are shown. Charts for the current number of bug reports, total average time taken to resolve a bug, number of commits, review requests, social media activities and for many many other things allow you to get better insights into the ongoing KDE activities.
Check out recent Ahmed’s blogs for a number of useful examples
Besides the porting activities mentioned above, Kopete got help from two more students this year. Nikolaos Chatzidakis worked (and is still working on it even GSoC is already finished, on a GnuPGP-plugin for Kopete to allow secure encrypting, signing, decrypting and verifying of messages via GnuPGP. Joseph W Joshua contributed to a new history plugin for Kopete based on a SQL-database. The idea behind this plugin is to store the messages in a database and to provide an interface for quick and advanced searching in the history.
For many students participated in this year’s GSoC, the contribution to the open-source community and especially to KDE didn’t end with the final reports written in August. Many students are still in touch with their mentors, continue to work on their projects or are even looking for new tasks. All in all, a great GSoC season for KDE with remarkable achievements. We’re looking forward for GSoC2016!
Qualys on Thursday reported a flaw in the OpenSSH client that could let a hacker steal the client’s private crypto keys. The bug is the result of an undocumented feature called “roaming” that exists in version 5.4 and above. It’s one of two vulnerabilities that a malicious SSH server or a trusted but compromised server can exploit, Qualys said. The other is a heap-based buffer overflow.
The Linux Foundation this week announced an expansion of the Dronecode project with investments from new members and the creation of three technical working groups. The foundation launched the open source project in 2014 in an effort to create a unified platform for commercial drone technology. Twenty-seven companies have joined Dronecode since, bringing membership to 51, officials said.