Welcome to Planet openSUSE

This is a feed aggregator that collects what openSUSE contributors are writing in their respective blogs.

To have your blog added to this aggregator, please read the instructions.

21 July, 2014


Can you afford not to do continuous deployment?

Continuous deployment is the practice of regularly (more than daily) deploying updated software to production.

Arguments in favour continuous deployment often focus on how it enables us to continually, regularly, and rapidly deliver value to the business, allowing us to move fast. It’s also often discussed how it reduces release-risk by making deployments an everyday event – with smaller, less risky changes, which are fully automated.

I want to consider another reason

Unforeseen Production Issues

It can be tempting to reduce the frequency of deployments in response to risk. If a deployment with a bug can result in losing a significant amount of money or catastrophic reputation damage, it’s tempting to shy away from the risk and do it less often. Why not plan to release once a month instead of every day? Then we’re only taking the risk monthly.

Let’s leave aside the many reasons why doing things less often is unlikely to reduce the risk.

There will always be things that can break your system in production that are outside your control, and are unlikely to be caught by your pre-deployment testing. If you hit one of these issues then you will need to perform a deployment to fix the issue.

Time-sensitive Bugs

How often do we run into bugs in software due to failing to anticipate some detail of time and dates. We hear stories of systems breaking on 29/02 nearly every leap year. Have you anticipated backwards time corrections from NTP? Are you sure you handle leap-seconds? What about every framework and third party service you are using?

Yes, most of these can be tested for in advance with sufficiently rigorous testing, but we always miss test cases.

Time means that we cannot be sure that software that worked when it was deployed will continue to work.

Capacity Problems

If you production system is overloaded due to unforeseen bottlenecks you may need to fix them and re-deploy. Even if you do capacity planning you may find the software needs to scale in ways that you did not anticipate when you wrote your capacity tests.

When you find an unexpected bottleneck in a production system, you’re going to need to make a change and deploy. How quickly depends on how much early warning your monitoring software gave you.

Third Party dependencies

That service that you depend on goes down for an extended period of time, suddenly you need to change your system to not rely on it.


Do you handle all the infrastructure related issues that can go wrong? What happens if DNS is intermittently returning incorrect results? What if there’s a routing problem between two services in your system?

Third Party Influence

“Noisy Neighbours” in virtualised or shared hosting. Third party JavaScript in your page overwriting your variables or event listeners. In most environments, you can be affected by others over whom you have no control.


Monitor Monitor Monitor


20 July, 2014


Here is updated openSUSE-Edu-li-f-e-gnome-classic iso, this update include GNOME 3.12, official openSUSE updates till date, and it brings back Sugar.

Download ISO | MD5 | Alternate download and mirrors

Previous release announcement.

18 July, 2014

Alexander Naumov: Perl party :)

13:19 UTCmember


    ''=~(        '(?{'        .('`'        |'%')        .('['        ^'-')
    .('`'        |'!')        .('`'        |',')        .'"'.        '\\$'
    .'=='        .('['        ^'+')        .('`'        |'/')        .('['
    ^'+')        .'||'        .(';'        &'=')        .(';'        &'=')
    .';-'        .'-'.        '\\$'        .'=;'        .('['        ^'(')
    .('['        ^'.')        .('`'        |'"')        .('!'        ^'+')
   .'_\\{'      .'(\\$'      .';=('.      '\\$=|'      ."\|".(      '`'^'.'
  ).(('`')|    '/').').'    .'\\"'.+(    '{'^'[').    ('`'|'"')    .('`'|'/'
 ).('['^'/')  .('['^'/').  ('`'|',').(  '`'|('%')).  '\\".\\"'.(  '['^('(')).
 '\\"'.('['^  '#').'!!--'  .'\\$=.\\"'  .('{'^'[').  ('`'|'/').(  '`'|"\&").(
 '{'^"\[").(  '`'|"\"").(  '`'|"\%").(  '`'|"\%").(  '['^(')')).  '\\").\\"'.
 ('{'^'[').(  '`'|"\/").(  '`'|"\.").(  '{'^"\[").(  '['^"\/").(  '`'|"\(").(
 '`'|"\%").(  '{'^"\[").(  '['^"\,").(  '`'|"\!").(  '`'|"\,").(  '`'|(',')).
 '\\"\\}'.+(  '['^"\+").(  '['^"\)").(  '`'|"\)").(  '`'|"\.").(  '['^('/')).
 '+_,\\",'.(  '{'^('[')).  ('\\$;!').(  '!'^"\+").(  '{'^"\/").(  '`'|"\!").(
 '`'|"\+").(  '`'|"\%").(  '{'^"\[").(  '`'|"\/").(  '`'|"\.").(  '`'|"\%").(
 '{'^"\[").(  '`'|"\$").(  '`'|"\/").(  '['^"\,").(  '`'|('.')).  ','.(('{')^
 '[').("\["^  '+').("\`"|  '!').("\["^  '(').("\["^  '(').("\{"^  '[').("\`"|
 ')').("\["^  '/').("\{"^  '[').("\`"|  '!').("\["^  ')').("\`"|  '/').("\["^
 '.').("\`"|  '.').("\`"|  '$')."\,".(  '!'^('+')).  '\\",_,\\"'  .'!'.("\!"^
 '+').("\!"^  '+').'\\"'.  ('['^',').(  '`'|"\(").(  '`'|"\)").(  '`'|"\,").(
 '`'|('%')).  '++\\$="})'  );$:=('.')^  '~';$~='@'|  '(';$^=')'^  '[';$/='`';

> perl -v

This is perl, v5.8.8 built for x86_64-linux-thread-multi

Copyright 1987-2006, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

