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.

22 July, 2015

Jos Poortvliet: Link

12:35 UTCmember

The Washington Post again demanded that tech companies create special 'golden keys' for authorities to keep and use for access to private communication. Protected by a warrant, of course. For the benefit of this discussion (which is really getting old), I just put together the reasons why it is a dumb idea.

First of all. It is a pure fantasy, an entirely unrealistic wish of the Pink Unicorn variety that it is possible to create a key which only the US goverment (and other sanctioned agencies) would have access to. It is technically not possible. Ever. I explained that before so let me now just quote Bruce Schneier:
"We have one infrastructure. We can't choose a world where the US gets to spy and the Chinese don't. We get to choose a world where everyone can spy, or a world where no one can spy. We can be secure from everyone, or vulnerable to anyone. And I'm tired of us choosing surveillance over security."
And let's be clear - we've been over this, the Clinton government wanted a similar thing with the Clipper chip and as security researcher Matthew Green pointed out:
Clipper is only one of several examples of 'government access' mechanisms that failed and blew back on us catastrophically.
A second issue with the proposal is that it doesn't do anything. Just like all the spying programs that came before in this and previous decade. Here's Bruce talking about that, here the Guardian, the Newyorker, Wired and Washingtonsblog. Whatever these spy programs do - from spying on German Chancellor Merkel to US congress (that's the Washington Post itself!) to the United Nations and Unicef - the government spying programs certainly don't target or are helpful against terrorism or pedophilia or any of the other stuff they are claimed to be for. And neither will these 'golden keys' be used to catch terrorists.

Last, and this should already be blindingly clear if you see the list above of some of the targets of surveillance, you should doubt if the government agencies will abide by the rules - they haven't in the past.

I also want to point out that the very reason we're having this conversation in the first place is because we're idiots.


Muitos xiitas pode não gostar deste post, mas a verdade seja dita, a Microsoft vem se reinventando com a a abertura do código fonte do .NET Core e suporte oficial da empresa ao Linux. Com o meu amadurecimento defendo hoje a liberdade de escolha e não a obrigatoriedade do uso do Linux (caso contrário onde estaria a liberdade). CLARO que não consigo ficar mais sem o Linux no meu dia a dia, mas existem pessoas que por algum motivo desejam continuar com outros sistemas e respeito isto com maturidade. Sem contar que muitos sistemas legados escritos em .NET em breve poderão roda no nosso GNU/Linux,


Agora é oficial a parceria e apoio da Microsoft ao serviço Serviço Certiface (serviço em nuvem de reconhecimento facial e biometria) e mesmo sendo todo baseado em Linux. Para a Microsoft o importante é o conceito de interoperabilidade, como a Microsoft Azure suporta 100% soluções Linux (openSuSE) na sua nuvem, os ambientes se tornaram viáveis em termo tecnologicos e de parceria comercial. A seguir o Vídeo da apresentação do Certiface no Microsoft Build 2015 como também o link da Formalizando a parceria.


Para finalizar este post, deixo aqui a dica de como utilizar o Visual Studio Code da Microsoft na plataforma Linux.

Primeiramente entre no link https://code.visualstudio.com/Download e selecione a plataforma linux e efetue o download do arquivo VSCode-linux-x64.zip

Apó o download descompacte o arquivo com o comando zip e pronto execute o Visual Studio Code (Eu particularmente prefiro o VI).

$ unzip VSCode-linux-x64.zip
$ cd VSCode-linux-x64/
$ ./Code



t-shirt-motiv1A job announcement for a Release Engineer for openSUSE was published today and it offers a unique challenge, which sounds pretty cool. The optional bonus challenges to be included in the candidates’ application are:

1. Being a regular contributor to a community distribution? Point us to your work!

2. Using a programming language of your choice, write a small program that extracts all CVE identifiers from a given set of RPMs, and creates a sort index mapping CVEs to packages.

Bonus points if you can do it in 10 lines of perl. Extra bonus points if our perl experts scratch their head and ask “how does he do that?!” :)

