Elvis Wiki - User contributions [en]

Proprietary Crypto Implementations

2020-02-17T22:23:21Z

Sprochazka: /* Summary */

== Summary ==

Proprietary Software is computer software that is not free and protected by mostly copyright or patent rights. This means it is normally not possible for an unauthorized user to have a look at the source code of the program or change it in any way. Companies or persons that want to use a proprietary software need to pay for it. On the other hand, there is free software also called open source software. It is free to use, and mostly also free to change up to a certain point. Normally open source software offers the possibility to look at and change the source code. A commonly known example of proprietary versus open source software are the operations systems windows and Linux.
Proprietary cryptographic software fulfilles the same fundamentals. A company must pay to use the encryption algorithm and the code remains hidden.
August Kerckhoffs born in 1835 in Denmark was a famous linguist and cryptographer who wrote the book “La Cryptographie Militaire”, a stepstone for the cryptography of the 19th century.
He is famous for the “Kerckhoffs´s principle, which states: “It [The cryprosystem] must not require secrecy and it can without disadvantage fall into the hands of the enemy” which means and is used in today’s terms that a cryptosystem should be secure even if everything about the system, except the key, is public knowledge. This stands in strong contrast to the concept “security through obscurity”. Security by obscurity goes with proprietary software in that case, that it relies on the secrecy of the inner workings of a system and the algorithm to keep the system secured.
There is a huge discussion if a cryptosystem is more secure if the mechanism is kept secret or if it is open to public and thus overviewed by many people and tested for weak spots. One argument states, that keeping the algorithm secret may improve short term security but for long term security its better if a system has been published and analyzed. The problem is, if the security of the system relies on the secrecy of the mechanisms, if get leaked or hacked, the whole mechanism is useless.

== History ==

Before 1969, software and services that went with the use of servers and computers where provided without extra charge. Source codes where available and everyone had the possibility to change and develop them and shared the results. That change when first IBM in 1969 started a new change leading to proprietary software. Companies started to keep source code secret to hinder other companies to steal and use it. Besides the source code, the fact that it was now possible to sell and change software on the base of microprocessors encouraged that change since the U.S. Copyright Act of 1976 extended the copyright law to protect binary programs as well. In February 1983 IBM took another step and established the “object-code-only”- Modell, which means the selling of a software without source code.

== Examples of exploited proprietary systems ==

'''Legic''' is a swiss supplier of access control systems that uses RFID (radio-frequency identification) with smartcards to secure building access and micropayment applications. The cards are used throughout Europe in clinical infrastructures, military installations, governmental departments, power plants, hospitals and airports. Beside the fact that they are used in high security facilities, it was exploited, that access cards could be cloned form distance. The algorithm was reversed engineered by a method called chip-slicing and it shows that there is no secret key involved, only a secret algorithm.

'''SimonsVoss G1''' is a locking system used for electronic locks whose cryptographic primitives and radio protocol where reverse engineered and discovered some implementation flaws which allow two ways to extract the master secret. There were also found some several weaknesses in the PRNG (Pseudo Random Number Generator).

'''DST''' stands for Digital Signature Transponder and is a cryptosystem used in vehicle immobilizer. The transponder was used for black-box analysis and it was shown, that is straightforward to recover the proprietary algorithms used in the cryptosystem. They then did an exhaustive search over the complete key space.

'''KeeLoq''' is used in Remote Keyless Entry (RKE) that are used for garage doors. The cipher was published in 2006 and the first proposed attack was a combination of linear attacks and correlation to recover the secret key.

'''ORXY''' is a stream cipher that is used to protect the wireless data services of the North American Telecommunications Industry Association (TIA). The cipher was first publicly reviewed in 1995 and it was shown that although the cipher should provide a computational complexity of 2 hoch 96 it only had 2 hoch 16. The same reviewers used a divide-and-conquer attack to reduce the computational complexity of the cipher. Since the cipher was insecure, they updated their specification and removed ONXY from the list of proposed cryptographic primitives.

'''A3, A8, COMP128''' is a proprietary algorithm for network authentication that instances the two proprietary algorithms A3 and A8. A3 is used to authenticate the mobile station to the network, A8 is used to generate the session key. COMP128 was copied and deployed by different service providers although it was just a reference example. The first attack to this was published in 1998 and later extended and generalized. There was also a hardware attack where just 8 chosen plaintext where used to retrieve a 128-bit key.

== Encryption techniques ==

'''CSS''' the content scramble system is a proprietary cryptosystem is used to store encrypted information on a DVD. The working was later published and there were several serious weaknesses and the 40-bit secret key can be recovered with a computational complexity of only 2 hoch 25 operations.

'''E0''' is a stream cipher algorithm used to encrypt the communication between Bluetooth devices. The first attack was published shortly after its introduction and is based on general correlation attack techniques. An article of 2013 identifies weaknesses that allows to recover the complete 128-bit secret key.

'''Skipjack''' depends on an 80-bit secret key and was designed by the National Security Agency (NSA). It was only used in a hardware device called the Clipper chip which was for example used by telecom providers to secure the confidentiality of telephone conversations. The requirement to use the chip was to share every used secret key with the US government. Although several minor weaknesses were identified the design of the proprietary cipher Skipjack does not seem to be very insecure.

'''RC4''' short for Rivest Cipher 4, is a proprietary stream cipher that was designed in 1987 and originally considered a trade-secret only available under a Non-Disclosure Agreement (NDA). The creator was Ron Rivest, the same who tool part in designing RSA. The design is more than 20 years old but still used in many protocols such as TLS, SSH or to encrypt network traffic in VPNs. When the code first appeared in the internet in 1994 it was anonymously posted and several weaknesses where identified. When used with a long random initializing internal state thou, it is still much more secure than most proprietary algorithms.