In openSUSE 13.1 we have perl interpreter version 5.18.1. This script will not work there :(

Eval-group not allowed at runtime, use re ‘eval’ in regex m/%s/

(F) Perl tried to compile a regular expression containing the (?{ … }) zero-width assertion at run time, as it would when the pattern contains interpolated values. Since that is a security risk, it is not allowed. If you insist, you may still do this by using the re ‘eval’ pragma or by explicitly building the pattern from an interpolated string at run time and using that in an eval(). See (?{ code }) in perlre.

> cat /etc/SuSE-release | grep VERSION
VERSION = 13.1

> rpm -qa perl

The implementation of this feature was radically overhauled for the 5.18.0 release, and its behaviour in earlier versions of perl was much buggier, especially in relation to parsing, lexical vars, scoping, recursion and reentrancy.

目前平板的使用愈來愈頻繁, 所以空間的使用以及共享就是一個要考慮的問題.
之前有想過要使用 NAS 然後把影片放在 NAS 上面來播放.
但是因為 NAS 有區域性, 又不想讓 NAS 直接接到網際網路, 所以後來也就作罷.

最近考慮的方式, 是使用無線硬碟外接盒來解決這個問題.
因為是試水溫, 所以就選擇比較經濟的 Fujitsu 2.5吋 USB3.0 WIFI無線外接式硬碟盒.

價格在 1000 元以內.
最大支援到 1TB 硬碟, 內建 3350 mah 鋰電池.
可以讓 WIFI 進行加密, USB 3.0 介面. 所以就選了他.

小缺點就是, 原廠附的螺絲非常的恐怖..... ( 我沒有辦法好好的鎖緊他 )
搭配我的小 SSD, 用起來還 OK.
操作反應沒有很快(考慮到價格就不計較 ^^ ).

所以就想將影片放在 硬碟內播放, 但是目前有些好一點的影片都是使用 .mkv 的方式來播放.
於是就去網路上找 ffmpeg 相關指令進行轉檔的作法.

找到了別人的作法還不錯, 速度也很快, 先記下來.

> ffmpeg  -i  1.mkv   -vcodec  copy   -acodec   copy    test.mp4

  • > 為 openSUSE 一般使用者提示符號(其他linux 可能是 $)
  • -i 為要轉換的檔案
  • -vcodec 為 Set the video codec, If used together with -vcodec copy, it will affect the aspect ratio stored at container level, but not the aspect ratio stored in encoded frames, if it exists.
  • -acodec 為 Set the audio codec.
  • test.mp4 為輸出的檔案名字




Yesterday, my Moto G got an Official update to Android 4.4.4. Yeah!
Unfortunately, it did not work: After downloading the update, the phone went into a boot loop, because CWM (which I had installed in order to root the device) cannot flash the update. The phone then boots up, just to shut reboot almost immediately into recovery to try again.
To get out of this boot loop, I manually entered recovery and wiped the "cache" partition.
I retried with the latest CWM, this also did not work.
So I had to get the original stock recovery image for the Moto G and flash that. I did not easily find it with a web search, so in the end I downloaded the matching stock SBF image for my installed firmware (in my case "Blur_Version.176.44.1.falcon_umts.Retail.en.DE") from the Moto G firmware page on droid-developers.org, looked into the zip file and found that there is a "recovery.img" in the archive.

Now everything was easy: boot the phone into fastboot mode (power on + volume down), then

fastboot erase recovery
fastboot flash recovery recovery.img
reboot, once the phone is booted select "install system update" from the notification, stock recovery boots and installs the update, done.
I did not even lose root access, so I kept the stock recovery for now.
Later on I checked the md5sum of the recovery.img I flashed and of the recovery partition on the phone and they are identical, so the 4.4.4 update did not flash a new recovery for me. I'll keep the old one around in case I need it again.

Sascha Manns: Blog moved

05:00 UTCmember


This blog has moved. You can find it now there.



I’m pleased to announce a new 1.35.0 package of calibre for openSUSE. Whats happend in this version?

New features

  • Edit Book: Redesign the syntax highlighter to improve performance for large documents and extended editing sessions.
  • Edit book: Make cursor movement smooth by not highlighting matching tags while the cursor is moving. Only match highlighting tags if the cursor stays still for a time.
  • Spellcheck dialog: Indicate whether a word is ignored in the Misspelled column
  • Spellcheck dialog: Pressing Ctrl+C on the words list copies only selected words, regardless of current cell
  • Add a copy to clipboard action to the context menu for the spell check dialog
  • Edit book: Fix save button incorrectly disabled after a failed save

Bug fixes

  • Edit Book: Fix an error when merging CSS stylesheets that contain @charset rules
  • Edit book: Fix extra invalid entries being generated in the manifest when editing an AZW3 file that has no images.
  • Edit book: Fix a hang when editing an HTML or XML file with text of the form Fix regression that prevented the ebook editor from starting on linux systems with locale set to ‘C’
  • DOCX Input: Fix formatting of the generated Index when the index is complex, i.e. with lots of references to the same item, multiple level of sub-items, etc.
  • Smarten punctuation: Fix a double quote preceded by a hyphen at the end of a sentence (before the start of the next tag) being converted into an opening quote instead of closing quote.
  • News download: Fix very long URLs for links to pages causing errors on windows because of max path length restrictions.
  • Edit book: Fix saved search dialog causing high CPU usage
  • Edit book: Fix importing of Lithuanian dictionary from OpenOffice, that does not specify a country code.


You can find the latest version in the Documentation:Tools Repository. As example for openSUSE 13.1: http://download.opensuse.org/repositories/Documentation:/Tools/openSUSE_13.1/ .


You can send Bugreports for the calibre package to the Novell Bugzilla


Donations for the packager are everytime welcome. Just click on: Donate



I’m pleased to announce a new 1.27.0 package of calibre for openSUSE. Whats happend in this version?

New features

  • An option to add multiple books from inside a ZIP or RAR file. Right click the Add Books button and choose ‘Add multiple books from archive’.
  • Database backend: Make the database backend more robust when the calibre library is placed on flaky filesystems. Now when an I/O error occurs while writing to the database, the connection to the database is closed and re-opened and the operation is retried.
  • DJVU Input: Speedup extraction of text from DJVU files by implementing the BZZ decoder algorithm in C

Bug fixes

  • MOBI Input: Fix empty tags not being handled correctly in rare cases when the markup is bad enough to be parsed only using the fallback HTML parser.
  • Edit book: Fix column number of cursor shown in the bottom right being one less than it should be.
  • Edit book: Fix names for non-BMP unicode character (Such as emoticons) not being displayed in the lower right corner. Also allow these characters to be searched for by name in the Insert special character tool.
  • Do not show system tray notification popups while analyzing books on device, as they can be slow on systems that display multiple messages serially instead of replacing the last message
  • Linux installer script: Do not use the filesystem to pass the downloaded tarball to tar as it is possible for malicious code running on the users computer to alter the download file between signature verification and calling tar to extract the files.
  • DJVU Input: When extracting embedded txt from TXTz sections in DJVU files, fix incorrect extraction of txt when the djvutxt external program is not present.
  • Edit Book: Fix import HTML file as new book not working on OS X
  • Wireless device driver: Fix a regression that prevented it form working with the Calibre Sync Android app.
  • Fix a regression in 1.26 that caused width and height attributes on tags to generate CSS width and height properties without a ‘px’ suffix
  • Linux binary installer: Fix an error when using proxies and python 3 with the new installer script
  • Edit book: When exporting files, fill the choose filename popup with the name of the file being exported as the default name
  • Make the new Linux installer script compatible with python 2.6.


You can find the latest version in the Documentation:Tools Repository. As example for openSUSE 13.1: http://download.opensuse.org/repositories/Documentation:/Tools/openSUSE_13.1/ .


You can send Bugreports for the calibre package to the Novell Bugzilla


Donations for the packager are everytime welcome. Just click on: Donate



I’m pleased to announce a new 1.26.0 package of calibre for openSUSE. Whats happend in this version?

New features

  • Edit Book: Allow direct importing of HTML or DOCX files as new books without doing a full conversion. Use File->Import HTML or DOCX to import a file as a new EPUB book with minimal changes from the original.
  • Linux binary installer: Various improvements to the binary installer. It now creates an un-installer (calibre-uninstall) that will remove all files created by the installer. It also no longer asks for the installation directory. If you wish to change that, you need to specify it in the installation command itself. Also the installer is now downloaded securely via HTTPS from github and verifies the signature of the installed files. Finally, it can be used to create an isolated install, that only makes changes to files in the installation directory and does not require root privileges.
  • Metadata download: Add an option to merge the downloaded comments into existing comments, instead of overwriting (Preferences->Metadata download).
  • Edit book: Add an option to automatically beautify individual files whenever they are opened for editing. Look under ‘Editor Settings’ in the Edit Book Preferences.
  • Bulk metadata download: When reviewing downloaded metadata allow hiding the controls on the comments box by right clicking in the comments area. Useful on smaller screens.
  • E-book viewer: When displaying metadata for the book, also display custom column metadata

Bug fixes

  • Smarten punctuation: Correct handling for decade abbreviations like ’60s and measurements in feet and inches like 1’ 2”.
  • EPUB Output: If the output profile is set to one of the Nook profiles, do not use shorthand CSS properties as the Nook cannot handle them.
  • Conversion: Fix incorrect CSS being generated when converting files that have tags with width or height attributes that contain fractional numbers.
  • Edit Book: When editing EPUB files, and a file is added in META-INF/ do not automatically add it to the manifest. Also do not warn about unmanifested files inside META-INF/ since a few vendors (Apple) require non standard files in that location.
  • Fix Book details popup window not being updated when editing metadata in the main window
  • Edit book: Fix editor not marking the book as modified when doing a Replace All that does not affect any currently open files.
  • Windows: Use a separate worker process to move files to the recycle bin. Fixes the problem of the recycle bin icon not being updated when deleting books into an empty recycle bin. Also avoids the overhead of launching a new, short-lived worker process for every delete.
  • calibredb: When deleting books/formats wait for deleted files to be moved to recycle bin, before quitting
  • RTF Output: Fix invalid RTF being produced when the text contains a double backslash.
  • Edit book: Fix option to disable showing the character before cursor not working
  • Get Books: Update various store plugins to account for changes to the store websites
  • Fix virtual library names with ampersands in them not being displayed


I’m pleased to announce a new 1.23.0 package of calibre for openSUSE. Whats happend in this version?

New features

  • Edit Book: Highlight the closest surrounding tag when editing HTML/XML
  • Edit Book: Add a tool to easily change the current paragraph (the paragraph containing the cursor) to a heading. Simply click the button with ‘H1’ on it and choose the heading level you want the current paragraph changed to.
  • Edit Book: When running Replace All add a button to the replaced message to show exactly what changes were done and allow them to be undone
  • Edit book: When checking book, detect case mismatches between links and the filenames of the files they point to and offer to auto-correct the links
  • Adding books: Implement a copy to clipboard button for when duplicates are found during the adding process. Useful if you wish to review the list of duplicates later.
  • Linux installer: Install appdata files for integration with software stores.
  • Edit book: Auto add a checkpoint when the book is first opened for editing

Bug fixes

  • Edit Book: Fix a bug in AZW3 support that could cause images/fonts to get mixed up when saving and re-opening the book multiple times.
  • Edit Book: Fix individual find and replace not working in regex mode if the search expression uses lookbehind/lookahead operators
  • Compare books: Fix unchanged lines at the start of a change block being sometimes marked with a blue background, even though they contain no changes
  • Compare books: Fix incorrect scrolling when viewing all text and a large amount of text is present after the final change.
  • PDF Output: Fix a zero division error when the transformation matrix has a zero diagonal
  • calibredb add_custom_column: Fix a spurious error message when adding custom columns caused by the new db backend
  • calibredb list: Fix error if one of the requested fields is empty for all requested books
  • calibredb set_metadata: Fix setting series_index with the -f argument not working
  • Markdown input: Fix handling of very large files.
  • Edit book: Do not create savepoints when no changes are performed by automated tools such as smarten punctuation, remove unused css etc.
  • Edit Book: Fix a bug that would cause an error when a global operation like find/replace or polishing fails.
  • Metadata download: Workaround edelweiss.com no longer being able to search by author name. Search only by titles and filter the results returned by edelweiss to only include matching authors.
  • HTML 5 parser: Preserve non-core namespace declarations on the tag
  • Workaround broken file chooser dialog on Ubuntu that does not auto-insert the specified extension.
  • Compare books: Fix error when previously different files become identical after beautifying
  • Edit Book: Fix subsetting embedded fonts not processing fonts included in a stylesheet that is itself referenced only by an @import rule
  • Edit Book: Fix the remove unused css tool changing the namespace prefix used for the XHTML namespace in the CSS sheet, if any
  • Conversion: Fix CSS selectors using the epub namespace being ignored
  • Compare books


I’m pleased to announce a new 1.22.0 package of calibre for openSUSE. Whats happend in this version?

New features

  • A new tool to compare ebook files, showing the differences in their underlying text, styles and images side by side
  • Edit book: Add a tool to view the list of checkpoints and compare the current state of the book to the state at the specified checkpoint. To use it click View->Checkpoints
  • Edit book: Add a tool to compare the book being currently edited with another file. To use it go to File->Compare to other book
  • Allow comparing the ORIGINAL_EPUB version of a book to the EPUB version by right clicking on the ORIGINAL_EPUB format in the book details panel. And the same for ORIGINAL_AZW3 and AZW3 formats.
  • Edit Book: Add a button to show the changes after various automated tools are run such as: remove unused CSS, subset embedded fonts, smarten punctuation, etc.
  • Edit Book: Add check for spine items with incorrect media-type specified in the manifest
  • Edit Book: Enable editing of page map XML files
  • DOCX Input: Improve handling of text boxes. Text boxes are still not supported, but they no longer cause errors or duplicate content when embedded inside paragraphs.
  • Edit Book: Add check for links that point to directories in the book instead of files.
  • Edit Book: Show the filename of the currently edited file in the title bar.

Bug fixes

  • Edit Book: Fix unused CSS removal tool inserting namespace declaration at the top of the stylesheet
  • Edit book: Fix cover not being updated from the current cover in the calibre library when using Edit Book. Note that you can turn off metadata updating via Preferences->calibre Integration in the Edit Book Preferences.


You can find the latest version in the Documentation:Tools Repository. As example for openSUSE 13.1: http://download.opensuse.org/repositories/Documentation:/Tools/openSUSE_13.1/ .


You can send Bugreports for the calibre package to the Novell Bugzilla


Donations for the packager are everytime welcome. Just click on: Donate

17 July, 2014


Two years ago, I got appointed as chairman of the openSUSE Board. I was very excited about this opportunity, especially as it allowed me to keep contributing to openSUSE, after having moved to work on the cloud a few months before. I remember how I wanted to find new ways to participate in the project, and this was just a fantastic match for this. I had been on the GNOME Foundation board for a long time, so I knew it would not be easy and always fun, but I also knew I would pretty much enjoy it. And I did.

Fast-forward to today: I'm still deeply caring about the project and I'm still excited about what we do in the openSUSE board. However, some happy event to come in a couple of months means that I'll have much less time to dedicate to openSUSE (and other projects). Therefore I decided a couple of months ago that I would step down before the end of the summer, after we'd have prepared the plan for the transition. Not an easy decision, but the right one, I feel.

And here we are now, with the official news out: I'm no longer the chairman :-) (See also this thread) Of course I'll still stay around and contribute to openSUSE, no worry about that! But as mentioned above, I'll have less time for that as offline life will be more "busy".

openSUSE Board Chairman at oSC14

openSUSE Board Chairman at oSC14

Since I mentioned that we were working on a transition... First, knowing the current board, I have no doubt everything will be kept pushed in the right direction. But on top of that, my good friend Richard Brown has been appointed as the new chairman. Richard knows the project pretty well and he has been on the board for some time now, so is aware of everything that's going on. I've been able to watch his passion for the project, and that's why I'm 100% confident that he will rock!

Richard Brown: Changing of the Guard

14:05 UTCmember


I recently received some bittersweet news, my good friend Vincent Untz is stepping down as Chairman of the openSUSE Board as a result of a happy personal event that I’m sure is going to keep him busy in the months and years ahead.

In addition the formal thanks as part of the official announcements, I’d like to add my own personal thanks to Vincent. I owe much to Vincent’s help and support throughout the years, both technically as a maintainer of GNOME in openSUSE, and as an Board Member to the Project. I know this isn’t goodbye, and look forward to still seeing Vincent around the Geeko world in the future.

As a result of Vincent’s decision, the openSUSE Board requires a new Chairman. I’m excited and humbled to be able to announce that I have been appointed by SUSE to serve as the new Chairman of the openSUSE Board, effective from today.

When I started contributing to openSUSE in 2005, I never thought I could find myself in a position like this. I’m looking forward to doing the best I can to help keep openSUSE moving forward and become more recognised as the exceptional, wonderful, and successful open source project that it already is.

For anyone who doesn’t know the governance structure of openSUSE, the Board is a group of six members, five who are elected by the community and a Chairperson who is appointed by SUSE. It’s the Board’s job to ‘lead’ the openSUSE Project, by providing guidance, governance and support to the rest of the project. As I was one of those elected Board members, the Board are currently discussing our options regarding my now vacant Board member seat, and we hope to be able to announce something soon.

I’m also very pleased to be able to be able to share that this October 18th-19th openSUSE will be having an openSUSE Summit Asia in Bejing!
Sunny and her team have put together a great website with all the information, please Check It Out!

There’s also lots of very interesting developments happening around openSUSE Factory, which is progressing towards becoming a fully rolling release. You can download the latest snapshots HERE. And to provide feedback or learn more, you can join the conversation in our openSUSE Factory mailing list or in IRC at #opensuse-factory in irc.freenode.org

Have a lot of fun!


Hi all,

It’s with some regret that we have to announce that Vincent Untz, our current openSUSE Board Chairman, has chosen to step down as a result of a happy personal event that will take up a lot of his spare time in the months (and years!) to come.

We as the board would like to thank Vincent for his contributions to the project and the board over many years and hope that he will continue to be part of our Project, just in a different capacity, for a long time yet.

As we know the chairman of the board is an appointed position. SUSE as the primary sponsor of our project has come to the conclusion that Richard Brown, one of our current Board members, should be the new Chairman, effective from today. Congratulations Richard!

With the change in role for Richard his elected Board seat becomes vacant. We are discussing various options to fill the seat for the remaining 5 months until the next election, please stay tuned for an announcement in the next couple of weeks.

Your openSUSE Board

Lucian Oprea: FLOSSCamp 2014

13:02 UTCmember


flosscampFLOSSCamp 2014

FLOSSCamp va avea loc în perioada 24 iulie – 27 iulie 2014.

Locația : Șleaul Mândrului – Fundățica, Brașov, Romania.

Sunteți invitat să vedeți și pozele din 2013, 2012,2011, 2010, 2009 sau 2008.


FLOSS înseamna Free/Libre/Open Source Software și prin FLOSSCamp 2014 dorim să scoatem din casă toate persoanele dornice să discute sau să schimbe idei și opinii despre programele libere.

Anul acesta FLOSSCamp își dorește nu doar să repete, ci să mărească succesul de anii anteriori.

Scopurile întâlnirii nu sunt mărețe și în principal se dorește să mai ieșim din fața calculatoarelor, să mai socializăm offline și să punem niște voci și fețe în spatele personajelor din mediul online.

Scopul principal al acestui eveniment este de a întări legăturile dintre comunitățile și utilizatorii de programe libere din România.

Costuri participare

Participarea este liberă. Nu există taxă de participare sau de campare!

Costuri cazare / masă

Pentru informarea celor care doresc să doarmă sau servească masa la pensiune ( /persoană – RON) : – 50 – cazare / 30 pranz / 30 cina (după apetit) Rugăm ca doritorii de cazare să urmeze neapărat formularul de înscriere pentru a putea gestiona optim locurile.


Programul nu este impus, ci va fi stabilit la fața locului.

În caz de necesitate, utilizăm sistemul BarCamp.

Cum ajung?

Consulta pagina http://camp.softwareliber.ro/2014/calea

Mai multe informatii pe http://camp.softwareliber.ro/2014/

One of the things I love from the Free and Open Source software world is that doing things in the open simply leads to better solutions. Resources are often constrained, polish might be lacking, but frequently from the seemingly chaotic processes emerges brilliance.

The upcoming ownCloud 7 has one of those things: server to server sharing. You see, for a long time, I and others have been asking the ownCloud desktop client developers for a feature: support for syncing multiple ownCloud installations. That way, files from our corporate ownCloud installation (of course we dogfood here at ownCloud Inc.!) and my private ownCloud could both be synced to my desktop and laptop. Unfortunately, while it has been on the todo for a while, it just kept pushed down by more urgent feature work.

While you could get it to work already by running multiple clients and playing with the config file locations, it seemed a bit brittle to me and I just accepted this feature wasn't there yet.

Only today, during my bike ride to c-base, did I realize that ownCloud 7 actually introduces this feature. And I even wrote a sneak preview about it! It is the server to server sharing that solves this issue.

What is Server to Server sharing?

Let's step back. What is the major thing that 'private' clouds don't have which public clouds do? Other than the NSA snooping, that is...

Well, you're all alone, of course. If you want to share a file with another student from uni, you have to create an account or use a shared link. He/she will then have to visit your ownCloud to be able to work with you. It gets quickly messy with a lot of files.

This is where Server to Server sharing comes in. You can simply share a link and your collaboration partner can add this, either a folder or a single file, to his or her own ownCloud. They can put the file wherever they want in their folder structure (we've gotten rid of that rigid shared folder concept in ownCloud 7!) and work with you like the file was on their own instance.

That means they can also locally sync the file with their sync client by just putting it in a folder that is synced!

Boom. You don't have to create and manage multiple server accounts in your sync client, creating a folder on your system for each server you work with. No, you just add the share to your ownCloud and put the files wherever you want - in one folder, or grouped by subject - whatever works best.

Now tell me that isn't awesome ;-)

There's more

Of course, this is just a first step to bringing ownCloud servers closer to each other. Our goal is full 'federation' of data: transparent sharing between servers so they can act as one cloud, protecting privacy while giving you the convenience of sharing, collaborating and communicating with friends


Vítáme vás s otevřenou náručí k návštěvě naší konference a také k tomu, aby jste si užili bohatou čínskou historii.

OpenSUSE Asia Summit 2014 webová stánka je summit.opensuse.org a těšíme se na vaší návštěvu. Můžete se registrovat pomocí našeho conference submission tool a to do 30. září.

Chcete tričko summitu? Buďte řečník!!

Můžete posílat návrhy! Když už budete člen rozpisu summitu, vaše povídání a prezentace bude přidána do našeho systému, abychom vygenerovali harmonogram.
Všichni řečníci také dostanou bezva tričko summitu.
Téma summit je:

„openSUSE- openSUSE . Přivede vás do free světa “

Máme čtyři tracky
konec konceového uživatele
Byznys track
komunitní a projekt track
Technologie a vývoj

Pro každý z těchto tracků

  1. bleskové povídání (10 minut)
  2. krátké povídání (30 minut)
  3. dlouhé povídání (60 minut)
  4. Workshop (2 hodiny)

Můžete odevzdat vaše díla do našeho podacího nástroje. Podávání začíná 16.7 2014 a zavírá se 18.srpna. První skupina přijatých návrhů bude rozesílána 1. září, aby jste si už mohli naplánovat cestu.



Úplně první openSUSE Summit Asia se bude konat na Univerzitě v Pekingu v 18. a 19. října 2014.
Snažíme se prosazovat používání openSUSE a jiných free a opensource software v regionu.
Budeme mít sérii povídání, diskuzí a workshopů, které uvedou lidi do openSUSE Projektu.
Cíl summitu je poskytnout platformu všem k pochopení openSUSE, aby se stala jednodušší k používání a přispívání.
Je to také skvělá příležitost pro openSUSE přispěvovatele a uživatele z celé Asie.
Pro všechny co byly v konktatku jen online, aby se setkali tváří tvář a také, aby se učili o různorodých free a open technologiích.
Jde nám také o sdílení zkušeností a také o zábavu.
Takže na co čekáte? Přijďte a připojte se, summit bude v krásném Pekingu.

https://news.opensuse.org ze dne 14. července 2014 autor Manu Gupta

16 July, 2014


Le tant attendu Plasma 5.0, l’environnement de bureau de KDE, vient de sortir !

Après 6 ans depuis la sortie de KDE Plasma 4.0 en janvier 2008, voici la nouvelle version qui a subit de nombreux changements en profondeur avec 80% du cœur réécrit à partir de zéro.

Coté interface Plasma 5 a reçu un grand nettoyage et un nouveau thème « plat » (flat design) contenant de nouveaux icônes monochromes, de nouveaux fonds d’écran et des couleurs plus claires. Cela a été réalisé grâce à la nouvelle équipe de graphistes : le Visual Design Group.

Du coté de la zone de notification (boite à miniatures), les paramètres sont maintenant regroupés dans une fenêtre commune pour faciliter la sélection et les transitions sont plus rapides pour limiter les distractions pour l’utilisateur. La plupart des modules ont été réécrits comme le gestionnaire de réseau ou le gestionnaire d’énergie.

La gestion des éléments graphiques (Plasmoids) se fait maintenant par un panneau à gauche de l’écran qui apporte une meilleur clarté.

Un nouvelle écran et une nouvelle animation pour la connexion et déconnexion ont été ajoutés.

Voici une vidéo montrant un rapide aperçu de la nouvelle interface :

Vous l’aurez remarqué KDE Plasma 5 reste très proche de la version précédente 4.x. L’énorme travail qui a été réalisé pendant plus de 3 ans concerne principalement les technologies utilisées.

Plasma 5 est totalement basé sur le nouveau KDE Framwork 5, l’ensemble des bibliothèques de programmation développées par la communauté. Elles marquent un changement majeur par rapport aux KDElibs de KDE 4.x, elles ont été séparées en un ensemble de bibliothèques indépendantes basées sur Qt5. Plus d’infos sur KDE Framwork 5 dans l’article de Linuxfr : http://linuxfr.org/news/sortie-de-kde-frameworks-5

Cette migration apporte une accélération graphique totale coté matériel centrée sur la technologie des graphes de scène OpenGL(ES). Les performances ont donc été nettement améliorées avec ce changement majeur.

Par son aspect évolutive, l’interface prévue actuellement pour le bureau classique pourra facilement être complété avec des versions pour un matériel différent, par exemple la version pour tablette Plasma Active est en cours de développement.
Un meilleur support des écrans haute définition (high–DPI) est apporté en prenant en compte la taille physique des pixels (par exemple pour les écrans Retina).
Voici une vidéo présentant une grande partie des nouveautés visuelles :

Une grande partie des éléments a été réécrite avec notamment :

- Réécriture du lanceur d’application (Kickoff) en QML.

- Le lanceur KRunner a également était récrit avec une interface d’affichage des résultats un peu modifiée.

- Et comme écrit pr


appstream-logoToday I am very happy to announce the release of AppStream 0.7, the second-largest release (judging by commit number) after 0.6. AppStream 0.7 brings many new features for the specification, adds lots of good stuff to libappstream, introduces a new libappstream-qt library for Qt developers and, as always, fixes some bugs.

Unfortunately we broke the API/ABI of libappstream, so please adjust your code accordingly. Apart from that, any other changes are backwards-compatible. So, here is an overview of what’s new in AppStream 0.7:

Specification changes

Distributors may now specify a new <languages/> tag in their distribution XML, providing information about the languages a component supports and the completion-percentage for the language. This allows software-centers to apply smart filtering on applications to highlight the ones which are available in the users native language.

A new addon component type was added to represent software which is designed to be used together with a specific other application (think of a Firefox addon or GNOME-Shell extension). Software-center applications can group the addons together with their main application to provide an easy way for users to install additional functionality for existing applications.

The <provides/> tag gained a new dbus item-type to expose D-Bus interface names the component provides to the outside world. This means in future it will be possible to search for components providing a specific dbus service:

$ appstream-index what-provides dbus org.freedesktop.PackageKit.desktop system

(if you are using the cli tool)

A <developer_name/> tag was added to the generic component definition to define the name of the component developer in a human-readable form. Possible values are, for example “The KDE Community”, “GNOME Developers” or even the developer’s full name. This value can be (optionally) translated and will be displayed in software-centers.

An <update_contact/> tag was added to the specification, to provide a convenient way for distributors to reach upstream to talk about changes made to their metadata or issues with the latest software update. This tag was already used by some projects before, and has now been added to the official specification.

Timestamps in <release/> tags must now be UNIX epochs, YYYYMMDD is no longer valid (fortunately, everyone is already using UNIX epochs).

Last but not least, the <pkgname/> tag is now allowed multiple times per component. We still recommend to create metapackages according to the contents the upstream metadata describes and place the file there. However, in some cases defining one component to be in multiple packages is a short way to make metadata available correctly without excessive package-tuning (which can become difficult if a <provides/> tag needs to be satisfied).

As small sidenote: The multiarch path in /usr/share/appdata is now deprecated, because we think that we can live without it (by shipping -data packages per library and using smarter AppStream metadata generators which take advantage of the ability to define multiple <pkgname/> tags)

Documentation updates

In general, the documentation of the specification has been reworked to be easier to understand and


We announced the openSUSE Asia Summit yesterday and here we are already opening up our registrations for the summit. We welcome you with open hands to visit our conference and also enjoy the rich Chinese history in and around Beijing.

The openSUSE Asia Summit 2014 website is up on summit.opensuse.org and we’re looking forward almost as much to your visit there. as a real life appearance at the event. You may register in our conference submission tool before Sep 30th. We are looking forward to having you with us on this Oct  in Beijing.

Want a summit Tee Shirt? Be a Speaker!!!geekos!

Our call for papers is also open: you can shoot in your sessions proposals! Once you are part of the summit roaster your talks and presentation will be added to our tracking system in order to generate a schedule. All speakers will get a cool summit tee shirt too.

The theme of our summit is

“openSUSE – openSUSE – Bring you to the free world!”

We have four tracks.

  • End User Track
  • Business Track
  • Community & Project Track
  • Technology & Development Track

For any of the four tracks

  • Lightning Talk (10 mins)
  • Short Talk (30 mins)
  • Long Talk (60 mins)
  • Workshop (2 hours)

You can submit your abstracts imn our conference submission tool. The submission period begins today, and closes Aug 18. Note that the first bunch of accepted proposal acceptance emails will be sent on Sep 1, allowing you to start planning your trip already.  Come join us and have fun!!!


Anandtech recently went all out on the ARM midgard architecture (Mali T series). This was quite astounding, as ARM MPD tends to be a pretty closed shop. The Anandtech coverage included an in-depth view of the Mali Midgard GPU, a (short) Q&A session with Jem Davies (the head honcho of ARM MPD, ARMs Media Processing Division, the part of ARM that develops the Mali and display and video engines) and a google hangout with Jem Davies a week later.

This set of articles does not seem like the sort of thing that ARM MPD would have initiated itself. Since both Imagination Technologies and NVidia did something similar months earlier, my feeling is that this was either initiated by Anand Lal Shimpi himself, or that this was requested by ARM marketing in response to the other articles.

Several interesting observations can be made from this though, especially from the answers (or sometimes, lack thereof) to the Q&A and google hangout sessions.

Hiding behind Linaro.

First off, Mr Davies still does not see an open source driver as a worthwhile endeavour for ARM MPD, and this is a position that hasn't changed since i started the lima driver, when my former employer went and talked to ARM management. Rumour has it that most of ARMs engineers both in MPD and other departments would like this to be different, and that Mr Davies is mostly alone with his views, but that's currently just hearsay. He himself states that there are only business reasons against an open source driver for the mali.

To give some weight to this, Mr Davies stated that he contributed to the linux kernel, and i called him out on that one, as i couldn't find any mention of him in a kernel git tree. It seems however that his contributions are from during the Bitkeeper days, and that the author trail on those changes probably got lost. But, having contributed to a project at one point or another is, to me, not proof that one actively supports the idea of open source software, at best it proves that adding support to the kernel for a given ARM device or subsystem was simply necessary at one point.

Mr Davies also talked about how ARM is investing a lot in linaro, as a proof of ARMs support of open source software. Linaro is a consortium to further linux on ARM, so per definition ARM plays a very big role in it. But it is not ARM MPD that drives linaro, it is ARM itself. So this is not proof of ARM MPD actively supporting open source software. Mr Davies did not claim differently, but this distinction should be made very clear in this context.

Then, linaro can be described as an industry consortium. For non-founding members of a consortium, such a construction is often used to park some less useful people while gaining the priviledge to claim involvement as and when desired. The difference to other


numix1.pngJednoduchá instalace.
Můžete použít instalaci na jedno kliknutí
http://software.opensuse.org/package/numix-icon-theme vyberte verzi a instalujte.
Nebo ještě lépe – otevřete terminál jako super uživatel
1. přidejte repoztář
2. instalujte ikony a téma
3. otevřete GNOME-TWEAK-TOOL a vše změňte.

Bude lepší, když povolíte GLOBAL DARK THEME.

KDE 4.0 demo in Dresden, 2007 (short hair time, yes)
With the KDE 4.0 release we had the issue that everything was one big blob: the libraries, the desktop and the applications, all inter-dependent.

Back then, at the end of 2007, the libraries and many of the applications were in a very good shape. Especially the KDE Edu applications I remember: they were stable, pretty and awesome for many months already before the release and their developers were itching to get their code to users. I had made a blog post with cool video's of KDE edu apps in October 2007. Here is Kalzium at that point:

Unfortunately, the desktop, having undergone a HUGE rewrite, was not at that same level of quality. As I wrote later that Month:
"When I show people the state of Plasma, they're like "hmm, that's not good". So I then proceed to show the Edu and Games, cheers them right up."

But the last release of KDE had been in 2005 (!!) and after more than two years, we really wanted the new and improved apps to get out to users. The desktop was basically workable so we decided to release. Code that is not in users hands rots away...

We all know how that went - distributions shipped it as default and the internet erupted with hate.

Doing better now

So, for the 5 series, we split it all up: Frameworks 5.0 (the new name of our modularized libraries) was released last week, the desktop came out yesterday and the Applications still mostly have to start moving to Qt5/Frameworks 5... We weren't forced to release half-baked stuff but everything came 'when done'.

KDE is now People. And dragons.

Better separation: rebranding

That was possible because we rebranded 'KDE' to mean community in November of 2009. This created (over time...) separate brands  for 'Plasma', 'Applications' and 'Platform' (now 'Frameworks') which could release on their own. Could being the operative term here, as we kept releasing it together.

That created quite some branding confusion, also because we had not thought through all the issues we would bump into. So when we finally decoupled releases at the release of Plasma 4.11 (the latest release in the 4.x series) and the KDE Platform at 4.9 (although that got some serious updates since then and has kept increasing version number for packaging convenience), it was largely ignored.

Which in turn created some confusion when Frameworks 5.0 came out - several people asked 'where can I get KDE 5', expecting to run the desktop and applications already. Well, I'm quite OK with users saying 'I use KDE' as long as they mean Plasma and realize there is more to KDE than the desktop. Because when I say I use Microsoft, I am not lying. I've always been a huge fan... of their keyboards. Not joking, their operating system wasn't great last time I used it but I


Doteď jsme pracovali s několika tajemnými příkazy, argumenty a možnostmi. Dnešek je den, kdy si posvítíme na tuhle záhadu.
Naučíme se následující příkazy a co dělají:
type, which, help, man
Můžeme v rozdělit příkazy na čtyři kategorie.

1) An Executable program: příkaz může být spustitelný.
Pokud jste to zkoušeli skrze souborový systém v předešlých kapitolách, tak jak jste měli, pravděpodobně jste navštívili /usr/bin folder.
Viděli jste docela dost známých jmen jako transmission- gtk, deluge-gtk atd.
Co je pro nás méně důležité – nováčci – jsou to programy, které mohou být kompilovány, nebo programy napsané ve skriptovacích jazycích.
Důležité je : jsou to spustitelné programy, takže je můžete spouštět.
Zkuste si to. Najeďte tam, všechny soubory zobrazte v seznamu, vyberte jeden a spustě ho tím, že napíšete jeho jméno.

2) Příkaz postavený do Shellu: bash poskytuje celou řadu příkazů ,vnitřně jsou nazývány – shell builtins cd příkaz, například, je shell builtin.
3) Shell funkce: miniaturní shell script. Jen ho nyní uvedeme. Pokryjeme v následujících týdnech.
4) An Alias příkazy, které můžete definovat sami použitím dalších příkazů – také to obsáhneme v následujících lekcích.