3. Find out what changed in the minimal text installation between 13.2 and current TW and try to find the reasoning behind the changes.

Providing answers to the challenge really give people applying for the position an opportunity to stand out among other candidates.

There are many smart people in the openSUSE Community and taking part in the openSUSE Project every day constantly reminds me of how many brilliant people I work with here in Germany and elsewhere.

If you are going to apply for this position, be sure to bring your “A Game” because to make our perl experts scratch their head is quite the challenge.

21 July, 2015


java no linux

Java é uma linguagem e ao mesmo tempo uma plataforma importante. No Linux, cada distribuição tem seu modo de fornecer o Java e para dar aos usuários um método que funcione na maioria delas, hoje mostrarei como instalar Java no Linux manualmente (nesse caso o Java da Oracle).

Leia o restante do texto "Java no Linux: veja como Instalar manualmente"

Não está aparecendo algo?

Este post é melhor visualizado acessando direto da fonte. Para isso, clique nesse link: Java no Linux: veja como Instalar manualmente.

20 July, 2015


Assim como outros personagens reais que foram parar no quase imaginário popular, Jack, o estripador, sempre me deixou curiosa.Refrescando: Inglaterra vitoriana, século 19. Havia um assassino de prostitutas à solta no distrito de Whitechapel em Londres. 5 mulheres foram mortas, com direito à evisceração.Não sou muito chegada em livros policiais nem em jornalecos sensacionalistas da TV, mas gosto

Michael Meeks: 2015-07-20 Monday.

14:21 UTCmember

  • Mail chew, 1:1 with Kendy, Niall, lunch with H. team call. Mail chew, booked LibreOffice conference travel - thank God for RyanAir direct Stansted to Arhus; wow.


No dia 17 de julho, aniversário do Ultraman, a Tsuburaya publicou um vídeo impressionante utilizando computação gráfica onde o Ultraman aparece lutando com o Kaiju em Shibuya. “Um pdf da “Fields Gaming & Entertainment” revelou que a Tsuburaya tem planejado para 2017 uma nova série de TV de Ultraman e um filme para 2018 destinado para o público adulto. Isso pode ser algo relacionado ao trailer “Ultraman n/a” que você pode assistir logo abaixo .”

Fonte: Nihon Hero


19 July, 2015

Michael Meeks: 2015-07-19 Sunday.

21:00 UTCmember

  • Off to NCC, tried to help the older kidlets understand Good Shepherds; home for a pizza lunch, got singing our quartet surprisingly well in harmony. Tried to replicate that with other music - not so easy.
  • Advanced slugging, read books, lazed, Yes Minister in the evening. Bed.

18 July, 2015

Michael Meeks: 2015-07-18 Saturday.

21:00 UTCmember

  • Drove to Bruce & Anne's for a combined 80th and 45th birthday party celebration; a lovely time had by all, fine food, weather, wider family company etc. Babes played a quartet or two to celebrate. Chewed mail on the way home in the car, undid some data-loss, filed an easy-hack, etc.


Lee en español la entrevista al vicepresidente del la Free Software Foundation Europe antes de su charla en el Akademy 2015.


Desde la web de KDE han realizado una entrevista a Matthias Kirschner, el vicepresidente de la FSFE. Una entrevista para conocer más a esta importante persona del mundo del software libre que estará este año 2015 dando una charla en Akademy, la reunión de KDE que se celebra en A Coruña.

La entrevista se desarrolla en inglés y la puedes leer en el siguiente enlace:

Me parece interesante conocer un poco más a la persona, y sus ideas sobre el software libre, y su papel en la sociedad y la democracia. Así que la he traducido en el blog al español para que la leas. Respeta la licencia de la traducción y del original.

