Day 2 of the Embedded World – MES053
This is the 2nd episode of my 2017 visit to the Embedded World exhibition in Nuremberg. For the 1st part please refer to this episode.
I have captured these details on my 2nd day at the Embedded World 2017 in Nuremberg. I once again want to present smaller companies. Of course always with interesting, sometimes even exciting offers. I do not want to ignore the bigger ones, however it’s like looking for nuggets. You have to dig deeper and scrutinize into the inner details. I would be very happy if you find something in for you which is worthwhile to share again. Please do not hesitate and forward this episode to your friends and colleagues.
You are a more visual person? You’d like to see some details? Then look at my day#2 video and day #1 video at YouTube.
The Embedded World topics in this episode are:
- Cryptosource’s fleaTLS – a free TLS implementation designed for small footprint. Available royalty free in 3rd quarter 2017.
- Asaphus Vision presenting their Face Recognition Library. They support head- and eye-tracking and face-identification mainly, but not only, for self-driving vehicles.
- Timing suite for real-time systems by GLIWA. Supervise and collect timing- and stack-conditions on-the-fly in your embedded device.
- RTSoft supports you with experts for BSPs, drivers, middleware and APIs.
- HALCON is the machine vision solution by MVTec. They provide a versatile system supporting deep learning in visual data gathering.
- Grammatech’s binary code-analysis finally makes analysis of 3rd-party software possible, even you do not have the source-code available.
- My personal favorite of this day: Fraunhofer’s Equivert as new solution for dizziness therapy. An innovative idea presented as simple headphone with a lot of knowledge and experience inside. It gives dizzy patients the training they need to overcome their disease and step back into regular daily life.
- And more details and observations from this second day.
I am a wholehearted SW-engineer on my journey to create a business supporting newcomers, seniors, managers and leaders.
Dear Georg.
Thank you for your podcasts. Sounds nice, quite professional and ordered. This one is particularly interesting. I work within Automotive Embedded Systems and Control Engineering domain and will be glad to study new technologies, collaborate/cooperate efficiently towards concrete goals and accomplishments, enhance my current knowledge and skills as well as to acquire new skills.
The domain is very large and continuous study is essential to be efficient within the field.
Would you be so kind as to write / explain me if I have a web site which supports only HTTP connections, how can I make it working on HTTPS? How the migration to HTTPS is done usually today?
Kind Regards,
Dipl.-Ing. Pavel Mazniker
Hi Pavel,
thank you for your comment.
As you know changing from http to https usually means to introduce an additional encryption layer (TLS/SSL) into the communication between host (http://embeddedsuccess.com) and client. For TLS-connection setup you need to have a certificate. It’s quite easy to create your own host-certificate, but if you do not spend some money (regularly every year) your certificate will not be signed by a Certificate Authority (CA). Every web-browser has public keys of lots of official CA’s built in. If the browser requests a https-connection and gets a host-certificate signed by an official CA, the browser will continue with complaints. If you, due to cost reasons or similar, try to use your own self-signed host-certificate the browsers will yell like hell. And many visitors will avoid visiting the website for that reason.
Here https://letsencrypt.org/ enters the game. Aka roughly 2 years ago Let’s Encrypt came up to provide host-certificates for no money. These certs are only valid for establishing a TLS/SSL-connection, no signing, no encryption, nothing else. But they are free.
And many web-service providers (like mine, I do not take the effort to run my own root-server) provide nice interfaces to introduce Let’s Encrypt certificates. Now it should be possible for everybody to use https instead of http.
That’s fine if you start from scratch. If you already have a WordPress (or other) installation running you need to migrate from http to https. In WordPress there are tons of references to http://embeddedsuccess.com which have to be adapted. All manual work – no automation!
I followed https://www.webongo.de/wordpress-https-umstellen/ and https://dhue.de/wordpress-blog-von-http-auf-https-umstellen/. Sorry, all of them in German, but in the first you find all of the mandatory SQL-statements to also modify the underlying MySQL-database.
Migration lasted roughly 1 hour. Hereby taking the full-backup used up half of the time. Preparation time was a bit longer. Needed several hours to find appropriate details, give it a try on a test-domain and make some errors 🙂
For me the backup was important. I do use Updraft Plus for making my backups. It’s up-to-date, reliable and can also migrate WP-installation from one domain to another.
How migration from http to https is done nowadays in general I cannot reply. There are too many approaches, installations, web-servers and other impacts. But having a certificate available you should be able to find sufficient resources in the net.
BTW, have a look at the https-session opening using wireshark. It explains a lot what actually happens between both parties.
Cheers, Georg