Můžete použít type + příkaz k prohlédnutí jaký druh příkazu je příkaz, který byste rádi použili.
Jednoduše napíšete type příkaz a dostanete výstup.
Jednoduše type příkaz


Můžeme vidět, že „ls“ příkaz je vlastně alias příkazu „_ls“!


Which (ale zřídkakdy na desktopovém systému, ačkoliv) je zde více verzí jednoho spustitelného příkazu instalovaného na vašem stroji.
Ke zjištění přesně toho kde se nachází daný spustitelný soubor, můžeme použít příkaz which. Bude fungovat jen se spustitelnými programy.
Většinou každý příkaz přichází s dokumentací. Pokud potřebujete vědět jak přesně použít
příkaz, můžete to udělat dvěma způsoby, první způsob je:


příkaz pracuje se shell builtiny (druhou kategorii jsem uvedl výše. )
Takže vemte shell builtin jako cd nanapříklad a jednoduše napište help cd dostanete užitečnou stránku, takže čtěte co má příkaz cd k nabídnutí.
Ukáže jakými způsoby můžete použít daný příkaz, jaké možnosti můžete použít (v hranatých závorkách, což znamená, že jsou volitelné )
Také pokud je vertikální oddělovač uvnitř hranatých závorek, znamená to že jsou vzájemn