Si vas a ir a Akademy este puede ser un buen aperitivo para abrir boca, y si todavía estás indeciso, quizás esto haga que te decidas. Sea como sea creo que cuenta unas historias interesantes. Empezamos con la traducción, disfruta…

Cuentanos algo sobre ti mismo

Hola! Soy Matthias y soy de Berlin, trabajo para la Free Software Foundation Europe, y me encanta. Describirse uno mismo es una de las tareas más difícile, espero que me conozcais algo mejor después de esta entrevista. O mejor todavía, ¡porque no lo acabas de descubrir tu mismo en la Akademy de este año!

¿Cual fue la primera distribución de Linux que usaste y como llegaste a ella? ¿Y qué es lo que hizo que nunca volvieras a tu antiguo sistema operativo no libre ni abierto?

En 1999, mi familia tenía dos ordenadores en casa: un Intel Pentium II MMX y un Intel 486. Para el Pentium teníamos un modem, y había una conexión ethernet con el 486. Un día quise mandar correos electrónicos desde el Pentium al 486 sin la conexión a internet. No tenía mucho sentido, ya que ambos ordenadores estaban en la misma habitación, pero estaba ansioso por ver si podía hacerlo funcionar. Aunque ambos ordenadores tenían programas de “correo electrónico” instalados, no fui capaz de encontrar la manera de enviar correos directamente de un ordenador a otro.

Cuando me quejé de esto en la escuela, un amigo me sugirió una solución y me trajo al día siguiente unos disquettes con SuSE 6.0, CD’s y libros. Así es como empecé. Algunas horas después ya había hecho mi primera instalación de GNU/Linux. Para ser más precisos, al principio solo tenía la línea de comandos, no funcionaba el servidor gráfico, el ajuste del audio, ni funcionaba la impresora.

Junto con algunos amigos visitamos la LinuxTag en Stuttgart y después de eso fundamos un grupo local de usuarios

17 July, 2015

Michael Meeks: 2015-07-17 Friday.

21:00 UTCmember

  • Up early; train into Cambridge not running, struck by lightning overnight or somesuch. Drove 5x stranded others into Cambridge. Battled with awful Windows machines & hardware.
  • Meeting with Philippe & Tracie; quick lunch, back to battling hardware. Unbelievably broken Windows 7 - blue-screen and auto-re-booting with a totally generic crash-dump despite a full Acer BIOS & Intel driver upgrade, endless disk manager fiddling etc.. Attempted to install Windows 8 - after struggling to disable the horrendous anti-Linux 'secure-boot' foo - then external USB CD drive refused to play with the BIOS; irritating. Attempted to debug other thermal issues fruitlessly.
  • Home via picking up kids, relaxed watched Yes Minister with them; bit more hackery before bed.


Outro livro de Arthur C. Clarke na minha mão. Apesar de não ter gostado do filme "2001 -- Uma odisséia no espaço" (achei massante por se concentrar apenas no HAL-9000 e o final, apressado) o livro foi uma boa surpresa. E acabei gostando da forma com a qual Clarke escreve. No prefácio, o autor, morto em 2008, já diz que se Hollywood fizer um filme baseado em "O fim da infância", todos irão achar


Adding more to the Raspberry Pi Having already basically created a thermostat using a Raspberry Pi and a temperature monitor in conjunction with the WiFi power socket I was wondering what functionality I could add. Having looked around for a bit I found that there is a camera module available which can pick up infra-red […]


Running Unfortunately, it’s more running without heart rate monitoring earphones, as the fifth pair have now failed. I make that just about 5 pairs failed inside 5 months. I am not going to warranty replace these ones – there is quite clearly a flaw and I don’t really see the point in continuing to trek […]

Jonathan Ervine: Loops

06:51 UTC


Running in circles Another run without earphones was completed last night – I’ve reverted to using a Polar chest strap hear rate monitor whilst the Jabras are in their non-working state. Relatively faster and slow interval running last night – at over 30C and high humidity it’s not much fun. Jabra have offered to check […]