'''WEP''' the Wired Equivalent Privacy is a wireless network communication protocol that was officially introduced as part of the IEEE 802.11 in 1999. There were several weaknesses in the loading and scheduling of the secret key and after the first attack methodology was published, an experiment that demonstrated the feasibility of the proposed attack followed. As a result, the IEEE together with the Wi-Fi Alliance superseded by the Wi-Fi Protected Access (WPA).

== References ==

*https://www.zdnet.de/2130055/proprietaer-vs-open-source-eine-frage-der-sicherheit/
*https://www.heise.de/newsticker/meldung/FOSDEM-Kann-man-ohne-proprietaere-Software-leben-4296589.html
*https://www.security-insider.de/open-source-macht-hintertueren-transparent-a-612960/
* "The (in)security of proprietary cryptography"; Roel Verdult; 2015

[[Category:Documentation]]

Threat Modelling

2020-02-17T22:22:04Z

Proprietary Crypto Implementations

2020-02-13T09:20:16Z

Sprochazka:

== Summary ==

Proprietary Software is computer software that is not free and protected by mostly copyright or patent rights. This means it is normally not possible for an unauthorized user to have a look at the source code of the program or change it in any way. Companies or persons that want to use a proprietary software need to pay for it. On the other hand, there is free software also called open source software. It is free to use, and most are also free to change to a certain point. Normally open source software offers the possibility to look at and change the source code. A commonly known example of proprietary versus open source software are the operations systems windows and Linux.
Proprietary cryptographic software erfüllt the same fundamentals. A company must pay to use the encryption algorithm and the code remains hidden.
August Kerckhoffs born in 1835 in Denmark was a famous linguist and cryptographer who wrote the book “La Cryptographie Militaire”, a stepstone for the cryptography of the 19th century.
He is famous for the “Kerckhoffs´s principle, which states: “It [The cryprosystem] must not require secrecy and it can without disadvantage fall into the hands of the enemy” which means and is used in today’s terms that a cryptosystem should be secure even if everything about the system, except the key, is public knowledge. This stands in strong contrast to the concept “security through obscurity”. Security by obscurity goes with proprietary software in that case, that it relies on the secrecy of the inner workings of a system and the algorithm to keep the system secured.
There is a huge discussion if a cryptosystem is more secure if the mechanism is kept secret or if it is open to public and thus overviewed by many people and tested for weak spots. One argument states, that keeping the algorithm secret may improve short term security but for long term security its better if a system has been published and analyzed. The problem is, if the security of the system relies on the secrecy of the mechanisms, if get leaked or hacked, the whole mechanism is useless.

== History ==

Before 1969, software and services that went with the use of servers and computers where provided without extra charge. Source codes where available and everyone had the possibility to change and develop them and shared the results. That change when first IBM in 1969 started a new change leading to proprietary software. Companies started to keep source code secret to hinder other companies to steal and use it. Besides the source code, the fact that it was now possible to sell and change software on the base of microprocessors encouraged that change since the U.S. Copyright Act of 1976 extended the copyright law to protect binary programs as well. In February 1983 IBM took another step and established the “object-code-only”- Modell, which means the selling of a software without source code.

== Examples of exploited proprietary systems ==

'''Legic''' is a swiss supplier of access control systems that uses RFID (radio-frequency identification) with smartcards to secure building access and micropayment applications. The cards are used throughout Europe in clinical infrastructures, military installations, governmental departments, power plants, hospitals and airports. Beside the fact that they are used in high security facilities, it was exploited, that access cards could be cloned form distance. The algorithm was reversed engineered by a method called chip-slicing and it shows that there is no secret key involved, only a secret algorithm.

'''SimonsVoss G1''' is a locking system used for electronic locks whose cryptographic primitives and radio protocol where reverse engineered and discovered some implementation flaws which allow two ways to extract the master secret. There were also found some several weaknesses in the PRNG (Pseudo Random Number Generator).

'''DST''' stands for Digital Signature Transponder and is a cryptosystem used in vehicle immobilizer. The transponder was used for black-box analysis and it was shown, that is straightforward to recover the proprietary algorithms used in the cryptosystem. They then did an exhaustive search over the complete key space.

'''KeeLoq''' is used in Remote Keyless Entry (RKE) that are used for garage doors. The cipher was published in 2006 and the first proposed attack was a combination of linear attacks and correlation to recover the secret key.

'''ORXY''' is a stream cipher that is used to protect the wireless data services of the North American Telecommunications Industry Association (TIA). The cipher was first publicly reviewed in 1995 and it was shown that although the cipher should provide a computational complexity of 2 hoch 96 it only had 2 hoch 16. The same reviewers used a divide-and-conquer attack to reduce the computational complexity of the cipher. Since the cipher was insecure, they updated their specification and removed ONXY from the list of proposed cryptographic primitives.

'''A3, A8, COMP128''' is a proprietary algorithm for network authentication that instances the two proprietary algorithms A3 and A8. A3 is used to authenticate the mobile station to the network, A8 is used to generate the session key. COMP128 was copied and deployed by different service providers although it was just a reference example. The first attack to this was published in 1998 and later extended and generalized. There was also a hardware attack where just 8 chosen plaintext where used to retrieve a 128-bit key.

== Encryption techniques ==

'''CSS''' the content scramble system is a proprietary cryptosystem is used to store encrypted information on a DVD. The working was later published and there were several serious weaknesses and the 40-bit secret key can be recovered with a computational complexity of only 2 hoch 25 operations.