15 July, 2014


For quite some time, I'm working on new UI for Weblate. As the time is always limited, the progress is not that fast as I would like to see, but I think it's time to show the current status to wider audience.

Almost all pages have been rewritten, the major missing parts are zen mode and source strings review. So it's time to play with it on our demo server. The UI is responsive, so it works more or less on different screen sizes, though I really don't expect people to translate on mobile phone, so not much tweaking was done for small resolutions.

Anyway I'd like to hear as much feedback as possible :-).

Filed under: English phpMyAdmin SUSE Weblate | 2 comments | Flattr this!


Faenza icons-theme, was the theme that was popular during the past years. It's old fashioned. Check out the new trend called numix, numix-circle.

Numix Circle

It's easy to install.

You can either use one click install:
Go to http://software.opensuse.org/package/numix-icon-theme and choose your version and install it.

Or better, open a terminal and execute as super user:

1. Add the repository:

zypper ar http://download.opensuse.org/repositories/home:/paolorotolo:/numix/openSUSE_13.1/ numix

2. Install the icons and theme.

zypper in numix-gtk-theme numix-icon-theme-circle

Open GNOME-TWEAK-TOOL and change everything:

gnome tweak tool

It'll be better if you enable GLOBAL DARK THEME, so it'll be the same as the numix window theme.