TV Struggles Watching live sport in Hong Kong can always be a bit of a challenge. There’s generally two providers of many things pay TV, and sometimes it feels like it’s all a bit of a stitch up. When I first arrived in Hong Kong (8+ years ago!) I signed up for nowTV with the […]

16 July, 2015

Michael Meeks: 2015-07-16 Thursday.

21:00 UTCmember

  • Mail chew, ESC call, Advisory Board call, worked on financials, misc. ranking bits.


como usar várias contas skype

Se você precisa separar suas identidades no Skype, mas não consegue usá-las simultaneamente, veja como usar várias contas Skype ao mesmo tempo no Linux.

Leia o restante do texto "Como usar várias contas Skype ao mesmo tempo no Linux"

Não está aparecendo algo?

Este post é melhor visualizado acessando direto da fonte. Para isso, clique nesse link: Como usar várias contas Skype ao mesmo tempo no Linux.


TumbleweedSince our last update on news.opensuse.org about Tumbleweed, a lot has happened. The rolling release now uses GCC 5 for the compiler. There was a large chunk of bugfixes and powerpc backports. The list for the July 2 snapshot was lengthy and quite a few packages were removed from that snapshot. Apparmor and many libraries a had extensive work done, but the real story about that snapshot is how GCC 5 was tested extensively in openQA and before being released as a Tumbleweed snapshot.

“Better tested/failed in openQA than tested/failed on your own machine, right?” wrote Dominique Leuenberger, the Factory master.

This proves the environmental care and trust people have with using Tumbleweed.

The next big thing coming in Tumbleweed will be Perl updates.

The July 11 snapshot focused primarily on KDE Plasma updating to 5.3.2 and providing bugfixes.

The last Tumbleweed snapshot on July 13 had minimal updates, but there is a reason. Why? Leap!

Leap’s milestone is being tested in openQA and receiving attention. People involved within Factory may want to check and submit the packages, for example xfce.

Polishing patterns will advance the release of the Leap milestone and some incomplete packages need attention.

The snapshot released 15 minutes ago just updated the Linux Kernel from 4.0.5 to 4.1.1.


SUSE Linux Enterprise 11SP4 byl vydán včera (tj.středa 15. července 2015 ).
Obsahuje mnoho software updatů a fíčur. Pro více info mrkněte na poznámky k desktopové verzi ZDE a na serverovou verzi ZDE


SUSE Linux Enterprise SP4 obsahuje mnoho updatů například nový openSSH a zypper.
Pokud váš počítač běží na verzi SLES11 SP3 musíte udělat několik kroků (SLES11 SP3 -> SLES11 SP4 -> SLES12
Pokud nebudete spokojeni můžete zpět downgradovat na starou verzi, stačí kliknout na undo upgrade
konec hlášení :-)

Jonathan Ervine: Progress?

08:26 UTC


New earphones! Yep – a new set of Jabra earphones turned up yesterday. As promised by Jabra, they’ve sent me a pair of Sport Coach earphones, which are supposedly the next development from the Sport Pulse ones I was previously using and breaking wearing out in rapid time. Unfortunately, this model of earphones do not […]

15 July, 2015

Michael Meeks: 2015-07-15 Wednesday.

21:00 UTCmember

  • Spammed people wrt. regression testing ideas and started collating votes. Mail chew, poked at configmgr write noise, and odd effects around inlining in Calc.
  • Miriam returned from Thorpe Woodlands having a great time, with lots of frenetic exercise .


La nueva versión de openSUSE ya se está cocinando a fuego lento. openSUSE tomando impulso para dar el salto!


Hace algo más de una semana ya pudiste leer en este blog en primicia el anuncio oficial de la nueva versión de lanzamiento regular de openSUSE, la que será conocida como openSUSE Leap 42.1 Aqui tienes el enlace por si te lo perdiste.

