projects
/
hmcfgusb
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
ed57121
)
README: formatting
author
Michael Gernoth
<michael@gernoth.net>
Fri, 11 Sep 2015 10:58:22 +0000
(12:58 +0200)
committer
Michael Gernoth
<michael@gernoth.net>
Fri, 11 Sep 2015 10:58:22 +0000
(12:58 +0200)
README.md
patch
|
blob
|
blame
|
history
diff --git
a/README.md
b/README.md
index 26bf79ccdcc62cdeb19e5e2eb07b280335cd3ad1..ee77bc07c5420ea78c788ac84e1cc0a60e0e0782 100644
(file)
--- a/
README.md
+++ b/
README.md
@@
-48,7
+48,7
@@
AES-signing like [KeyMatic][].
``define hmusb HMLAN 127.0.0.1:1234``
``attr hmusb hmId <hmId>``
``define hmusb HMLAN 127.0.0.1:1234``
``attr hmusb hmId <hmId>``
-**Important compatibility information:**
+**Important compatibility information:**
If older Fhem-versions (before 2015-06-19) or [Homegear][] before 2015-07-01
is used to connect to hmland, the `-I` switch might be needed to
impersonate a LAN-interface (this replaces the identity string HM-USB-IF with
If older Fhem-versions (before 2015-06-19) or [Homegear][] before 2015-07-01
is used to connect to hmland, the `-I` switch might be needed to
impersonate a LAN-interface (this replaces the identity string HM-USB-IF with
@@
-60,7
+60,7
@@
hmland without this switch. It was the hardcoded default in versions
This incompatibility is needed so connecting software is able to
differentiate between HM-CFG-LAN and HM-CFG-USB.
This incompatibility is needed so connecting software is able to
differentiate between HM-CFG-LAN and HM-CFG-USB.
-**Important security information:**
+**Important security information:**
Versions before 0.101 do not correctly transmit the AES channel-mask
to the HM-CFG-USB, which results in signature-requests not being generated
by the device in most cases. This can lead to processing of unsigned messages
Versions before 0.101 do not correctly transmit the AES channel-mask
to the HM-CFG-USB, which results in signature-requests not being generated
by the device in most cases. This can lead to processing of unsigned messages
Impressum
,
Datenschutz