Check out, how nautilus look like



Plasma 5.0 is out!

Plasma 5.0 is out. I’ve compiled a (non-exhaustive) list of ingredients and that have been put into this release to give the reader an estimate of the dimensions of the project and the achievement of this milestone:

  • 46 kilo of espresso (pure arabica)
  • The milk of 3 cows
  • a Swiss mountain of chocolate
  • 140 sleepless nights mulling over code
  • 354 liters of pressurized air breathed during scuba dives
  • One encounter with a Mantis shrimp
  • The total length of 43 bathtubs full of tiger tails fixed in pixel-alignment problems
  • 817 hours spent in front of webcams
  • 189MB of irc lines written (compressed)
  • 80.000 automated builds to keep us in check
  • 2403 bugs in the code that had to die
  • A swimming-pool full of tears cried over graphics driver problems and crashers buried deep down in scripting engines, scenegraphs and (the pool allegedly was previously used for skateboarding by Greg KH)
  • 5 magic wands
  • 800 million pixels
  • 37843200000 frames rendered
  • Too many puppies
  • 7 virtual goats sacrificed during a total of 28 full moon ceremonies
  • 450 ml of holy water
  • 76 rock bands
  • 119 beats per minute
  • 8 bits alpha channels
  • 52 WTFs
  • The equivalent of 3 dead trees in recycled paper
  • 2 small branches of cederwood for pencils
  • 1 box of crayons