'''E0''' is a stream cipher algorithm used to encrypt the communication between Bluetooth devices. The first attack was published shortly after its introduction and is based on general correlation attack techniques. An article of 2013 identifies weaknesses that allows to recover the complete 128-bit secret key.

'''Skipjack''' depends on an 80-bit secret key and was designed by the National Security Agency (NSA). It was only used in a hardware device called the Clipper chip which was for example used by telecom providers to secure the confidentiality of telephone conversations. The requirement to use the chip was to share every used secret key with the US government. Although several minor weaknesses were identified the design of the proprietary cipher Skipjack does not seem to be very insecure.

'''RC4''' short for Rivest Cipher 4, is a proprietary stream cipher that was designed in 1987 and originally considered a trade-secret only available under a Non-Disclosure Agreement (NDA). The creator was Ron Rivest, the same who tool part in designing RSA. The design is more than 20 years old but still used in many protocols such as TLS, SSH or to encrypt network traffic in VPNs. When the code first appeared in the internet in 1994 it was anonymously posted and several weaknesses where identified. When used with a long random initializing internal state thou, it is still much more secure than most proprietary algorithms.

'''WEP''' the Wired Equivalent Privacy is a wireless network communication protocol that was officially introduced as part of the IEEE 802.11 in 1999. There were several weaknesses in the loading and scheduling of the secret key and after the first attack methodology was published, an experiment that demonstrated the feasibility of the proposed attack followed. As a result, the IEEE together with the Wi-Fi Alliance superseded by the Wi-Fi Protected Access (WPA).

== References ==

*https://www.zdnet.de/2130055/proprietaer-vs-open-source-eine-frage-der-sicherheit/
*https://www.heise.de/newsticker/meldung/FOSDEM-Kann-man-ohne-proprietaere-Software-leben-4296589.html
*https://www.security-insider.de/open-source-macht-hintertueren-transparent-a-612960/
* "The (in)security of proprietary cryptography"; Roel Verdult; 2015

[[Category:Documentation]]

Proprietary Crypto Implementations

2020-02-13T09:17:37Z

Sprochazka: Created page with "== Summary == Proprietary Software is computer software that is not free and protected by mostly copyright or patent rights. This means it is normally not possible for an un..."

== Summary ==

Proprietary Software is computer software that is not free and protected by mostly copyright or patent rights. This means it is normally not possible for an unauthorized user to have a look at the source code of the program or change it in any way. Companies or persons that want to use a proprietary software need to pay for it. On the other hand, there is free software also called open source software. It is free to use, and most are also free to change to a certain point. Normally open source software offers the possibility to look at and change the source code. A commonly known example of proprietary versus open source software are the operations systems windows and Linux.
Proprietary cryptographic software erfüllt the same fundamentals. A company must pay to use the encryption algorithm and the code remains hidden.
August Kerckhoffs born in 1835 in Denmark was a famous linguist and cryptographer who wrote the book “La Cryptographie Militaire”, a stepstone for the cryptography of the 19th century.
He is famous for the “Kerckhoffs´s principle, which states: “It [The cryprosystem] must not require secrecy and it can without disadvantage fall into the hands of the enemy” which means and is used in today’s terms that a cryptosystem should be secure even if everything about the system, except the key, is public knowledge. This stands in strong contrast to the concept “security through obscurity”. Security by obscurity goes with proprietary software in that case, that it relies on the secrecy of the inner workings of a system and the algorithm to keep the system secured.
There is a huge discussion if a cryptosystem is more secure if the mechanism is kept secret or if it is open to public and thus overviewed by many people and tested for weak spots. One argument states, that keeping the algorithm secret may improve short term security but for long term security its better if a system has been published and analyzed. The problem is, if the security of the system relies on the secrecy of the mechanisms, if get leaked or hacked, the whole mechanism is useless.

== History ==

Before 1969, software and services that went with the use of servers and computers where provided without extra charge. Source codes where available and everyone had the possibility to change and develop them and shared the results. That change when first IBM in 1969 started a new change leading to proprietary software. Companies started to keep source code secret to hinder other companies to steal and use it. Besides the source code, the fact that it was now possible to sell and change software on the base of microprocessors encouraged that change since the U.S. Copyright Act of 1976 extended the copyright law to protect binary programs as well. In February 1983 IBM took another step and established the “object-code-only”- Modell, which means the selling of a software without source code.

== Examples of exploited proprietary systems ==

'''Legic''' is a swiss supplier of access control systems that uses RFID (radio-frequency identification) with smartcards to secure building access and micropayment applications. The cards are used throughout Europe in clinical infrastructures, military installations, governmental departments, power plants, hospitals and airports. Beside the fact that they are used in high security facilities, it was exploited, that access cards could be cloned form distance. The algorithm was reversed engineered by a method called chip-slicing and it shows that there is no secret key involved, only a secret algorithm.

'''SimonsVoss G1''' is a locking system used for electronic locks whose cryptographic primitives and radio protocol where reverse engineered and discovered some implementation flaws which allow two ways to extract the master secret. There were also found some several weaknesses in the PRNG (Pseudo Random Number Generator).

'''DST''' stands for Digital Signature Transponder and is a cryptosystem used in vehicle immobilizer. The transponder was used for black-box analysis and it was shown, that is straightforward to recover the proprietary algorithms used in the cryptosystem. They then did an exhaustive search over the complete key space.

'''KeeLoq''' is used in Remote Keyless Entry (RKE) that are used for garage doors. The cipher was published in 2006 and the first proposed attack was a combination of linear attacks and correlation to recover the secret key.

