Přeskočit na hlavní obsah

jOpenSpace 2014

The best pure Czech not-only-Java conference jOpenSpace is over for this year and I'd like to write few words about it.

First of all, big thanks goes to Honza @novoj Novotný as the main organizer. This awesome event under his supervision become not only interesting from the technical PoV, but also very socializing (We were a nice Java family).

Next thanks goes to all sponsors, who made jOpenSpace comfortable and cheap as a hell:
  • Red Hat
  • Vendavo
  • MoroSystems
  • FG Forrest
  • Kerio
  • ABRA FlexiBee

Friday

We started the conference with a free day! The main program for Friday was a trip to Slovakia - to climb the Velka Javorina. Rainy weather was very demanding. Nevertheless, no one gave up! Hotel sauna was a nice end of a day and it was already fulfilled with interesting Java topics.

Saturday

Few of us started the day with a nice 9km run. The weather was beautiful and hills around colorful. First lightning talks started after the breakfast and continued during whole day. Hands-on labs started later in the afternoon. However, I didn't join the labs and I visited the holy city MyJava in Slovakia instead. Tasting Moravian wines in a wine cellar finished this long day.

Sunday

Few of us started the day with a hard 9km run. The night was too short. Lightning talks continued during the morning and we finished at lunch time. Finally we made a group photo and said goodbye to this unforgettable event.

The topics

You'll find most of the lightning talks (slides+audio) on jOpenSpace web during November. The area covered was very wide:
  • hardware - Quadcopters, Sparki robot, Raspbery PI
  • soft-skills & interesting books - Thinker's Toolkit
  • databases - MUMPS, Hazelcast
  • testing - SmartMeter, COllaborative Editor testing
  • tools - Code review with Atlassian, Future of Markdown
  • and many other interesting topics (E.g. the truth about drug manufacturers)
My presentation was about Java Security Manager and pro-grade library. The slides are online.
Few photos from my phone is in G+ album.

Komentáře

Populární příspěvky z tohoto blogu

Three ways to redirect HTTP requests to HTTPs in WildFly and JBoss EAP

WildFly application server (and JBoss EAP) supports several simple ways how to redirect the communication from plain HTTP to TLS protected HTTPs. This article presents 3 ways. Two are on the application level and the last one is on the server level valid for requests to all deployments. 1. Request confidentiality in the deployment descriptor The first way is based on the Servlet specification. You need to specify which URLs should be protected in the web.xml deployment descriptor. It's the same approach as the one used for specifying which URLs require authentication/authorization. Just instead of requesting an assigned role, you request a transport-guarantee . Sample content of the WEB-INF/web.xml <web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd" version="3.1

Simple TLS certificates in WildFly 18

It's just 2 weeks when WildFly 18 was released. It includes nice improvements in TLS certificates handling through ACME protocol (Automatic Certificate Management Environment), it greatly simplifies obtaining valid HTTPS certificates. There was already a support for the Let's Encrypt CA in WildFly 14 as Farah Juma described in her blog post last year. New WildFly version allows using other CA-s with ACME protocol support. It also adds new switch --lets-encrypt to interactive mode of security enable-ssl-http-server JBoss CLI commands. Let's try it. Before we jump on WildFly configuration, let's just mention the HTTPs can be used even in the default configuration and a self-signed certificate is generated on the fly. Nevertheless, it's not secure and you should not use it for any other purpose than testing. Use Let's Encrypt signed certificate for HTTPs application interface Start WildFly on a machine with the public IP address. Run it on the defaul

Weby ministerstev a jejich zabezpečení

Nedávno jsem hledal informaci na webu ministerstva zdravotnictví a zarazilo mě, že jsem nebyl automaticky přesměrován na zabezpečený protokol HTTPs. Napadlo mě podívat se, jak jsou na tom weby jednotlivých ministerstev s podporou tohoto protokolu. Rozdíly v zabezpečení jsou mezi weby velké a u některých ministerstev přímo překvapivé. Ministerstvo HTTPs Auto Redirect TLS 1.2 TLS 1.3 !RC4 !TLS 1 EV cert Doprava mdcr.cz Finance mfcr.cz Kultura mkcr.cz Místní rozvoj mmr.cz Obrana army.cz Práce a soc. věcí mpsv.cz Průmysl mpo.cz Spravedlnost justice.cz Školství msmt.cz Vnitra mvcr.cz Zahraničí mzv.cz Zdravotnictví mzcr.cz Zemědělství eagri.cz Životní prostředí mzp.cz Trocha teorie Proč HTTPs HTTPs znamená HTTP komunikaci přes spojení šifrované pomocí TLS protokolu (dříve SSL). Protokol HTTPs poskytuje nejen šifrování komunikace, ale t