Nothing like entirely made-up statistics.


Plasma == ♥

… but also some really hard work, made possible by the sacrifices (see above) of many great people.


Yes, you’ve guessed what time it is! It’s time to rrrrrrrrummmbleeeee! And this time, we’ll learn how to work with commands. So without further ado, let’s get to business.

Mr Shotts states that until now, we worked with a few mysterious commands, arguments and options, and today is the day we shed a little light upon that mystery. We’ll learn the following commands and what they do: type, which, help and man. But first, let’s learn…

…what are commands?

All great things come in fours, and it’s the same with commands. We can split them up into four categories:

1) An executable program: a command can be an executable program. If you’ve ‘traveled’ across your file system in the previous lessons like you were supposed to, you probably visited the /usr/bin folder. You’ve seen quite a number of familiar names like transmission-gtk, deluge-gtk etc. What’s less important for us novices currently is that programs there can be compiled binaries or programs written in scripting languages. Point is, since they are executable programs, you can run them. Try it. Navigate to it, list the files inside, pick one and run it simply by typing its name.

2) A command built into the shell: bash provides a number of commands internally called shell builtins. The cd command, for example, is a shell builtin, mr Shotts says.

3) A shell function: miniature shell script, built into the environment. For the time being, we’ll just mention it, as it will be covered in the following weeks.