'''ORXY''' is a stream cipher that is used to protect the wireless data services of the North American Telecommunications Industry Association (TIA). The cipher was first publicly reviewed in 1995 and it was shown that although the cipher should provide a computational complexity of 2 hoch 96 it only had 2 hoch 16. The same reviewers used a divide-and-conquer attack to reduce the computational complexity of the cipher. Since the cipher was insecure, they updated their specification and removed ONXY from the list of proposed cryptographic primitives.

'''A3, A8, COMP128''' is a proprietary algorithm for network authentication that instances the two proprietary algorithms A3 and A8. A3 is used to authenticate the mobile station to the network, A8 is used to generate the session key. COMP128 was copied and deployed by different service providers although it was just a reference example. The first attack to this was published in 1998 and later extended and generalized. There was also a hardware attack where just 8 chosen plaintext where used to retrieve a 128-bit key.

== Encryption techniques ==

'''CSS''' the content scramble system is a proprietary cryptosystem is used to store encrypted information on a DVD. The working was later published and there were several serious weaknesses and the 40-bit secret key can be recovered with a computational complexity of only 2 hoch 25 operations.

'''E0''' is a stream cipher algorithm used to encrypt the communication between Bluetooth devices. The first attack was published shortly after its introduction and is based on general correlation attack techniques. An article of 2013 identifies weaknesses that allows to recover the complete 128-bit secret key.

'''Skipjack''' depends on an 80-bit secret key and was designed by the National Security Agency (NSA). It was only used in a hardware device called the Clipper chip which was for example used by telecom providers to secure the confidentiality of telephone conversations. The requirement to use the chip was to share every used secret key with the US government. Although several minor weaknesses were identified the design of the proprietary cipher Skipjack does not seem to be very insecure.

'''RC4''' short for Rivest Cipher 4, is a proprietary stream cipher that was designed in 1987 and originally considered a trade-secret only available under a Non-Disclosure Agreement (NDA). The creator was Ron Rivest, the same who tool part in designing RSA. The design is more than 20 years old but still used in many protocols such as TLS, SSH or to encrypt network traffic in VPNs. When the code first appeared in the internet in 1994 it was anonymously posted and several weaknesses where identified. When used with a long random initializing internal state thou, it is still much more secure than most proprietary algorithms.

'''WEP''' the Wired Equivalent Privacy is a wireless network communication protocol that was officially introduced as part of the IEEE 802.11 in 1999. There were several weaknesses in the loading and scheduling of the secret key and after the first attack methodology was published, an experiment that demonstrated the feasibility of the proposed attack followed. As a result, the IEEE together with the Wi-Fi Alliance superseded by the Wi-Fi Protected Access (WPA).

== References ==

*https://www.zdnet.de/2130055/proprietaer-vs-open-source-eine-frage-der-sicherheit/
*https://www.heise.de/newsticker/meldung/FOSDEM-Kann-man-ohne-proprietaere-Software-leben-4296589.html
*https://www.security-insider.de/open-source-macht-hintertueren-transparent-a-612960/
* "The (in)security of proprietary cryptography"; Roel Verdult; 2015

[[Category:Documentation]]

WebAuthn

2020-01-30T16:15:01Z

Sprochazka:

[[File:webauthn_logo.PNG|500px|thumb|WebAuthn logo]]

== Summary ==

WebAuthn is an Application created by the FIDO (Fast Identity Online) alliance and the W3C (World Wide Web Consortium) to offer the possibility of passwordless authentication online. The latest recommendation is of March 2019 published by the W3C. Instead WebAuthn work either with the inbuild Authenticator of the device, such as fingerprint sensor or facial recognition, or with an extern media like an USB Stick for verification.

== Goal ==
Its purpose is to offer a more secure and easy possibility to log into your online accounts without storing or remembering huge amounts of passwords to prevent the possibility of passwords getting leaked or forgotten.

== Functionality ==
WebAuthn works with two ceremonies:

'''The Registration:'''
The Registration involves a Relying Party, the server that hosts the Website, and the user client that must host at least one authenticator. To register, the user has to navigate to the website where he wishes to use Web Authentication and sign in using the method that was used to this point, which means for example a password. After that it is to choose to register this site from now an using Web Authentication, which leads to the request to submit the configures authorization gesture. When the provided gesture is accepted, the registrations is complete.

'''The Authentication:'''
For the user, the authentication using the Web Authenticator works seemingly as a normal login with just the difference that instead of typing a password to verify its identity, the user uses the same Authentication gesture that he used to register to the site.

== Authenticators ==

The authenticator is necessary to create a public key credential and to register with a Relying Party.
There are two types of Authenticators:

'''Platform Authenticator:'''

The platform Authenticator is implemented on a device thus using a client device-specific transport called platform attachment. This authenticator is usually not removable from the device and the credential created with it is called platform credential.

'''Roaming Authenticator:'''

A roaming Authenticator is attached using cross-platform transport and is thus called a cross-platform attachment. They are removable from the device, such as an USB key fob, and the generated credential is called roaming credential

== Example ==

[[File:webauthn_1.PNG|400px]]

First you have to navigate to the Website where you want to change the default login to WebAuthn, in this case it is the test website of WebAuthn, the link is provided below, so we create a new user and pick the option PMT for we are going to use the inbuilt fingerprint sensor of the laptop to verify our identity.

[[File:webauthn2.PNG|300px]]

The security feature now asks us to verify the identity with the same Authenticatior you want to use every time you log into the website. The choice will be stored with your ID and used every time you login.

[[File:webauthn3.PNG|600px]]

The login was a scucess and now we are able to login just using our fingerprint.

[[File:webauthn4.PNG|300px]]