Hechas las presentaciones es hora de encender el horno y empezar a echar ingredientes para terminar cocinando la nueva Leap 42.1 que tiene fecha de lanzamiento para noviembre (aunque no está determinado)

Por tanto la comunidad de openSUSE ha empezado el desarrollo de esta nueva versión estable de openSUSE. Para ello utilizan openQA ¿no sabes qué es eso? Aqui tienes otro enlace interesante:

En resumidas cuentas es un test automático de un sistema operativo. En este caso se testean varios aspectos de openSUSE, con el software que se va integrando. openQA es capaz de instalar el sistema operativo y distintos aspectos del mismo e interactuar e identificar éxitos o errores en las diferentes pruebas. Ya se pueden lanzar versiones muy depuradas de un sistema.

Pero esto no quita que se sigan liberando versiones previas de prueba, para que los usuarios las testeen en sus máquinas o en entornos virtuales, y que aporten bugs, a corregir o errores que todavía surjan.

Puedes ver los test que se están realizando en openQA en este enlace:

Diferentes test para diferentes arquitecturas, entornos de escritorio, etc… y no sólo para el proyecto de lanzamiento estable (que serían los nombrados como staging) sino también realiza los test para Tumbleweed.

Utilizando esta herramienta y consultándola podemos ver si ha tenido éxito, o si se ha producido algún error y podremos consultar los “logs” para tratar de solucionarlos o aprender para después poder aportar.

Desde esta herramienta también podremos descargarnos la ISO que se está testeando para instalarla en nuestro PC y testearla o probarla y ver qué se está cocinando.

Atención, esta semana se espera que se libere la primera versión de pruebas, o milestone, de forma oficial, para poder descargarla y empezar a probar esta renovada openSUSE!

Estate atento!! ;)




SUSE Linux Enterprise 11 Service Pack 4 was released today. It contains lots of software updates and features. For more information have a look at the release notes of our Server and Desktop version.

SUSE Linux Enterprise 11 SP4 templates

SUSE Studio supports the new SUSE Linux Enterprise release from day one. Just click on the Create appliance link after you log in and select the template you'd like to start with.

As always you can configure, build, testdrive and publish your appliance.

Configure SUSE Linux Enterprise 11 SP4 GNOME desktop

Testdriving SUSE Linux Enterprise 11 SP4 GNOME desktop


SUSE Linux Enterprise SP4 includes a lot of updates like new versions for openSSH and zypper. OpenSSH is constantly improving and gaining new and more secure cipher suites. The newest SUSE Linux Service pack ships with version 6.6p1 of openSSH which includes modern elliptic curve ciphers based on the elliptic curve Curve25519, resulting in public key types Ed25519. Also the new transport cipher "chacha20-poly1305@openssh.com" was added, using the ChaCha20 stream cipher and Poly1305 MAC developed by Dan Bernstein.

SUSE Linux Enterprise Server 11 SP4 updates also PostgreSQL to Version 9.4 which includes the new JSONB data type for PostgreSQL. With the new data type users no longer have to choose between relational and non-relational data stores: they can have both at the same time. JSONB supports fast lookups and simple expression search queries using Generalized Inverted Indexes (GIN). For more information have a look at the PostgreSQL Wiki.


As usual you can upgrade previous SUSE Linux Enterprise versions to the new Service Pack 4. Just go to the start tab of your appliance and click the Upgrade button at the top bar.

Different than previously, we implemented a step-wise-upgrade. That means, if you currently run on SLES11 SP3 and you want to upgrade to SLES12 you need two steps (SLES11 SP3 -> SLES11 SP4 -> SLES12) and we won't upgrade to the latest version automatically.

First step: Upgrade to SUSE Linux Enterprise 11 SP4

Second step: Upgrade to SUSE Linux Enterprise 12

In case you are not satisfied with the upgrade you can also rollback to your old appliance version. Just click on Undo upgrade at the bottom of the appliance start tab.