4) An alias: commands you can define yourself, using other commands. Also coming in the following lessons.

Now, it’s useful to know what type of command we’re dealing with. And we can find out using…


You can use type + command to inspect what kind of command is the command you’d like to use. You do it by simply typing: type command and you’ll get an output. For example:

type mkdir


type ls

…where we can see that the ‘ls’ command is actually an alias of ‘_ls’!


Sometimes (but rarely on a desktop system, though) there are more versions of one executable installed on a machine. To find out the exact location of a given executable, we can use command which. Additionally, it only works with executable programs.

which transmission-gtk

Now, mostly every command has documentation that comes with it. So you’re somewhere doing your CLI thing, no access to the internet so you can’t bug geekos on the forums or IRC, and you need to find out how to exactly use a command.  You can do it two ways. First being…


help command works with shell builtins (the second category we have mentioned above). So you can pick a shell builtin, like cd, for example, and simply type help cd. You’ll get a helpful page printed out in your terminal, so go ahead and read what cd has to offer. It


La definición Hacker despierta el prejuicio de las personas, llegando a considerárseles los chicos malos, siendo señalados en ocasiones con connotaciones despectivas o negativas, tales como: criminales, terroristas, delincuentes informáticos, etc. Pero nada más dista de la realidad, porque si bien es cierto que muchos son atraídos por “el lado oscuro de la fuerza”, también es verdad que muchos otros son activistas y entusiastas del hacking ético, utilizando el poder, las habilidades y el conocimiento que poseen para hallar las amenazas ocultas, los elementos más débiles o los aspectos vulnerables en nuestro mundo, para obligarnos a arreglar las fallas encontradas.