You are ask to provide the same authentication which you used to login, in this case the fingerprint.

[[File:webauthn5.PNG|800px]]

If everything goes well, you are now logged in just using a fingerprint sensor!

----
Try it yourself if you want to!
[https://webauthn.io/ WebAuthn Demo]

== References ==

* https://webauthn.guide/#about-webauthn
* https://www.w3.org/TR/webauthn/#intro

[[Category:Documentation]]

2020-01-30T15:20:03Z

Sprochazka: /* Functionality */

WebAuthn

2020-01-30T15:19:51Z

Sprochazka:

WebAuthn

2020-01-30T15:18:06Z

Sprochazka:

WebAuthn

2020-01-30T15:17:36Z

Sprochazka:

WebAuthn

2020-01-30T07:00:37Z

Sprochazka: /* Used Hardware */

== Summary ==

== Goal ==

== Used Software ==

== Authenticators ==

== Titel ==

== References ==

* https://www.openhab.org/
* https://www.wireshark.org/

[[Category:Documentation]]

WebAuthn

2020-01-13T14:05:39Z

Sprochazka: Created page with "== Summary == == Goal == == Used Software == == Used Hardware == == Titel == == References == * https://www.openhab.org/ * https://www.wireshark.org/ Categor..."

== Summary ==

== Goal ==

== Used Software ==

== Used Hardware ==

== Titel ==

== References ==

* https://www.openhab.org/
* https://www.wireshark.org/

[[Category:Documentation]]

Pass-the-Hash (PtH)

2020-01-13T14:03:49Z

Sprochazka: Removed redirect to Brute-Force with NMAP

== Summary ==

== Goal ==

== Used Software ==

== Used Hardware ==

== Titel ==

== References ==

* https://www.openhab.org/
* https://www.wireshark.org/

[[Category:Documentation]]

File:VergleichOpenHAB ioBroker.jpg

2019-07-16T18:33:57Z

Sprochazka: Sprochazka uploaded a new version of File:VergleichOpenHAB ioBroker.jpg

Install OpenHAB

2019-07-16T18:31:49Z

Sprochazka: /* Compared to ioBroker */

== Summary ==

This documentation describes how to install and configure OpenHAB 2 on a Windows computer.

== Requirements ==

* Operating system: Windows
* Java JDK 8

== Description ==

=== Step 1: Set system variable Java 8 ===

At first, we have to make sure that we are using Java 8 because OpenHub will not work with Java 9 or 10.

Navigate to:
Control Panel > System > Advanced System Settings > Environment Variables > System Variables

Add here a System Environment Variable with the Name JAVA_HOME and fill in the path to your Java 8 JDK.

You can find how to install Java on the website of oracle or you click the link below.
* https://docs.oracle.com/javase/10/install/installation-jdk-and-jre-microsoft-windows-platforms.htm#JSJIG-GUID-A7E27B90-A28D-4237-9383-A58B416071CA

=== Step 2: Install OpenHAB 2 ===
To get started with OpenHub, first visit the official site https://www.openhab.org/ and klick on the
get started Button.

It leads to the very first and important site of the programs documentation, the welcome site.
On this site you learn everything that is essential to know for this program and it will lead you through a very detailed step by step manual on how to install and use the program.

OpenHub runs on most popular platforms such as Linux, Windows and MacOS, we installed it on Windows.
Under the section “Installation Overview” https://www.openhab.org/docs/installation/
that gives platform recommendations and asks you to choose help for the desired system.

You can download the latest Windows Stable version of as a zip-file from the download page of openHAB:
* https://www.openhab.org/download/

We unzip the file in the chosen directory and start the server by executing the script start.bat
which will open an runtime window showing you the following Window:

[[File:OpenHabStartWindow.png]]

After that you navigate your browser to http://localhost:8080 which will automatically direct you to the OpenHub package selection page.

Here you can decide between four different packages:

[[File:OpenHabPackages.PNG]]

We chose the Standard setup for it provides all necessary features for our tasks.

After that, the installation is complete.

The online documentation is very detailed and nearly every error that might have been made is covered.

During our installation process no problems occurred.

The section “While you are getting started” will lead you to a “new user tutorial” which will help with the use of the program. You can also reach the tutorial with the following link:
* https://www.openhab.org/docs/tutorial/

=== Step 3: Binding ===

A crucial step when using a Smarthome software is the binding of the devices we want to control.
We decided to use a PHILIPS HUE white and color ambiance single bulb and a PHILIPS HUE motion sensor.

No matter which product you use it is important to have a bridge to connect your devices with your network.
We use an original PHILIPS HUE Bridge which we connected directly to our router via a Lan cable.

After installing the program and choosing the setup, we enter the PAPER UI and start the configuration of our bindings:
* https://www.openhab.org/docs/tutorial/configuration.html
The first thing to do is to install the corresponding binding for the device you like to control, in our case, the HUE binding.

So, we navigate to the point Add-ons > bindings and search for HUE, then hit the install button.

[[File:Add-ons.png]]

After that, we enter the “Inbox” to search for new devices by taping the “SEARCH FOR THINGS” button.
This will automatically show all active devices nearby.

If the device you are looking for you can add it manually by hitting “ADD MANUALLY”.
There you must add which device it is, to which bridge it is connected and the device ID.

The next point to do is to navigate to the point “configuration” > “system” and activate the “Simple Mode” under the point “Item linking”.

Now when you navigate to “configuration” > “things” you can see the “thing” related to your device which should show the status “online”.
After you clicked on your thing you can see the so called “channels”. Those are the functions that you item provides.

The last thing to do is linking the channels together with the item and snice we activated the simple mode, we simply click on the corresponding blue radio button left to the channel.

At last we navigate to the “control” page where we can see our new Item and use its functions.

[[File:Control.png]]

If you want to change anything about your Item, you go to the “Configuration” > “thing” page and click the pen icon.

There you can edit the name, chose a location (eg. living room etc.) and change binding related options like the IP address, the timeout, the refresh interval etc.

== Compared to ioBroker ==
[[File:VergleichOpenHAB ioBroker.jpg]]

== Used Hardware ==

* [[Philips Hue Bridge 2.0, Gateway]]
* [[Philips Hue White and Color Ambiance Single LED-Bulb E27 10W]]

== References ==

* https://openhab.org
* https://www.oracle.com/technetwork/java/javase/downloads/index.html
* https://docs.oracle.com/javase/10/install/installation-jdk-and-jre-microsoft-windows-platforms.htm#JSJIG-GUID-A7E27B90-A28D-4237-9383-A58B416071CA
* https://www.iobroker.net/

[[Category:Documentation]]

File:VergleichOpenHAB ioBroker.jpg

2019-07-16T18:26:58Z

Sprochazka:

OpenHAB - Man in the middle attack

2019-07-16T18:21:30Z

Sprochazka: /* Used Software */

== Summary ==

The results of our Man in the middle attack on OpenHAB.

== Goal ==

To perform a Man in the Middle attack via arp spoofing between a Hue bridge and a computer and capture the traffic send between OpenHab and the bridge to control a wireless light.

== Used Software ==

* Cain & Able https://www.chip.de/downloads/Cain-Abel_17043501.html
* OpenHAB https://www.openhab.org/
You can find our documentation about installing OpenHAB here [[Install OpenHAB]].
* Wireshark https://www.wireshark.org/

== Used Hardware ==

[[Philips Hue White and Color Ambiance Single LED-Bulb E27 10W]]

[[Philips Hue Bridge 2.0, Gateway]]

== Capturing traffic before the Attack ==

Before we performed the Man in the Middle attack, we performed a wireshark capturing directly on the host camputer which was using OpenHab.

As one can see, we can see in plain text the numbers for color, saturation and brightness. And we see every PUT message send whenever we change something.

[[File:Traffic_before_attack.png]]

== Using Cain & Able ==

The first thing to do when using Cain and Able is to use the sniffing function the determine which hosts in the network are available for sniffing and MitM attacks.

To start the process, we click on the second button from the right in the top left corner.

[[File:Cain-Able-Sniffer.png]]

The output is a list of available hosts in the network, in our case including host 192.168.0.38 on which OpenHab is running and 192.168.0.150 which is our Philips Hue bridge.

[[File:Cain-Able-Sniffer_Output.png]]

The next step is to select with which participants we want to perform out attack, for that, we select the ARP menu at the bottom left part of our program and then tap on the big blue Plus symbol.

[[File:Cain-Able-ARP.png]]

In the newly opened window we can choose out to victims on which we will perform the arp spoofing so we chose out host computer and our bridge.

[[File:Cain-Able-Victims.png]]

The last step is to just press the Radioactive button to start the poisoning.

If we take a look now at the arp table of our host computer, we can see that our bridge and the attacker computer have different IP addresses,
but the same MAC address, namly the address of our attacking PC getting every message that is sent over our computer.

[[File:Cain-Able-Radioactive.png]]

Thus we can now also use Wireshark to capture the traffic between host computer and Hue Bridge.

== Capturing traffic during the attack ==

We can now capture the traffic send between host PC and Hue bridge on our MitM camputer and beside the fact that every package contains a timestamp which allows a precise reconstruction and collection of data when and how the lamp is used, we can as well see the status of the lamp such as brightness and saturation as well as changes displayed in plain text.

[[File:Cain-Able-Wireshark-1.png]]
[[File:Cain-Able-Wireshark-2.png]]

== API Interface ==

Another thing we can see during performing our MitM attack is the request api URI of our bridge.

[[File:URI-Request-API.png]]

We can use that URI with just a slight change, adding just lights instead of lights 1/state, to display a huge chunck of information about every light connected to our bridge.

[[File:watch-changes-without-spoofing.png]]

If this site is open, it is possible even without a running arp spoofing to watch the changes in the lamp's settings.

== References ==

* https://www.openhab.org/
* https://www.wireshark.org/

[[Category:Documentation]]

OpenHAB - Man in the middle attack

2019-07-16T18:21:18Z

Sprochazka: /* Used Software */

== Summary ==

The results of our Man in the middle attack on OpenHAB.

== Goal ==

To perform a Man in the Middle attack via arp spoofing between a Hue bridge and a computer and capture the traffic send between OpenHab and the bridge to control a wireless light.

== Used Software ==

* Cain & Able https://www.chip.de/downloads/Cain-Abel_17043501.html
* OpenHAB https://www.openhab.org/
You can find our documentation about installing OpenHAB here [[Install OpenHAB]].

* Wireshark https://www.wireshark.org/

== Used Hardware ==

[[Philips Hue White and Color Ambiance Single LED-Bulb E27 10W]]

[[Philips Hue Bridge 2.0, Gateway]]

== Capturing traffic before the Attack ==

Before we performed the Man in the Middle attack, we performed a wireshark capturing directly on the host camputer which was using OpenHab.

As one can see, we can see in plain text the numbers for color, saturation and brightness. And we see every PUT message send whenever we change something.

[[File:Traffic_before_attack.png]]

== Using Cain & Able ==

The first thing to do when using Cain and Able is to use the sniffing function the determine which hosts in the network are available for sniffing and MitM attacks.

To start the process, we click on the second button from the right in the top left corner.

[[File:Cain-Able-Sniffer.png]]

The output is a list of available hosts in the network, in our case including host 192.168.0.38 on which OpenHab is running and 192.168.0.150 which is our Philips Hue bridge.

[[File:Cain-Able-Sniffer_Output.png]]

The next step is to select with which participants we want to perform out attack, for that, we select the ARP menu at the bottom left part of our program and then tap on the big blue Plus symbol.

[[File:Cain-Able-ARP.png]]

In the newly opened window we can choose out to victims on which we will perform the arp spoofing so we chose out host computer and our bridge.

[[File:Cain-Able-Victims.png]]

The last step is to just press the Radioactive button to start the poisoning.

If we take a look now at the arp table of our host computer, we can see that our bridge and the attacker computer have different IP addresses,
but the same MAC address, namly the address of our attacking PC getting every message that is sent over our computer.

[[File:Cain-Able-Radioactive.png]]

Thus we can now also use Wireshark to capture the traffic between host computer and Hue Bridge.

== Capturing traffic during the attack ==

We can now capture the traffic send between host PC and Hue bridge on our MitM camputer and beside the fact that every package contains a timestamp which allows a precise reconstruction and collection of data when and how the lamp is used, we can as well see the status of the lamp such as brightness and saturation as well as changes displayed in plain text.

[[File:Cain-Able-Wireshark-1.png]]
[[File:Cain-Able-Wireshark-2.png]]

== API Interface ==

Another thing we can see during performing our MitM attack is the request api URI of our bridge.

[[File:URI-Request-API.png]]

We can use that URI with just a slight change, adding just lights instead of lights 1/state, to display a huge chunck of information about every light connected to our bridge.

[[File:watch-changes-without-spoofing.png]]

If this site is open, it is possible even without a running arp spoofing to watch the changes in the lamp's settings.

== References ==

* https://www.openhab.org/
* https://www.wireshark.org/

[[Category:Documentation]]

OpenHAB - Man in the middle attack

2019-07-16T18:20:54Z

Sprochazka: /* Used Software */

OpenHAB - Man in the middle attack

2019-07-16T18:20:42Z

Sprochazka: /* Used Software */

Install OpenHAB

2019-07-16T18:18:57Z

Sprochazka: /* Used Hardware */

== Summary ==

This documentation describes how to install and configure OpenHAB 2 on a Windows computer.

== Requirements ==

* Operating system: Windows
* Java JDK 8

== Description ==

=== Step 1: Set system variable Java 8 ===

At first, we have to make sure that we are using Java 8 because OpenHub will not work with Java 9 or 10.

Navigate to:
Control Panel > System > Advanced System Settings > Environment Variables > System Variables

Add here a System Environment Variable with the Name JAVA_HOME and fill in the path to your Java 8 JDK.

You can find how to install Java on the website of oracle or you click the link below.
* https://docs.oracle.com/javase/10/install/installation-jdk-and-jre-microsoft-windows-platforms.htm#JSJIG-GUID-A7E27B90-A28D-4237-9383-A58B416071CA

=== Step 2: Install OpenHAB 2 ===
To get started with OpenHub, first visit the official site https://www.openhab.org/ and klick on the
get started Button.

It leads to the very first and important site of the programs documentation, the welcome site.
On this site you learn everything that is essential to know for this program and it will lead you through a very detailed step by step manual on how to install and use the program.

OpenHub runs on most popular platforms such as Linux, Windows and MacOS, we installed it on Windows.
Under the section “Installation Overview” https://www.openhab.org/docs/installation/
that gives platform recommendations and asks you to choose help for the desired system.

You can download the latest Windows Stable version of as a zip-file from the download page of openHAB:
* https://www.openhab.org/download/

We unzip the file in the chosen directory and start the server by executing the script start.bat
which will open an runtime window showing you the following Window:

[[File:OpenHabStartWindow.png]]

After that you navigate your browser to http://localhost:8080 which will automatically direct you to the OpenHub package selection page.

Here you can decide between four different packages:

[[File:OpenHabPackages.PNG]]

We chose the Standard setup for it provides all necessary features for our tasks.

After that, the installation is complete.

The online documentation is very detailed and nearly every error that might have been made is covered.

During our installation process no problems occurred.

The section “While you are getting started” will lead you to a “new user tutorial” which will help with the use of the program. You can also reach the tutorial with the following link:
* https://www.openhab.org/docs/tutorial/

=== Step 3: Binding ===

A crucial step when using a Smarthome software is the binding of the devices we want to control.
We decided to use a PHILIPS HUE white and color ambiance single bulb and a PHILIPS HUE motion sensor.

No matter which product you use it is important to have a bridge to connect your devices with your network.
We use an original PHILIPS HUE Bridge which we connected directly to our router via a Lan cable.

After installing the program and choosing the setup, we enter the PAPER UI and start the configuration of our bindings:
* https://www.openhab.org/docs/tutorial/configuration.html
The first thing to do is to install the corresponding binding for the device you like to control, in our case, the HUE binding.

So, we navigate to the point Add-ons > bindings and search for HUE, then hit the install button.

[[File:Add-ons.png]]

After that, we enter the “Inbox” to search for new devices by taping the “SEARCH FOR THINGS” button.
This will automatically show all active devices nearby.

If the device you are looking for you can add it manually by hitting “ADD MANUALLY”.
There you must add which device it is, to which bridge it is connected and the device ID.

The next point to do is to navigate to the point “configuration” > “system” and activate the “Simple Mode” under the point “Item linking”.

Now when you navigate to “configuration” > “things” you can see the “thing” related to your device which should show the status “online”.
After you clicked on your thing you can see the so called “channels”. Those are the functions that you item provides.

The last thing to do is linking the channels together with the item and snice we activated the simple mode, we simply click on the corresponding blue radio button left to the channel.

At last we navigate to the “control” page where we can see our new Item and use its functions.

[[File:Control.png]]

If you want to change anything about your Item, you go to the “Configuration” > “thing” page and click the pen icon.

There you can edit the name, chose a location (eg. living room etc.) and change binding related options like the IP address, the timeout, the refresh interval etc.

== Used Hardware ==

* [[Philips Hue Bridge 2.0, Gateway]]
* [[Philips Hue White and Color Ambiance Single LED-Bulb E27 10W]]

== References ==

* https://openhab.org
* https://www.oracle.com/technetwork/java/javase/downloads/index.html
* https://docs.oracle.com/javase/10/install/installation-jdk-and-jre-microsoft-windows-platforms.htm#JSJIG-GUID-A7E27B90-A28D-4237-9383-A58B416071CA

[[Category:Documentation]]

Install OpenHAB

2019-07-16T18:18:10Z

Sprochazka: /* Used Hardware */

== Summary ==

This documentation describes how to install and configure OpenHAB 2 on a Windows computer.

== Requirements ==

* Operating system: Windows
* Java JDK 8

== Description ==

=== Step 1: Set system variable Java 8 ===

At first, we have to make sure that we are using Java 8 because OpenHub will not work with Java 9 or 10.

Navigate to:
Control Panel > System > Advanced System Settings > Environment Variables > System Variables

Add here a System Environment Variable with the Name JAVA_HOME and fill in the path to your Java 8 JDK.

You can find how to install Java on the website of oracle or you click the link below.
* https://docs.oracle.com/javase/10/install/installation-jdk-and-jre-microsoft-windows-platforms.htm#JSJIG-GUID-A7E27B90-A28D-4237-9383-A58B416071CA

=== Step 2: Install OpenHAB 2 ===
To get started with OpenHub, first visit the official site https://www.openhab.org/ and klick on the
get started Button.

It leads to the very first and important site of the programs documentation, the welcome site.
On this site you learn everything that is essential to know for this program and it will lead you through a very detailed step by step manual on how to install and use the program.

OpenHub runs on most popular platforms such as Linux, Windows and MacOS, we installed it on Windows.
Under the section “Installation Overview” https://www.openhab.org/docs/installation/
that gives platform recommendations and asks you to choose help for the desired system.

You can download the latest Windows Stable version of as a zip-file from the download page of openHAB:
* https://www.openhab.org/download/

We unzip the file in the chosen directory and start the server by executing the script start.bat
which will open an runtime window showing you the following Window:

[[File:OpenHabStartWindow.png]]

After that you navigate your browser to http://localhost:8080 which will automatically direct you to the OpenHub package selection page.

Here you can decide between four different packages:

[[File:OpenHabPackages.PNG]]

We chose the Standard setup for it provides all necessary features for our tasks.

After that, the installation is complete.

The online documentation is very detailed and nearly every error that might have been made is covered.

During our installation process no problems occurred.

The section “While you are getting started” will lead you to a “new user tutorial” which will help with the use of the program. You can also reach the tutorial with the following link:
* https://www.openhab.org/docs/tutorial/

=== Step 3: Binding ===

A crucial step when using a Smarthome software is the binding of the devices we want to control.
We decided to use a PHILIPS HUE white and color ambiance single bulb and a PHILIPS HUE motion sensor.

No matter which product you use it is important to have a bridge to connect your devices with your network.
We use an original PHILIPS HUE Bridge which we connected directly to our router via a Lan cable.

After installing the program and choosing the setup, we enter the PAPER UI and start the configuration of our bindings:
* https://www.openhab.org/docs/tutorial/configuration.html
The first thing to do is to install the corresponding binding for the device you like to control, in our case, the HUE binding.

So, we navigate to the point Add-ons > bindings and search for HUE, then hit the install button.

[[File:Add-ons.png]]

After that, we enter the “Inbox” to search for new devices by taping the “SEARCH FOR THINGS” button.
This will automatically show all active devices nearby.

If the device you are looking for you can add it manually by hitting “ADD MANUALLY”.
There you must add which device it is, to which bridge it is connected and the device ID.

The next point to do is to navigate to the point “configuration” > “system” and activate the “Simple Mode” under the point “Item linking”.

Now when you navigate to “configuration” > “things” you can see the “thing” related to your device which should show the status “online”.
After you clicked on your thing you can see the so called “channels”. Those are the functions that you item provides.

The last thing to do is linking the channels together with the item and snice we activated the simple mode, we simply click on the corresponding blue radio button left to the channel.

At last we navigate to the “control” page where we can see our new Item and use its functions.

[[File:Control.png]]

If you want to change anything about your Item, you go to the “Configuration” > “thing” page and click the pen icon.

There you can edit the name, chose a location (eg. living room etc.) and change binding related options like the IP address, the timeout, the refresh interval etc.

== Used Hardware ==

* [[Philips Hue Bridge 2.0, Gateway]]
* [[Amazon Echo Dot]]

[[PHILIPS HUE white and color ambiance single bulb]]

[[PHILIPS HUE motion sensor]]

[[PHILIPS HUE Bridge]]

== References ==

* https://openhab.org
* https://www.oracle.com/technetwork/java/javase/downloads/index.html
* https://docs.oracle.com/javase/10/install/installation-jdk-and-jre-microsoft-windows-platforms.htm#JSJIG-GUID-A7E27B90-A28D-4237-9383-A58B416071CA

[[Category:Documentation]]