Rollback to SUSE Linux Enterprise 11 SP4

Happy building :)


pacote office

Foi lançado o LibreOffice 5.0 RC3, uma prévia da futura geração dessa suíte de escritório. Se você está querendo experimentar a próxima versão do LibreOffice no Linux antes de todos, veja como instalar.

Leia o restante do texto "Como instalar a próxima versão do LibreOffice no Linux: 5.0 RC3 "

Não está aparecendo algo?

Este post é melhor visualizado acessando direto da fonte. Para isso, clique nesse link: Como instalar a próxima versão do LibreOffice no Linux: 5.0 RC3.


Screenshot from 2015-07-15 15:11:21Developing Leap 42.1 is happening quickly and it was announced yesterday that the milestone was being built.The first milestone will hopefully be released this week. Leap is going through its testing and the importance of openQA (Quality Assurance) in this development process can not be understated.

openQA is used for testing an operating system, finding and files bugs and provides fully automated testing to ensure a distribution work correctly with clean functionality.

The wonders of openQA determine if a build is good and triggered errors allow testers and developers to see errors quickly and determine a cause.

Feel free to look at the test of the Leap milestone and use the hints below to navigate through openQA.

See what Richard Brown, openSUSE chairman, had to say about Leap and openQA on Reddit.

How To: Use openQA to find and file bugs

  • Click on one of the Red or Green dots that represent a finished test
  • You’re at the ‘Test Results’ page, this is where you can see the results of this openQA test. By default you’re taken to the ‘Default’ tab, which shows you each test module and all the screenshots taken during that test
  • Look at the screenshots, do they all make sense to you? Pay attention especially to any screenshots in rows that are marked Red/Failed..they’re probably bad and broken. Don’t always assume the Green ones are perfect, sometimes we make mistakes with our automated tests :)
  • File bugs accordingly, good bug reports should always have logs attached, luckily openQA includes many logs in it’s “Logs & Assets” Tab
  • Alternatively just skip step the last step and fix the problems right away

How To: Get the ISO used in the Tests

  • Click on one of the Red or Green dots that represent a finished test
  • You’re at the ‘Test Results’ page, this is where you can see the results of this openQA test. By default you’re taken to the ‘Default’ tab, which shows you each test module and all the screenshots taken during that test
  • Click the ‘Logs & Assets’ tab. This is where openQA keeps its logs for that test, as well as a Video recording, and it’s ‘Assets’ (aka ISO’s and HDD Disk Images)
  • Click on the ISO you want to download, in this case openSUSE-42.1-DVD-x86_64-Build0002-Media.iso
  • Congratulations, you now have the same ISO that openQA is using for testing openSUSE Leap 42.1

How To: See tests that are running

  • Click on any Yellow dots, these are the tests that are running
  • Congratulations, you’re now able to see the test running in openQA in Real Time


“Since when has the world of computer software design been about what people want? This is a simple question of evolution. The day is quickly coming when every knee will bow down to a silicon fist, and you will all beg your binary gods for mercy.” Bill Gates

For the sake of the users, let’s assume Bill was either wrong or (||) sarcastic.

Let’s say that we want to deliver Freedom and privacy to the users and that we want to be more effective at that. We plan to do that through quality software products and communication — that’s how we reach new users and keep them loving our software.

We can’t get away with half-assed software that more or less always shows clear signs of “in progress”, we need to think our software through from a users point of view and then build the software accordingly. We need to present our work at eye-level with commercial software vendors, it needs to be clear that we’re producing software fully reliable on a professional level. Our planning, implementation, quality and deployment processes need to be geared towards this same goal.

We need processes that allow us to deliver fixes to users within days, if not hours. Currently in most end-user scenario, it often takes months and perhaps even a dist-upgrade for a fix for a functional problem with our software.

The fun of all this lies in a more rewarding experience of making successful software, and learning to work together across the whole stack (including communication) to work together on this goal.