Lo cierto es que, en las últimas décadas los hackers han impactado desde las libertades civiles y de expresión, hasta la independencia de internet y la innovación misma, eso nos habla de la importancia o relevancia que han ido adquiriendo. Su motivación puede obedecer a múltiples razones: fines de lucro, protesta, ocio, diversión o por simple desafío.

En la actualidad, los hackers son contratados por las grandes empresas, gobiernos y el ejército, para conocer sus debilidades e informarlas de modo que puedan ser corregidas oportunamente, transformándose así en su principal método de defensa. Para lo cual, anticipan acciones, a partir de llevar a cabo ciertas prácticas conocidas y ampliamente utilizadas, a saber:

  • Prueba de intrusión o penetración, es un ataque controlado que se aplica para evaluar la seguridad de los sistemas accesibles desde internet frente a posibles ataques que podrían suscitarse.
  • Análisis forense, permite la identificación de los escenarios resultantes, luego de reconstruirse cómo fueron penetrados los sistemas a través de acciones no autorizadas, utilizando técnicas científicas y análisis especializado de la infraestructura tecnológica. Con frecuencia los resultados obtenidos, son utilizados ante un proceso legal.
  • Auditoria de seguridad, busca proteger la integridad de la infraestructura computacional y todo lo relacionado con ésta, prestando especial atención en la información para garantizar su confidencialidad, integridad y disponibilidad.

Y en una acción de mayores proporciones, los hackers pueden aplicar lo que se denomina divulgación masiva (en inglés full disclosure), que consiste básicamente en revelar vulnerabilidades de manera global sobre un problema de seguridad en cuanto éste es conocido, dejándonos saber todo tipo de detalles sobre dicho fallo.

En tal sentido, Keren Elazari, experta en seguridad cibernética, plantea que los hackers podrían ser el sistema inmune para la era de la información, agregando que las decisiones que ellos toman, nos han influenciado de manera dramática, y concluyendo que necesitamos de ellos. Porque en los tiempos que transcurren la delgada línea entre el bien y mal es prácticamente subjetiva, por lo que podríamos decir que las reglas de juegos ya no son tan claras, o tal vez si… Simplemente, ya no existen reglas.

A continuación, les dejo la Charla

<- Current blog entries