So, with these objectives in mind, where do we go from here? The answer is of course that we’re already underway, not at a very fast speed, but many of us have good understanding of many of the above structural goals and found solutions that work well.

Take tighter and more complete quality control, being at the heart of the implementation, as an example. We have adopted better review processes, more unit testing, more real-world testing and better feedback cycles with the community, especially the KDE Frameworks and Plasma stacks are well maintained and stabilized at high speeds. We can clearly say that the Frameworks idea worked very well technically but also from an organizational point of view, we have spread the maintainership over many more shoulders, and have been able to vastly simplify the deployment model (away from x.y.z releases). This works out because we test especially the Frameworks automatically and rather thoroughly through our CI systems. Within one year of Frameworks 5, our core software layer has settled into a nice pace of stable incremental development.

On the user interaction side, the past years have accompanied our interaction designers with visual artists. This is clearly visible when comparing Plasma 4 to Plasma 5. We have help from a very active group of visual designers now for about one and a half year, but have also adopted stricter visual guidelines in our

14 July, 2015

Michael Meeks: 2015-07-14 Tuesday.

21:00 UTCmember

  • Mail chew; calls, fixed a 'base' crasher nasty; built ESC agenda - chased slideshow horrors; wow the slideshow presenter code has just some amazing things in it - its own timer thread, queues of idle handlers and user event posting to poke other idle queueing of screen rendering bits, un-necessary UNO interfaces and much more.


Te propongo un reto para probar tu destreza con la línea de comandos de GNU/Linux ¿Te atreves?


El término “hackear” más que con la delincuencia informática, lo asocio a las ganas de aprender, al placer de retarte tu mismo y saber de qué eres capaz o de qué cosas puedes llegar a descubrir. Así que prepárate a “hackear” con la línea de comandos de GNU/Linux con este reto, en el que además puedes ganar un pequeño premio!

Desde la web de opensource.com he leido que en uno de sus artículos proponían un reto a sus lectores. Si no lo has leido te lo traigo por el blog, para ver si te animas. El reto tiene premio, pero da igual que ganes que no, o que estes leyendo esto fuera de plazo. Diviértete con el proceso de encontrar una solución al problema, diviértete hackeando, aprendiendo, investigando… ese es el buen hacker! ;)

El reto en cuestión lo puedes encontrar en el siguiente enlace:

Y consiste en lo siguiente. Tenemos un servidor web, y tenemos múltiples ataques de acceso al host via SSH. Mediante la utilidad Fail2Ban, conseguimos que esos atacantes no tengan acceso a nuestro servidor.

Y además podemos exportar, entre otros datos, las direcciones, IP de los atacantes junto con la horar y más. Y esto nos lo genera en este archivo que puedes descargar desde este enlace (son 6Mb de archivo)

El reto

El reto consiste en contar el número de correos electrónicos que se han enviado por cada dirección IP que ha intentado acceder al host mediante SSH, pero no con un script, sino que deberás hacerlo con varios comandos utilizando la opción de las “tuberías” o pipes en inglés, ya sabes este operador |

Es decir que debes crear un comando de una sola línea (eso sí como quieras de larga) utilizando las tuberías para entubar la salida de un comando a la entrada de otro y así conseguir el objetivo, que es contar cuantos accesos ha habido por cad IP. ¿está claro? ¿sencillo?

Ah! y como puntuación extra, que te dará más opciones de ganar, sería incluir el nombre del país de cada dirección IP.

Como digo, tienes más información en la web original donde se propone el reto. Tienes de margen hasta el día 31 de julio de 2015, pero siempre tendrás tiempo de intentarlo aunque ya se haya pasado la fecha. Lo divertido es retarse a uno mismo! Más información aqui:

Mis consejos (si me lo permites): que dividas el reto en partes afrontado cada parte por separado y viendo que te funcionan, después ver

<- Current blog entries