node-red-contrib-s7-rust 1.0.3 → 1.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,51 @@ All notable changes to this project are documented here. The format follows
|
|
|
6
6
|
|
|
7
7
|
## [Unreleased]
|
|
8
8
|
|
|
9
|
+
## [1.0.5] - 2026-11-12
|
|
10
|
+
|
|
11
|
+
### Fixed
|
|
12
|
+
|
|
13
|
+
- S7CommPlus over TLS: symbol resolution, `dbs` and `browse` failed on S7-1500 FW V4.x
|
|
14
|
+
(tested on PLCSIM Advanced, FW S4.1) with `Explore returned 0xa201be00017eff79`. With an
|
|
15
|
+
integrity id, the Explore request now ends with one more 0 byte after the fill, like
|
|
16
|
+
S7CommPlusDriver. Symbolic reads such as `"DB".member` work over TLS now. The fake PLC
|
|
17
|
+
refuses the old request in TLS sessions, and the TLS test explores the DB list.
|
|
18
|
+
- S7CommPlus: a PLC that refuses a session without TLS (PLCSIM Advanced V8 with FW S4.1, or
|
|
19
|
+
"Only allow secure PG/PC and HMI communication") gave "CreateObject returned no session id".
|
|
20
|
+
The session setup now detects the negative return value (`0xa201d6000214fdf8`) and, when
|
|
21
|
+
the PLC supports TLS, says: "the PLC refused the session without TLS … enable TLS on the
|
|
22
|
+
endpoint" (#11). The fake PLC models this PLC, and goes on in plain text when a client
|
|
23
|
+
skips TLS after InitSsl.
|
|
24
|
+
- S7CommPlus: `dbs` reported a standard DB as `optimized: true` on S7-1500 FW V4.x (PLCSIM
|
|
25
|
+
Advanced, FW S4.1), and the symbols of that DB got no classic absolute address. This
|
|
26
|
+
firmware sets the optimized-access flag in standard DBs too. A DB with classic elements
|
|
27
|
+
(bit-offset info 0x08) is now a standard DB (#10). The fake PLC can send FW V4.x flags.
|
|
28
|
+
|
|
29
|
+
## [1.0.4] - 2026-11-08
|
|
30
|
+
|
|
31
|
+
### Fixed
|
|
32
|
+
|
|
33
|
+
- Tag addresses out of the S7 address range are now an error. Before, a byte offset past
|
|
34
|
+
2097151 (`DB1.DBB2097152`) wrapped in the 24-bit address field and reached another address
|
|
35
|
+
(`DB1.DBB0`), a timer/counter number past 65535 lost its high bits, and a count past
|
|
36
|
+
32767 (`T5[70000]`) was cut (and a very large one made the connection thread panic). All three
|
|
37
|
+
address syntaxes check the range.
|
|
38
|
+
|
|
39
|
+
### Added
|
|
40
|
+
|
|
41
|
+
- Fuzzing: cargo-fuzz targets for S7comm replies (COTP, S7 header, ReadVar data,
|
|
42
|
+
Userdata), tag addresses and values, block information and clock, S7CommPlus PDU
|
|
43
|
+
reassembly, messages, values, objects, notifications, alarm texts and comment blobs
|
|
44
|
+
(`fuzz/`, CI workflow `fuzz.yml`).
|
|
45
|
+
|
|
46
|
+
### Changed
|
|
47
|
+
|
|
48
|
+
- GitHub releases start with a summary for users (`.github/release-notes/`), then the
|
|
49
|
+
CHANGELOG section.
|
|
50
|
+
- CI: cargo-zigbuild installed from a hash-pinned requirements file; Node-RED 4 tests use the
|
|
51
|
+
locked alias `node-red-4` (no unpinned `npm install`); `node-red-dev` pinned; SECURITY.md
|
|
52
|
+
links the private reporting form.
|
|
53
|
+
|
|
9
54
|
## [1.0.3] - 2026-11-06
|
|
10
55
|
|
|
11
56
|
### Changed
|
|
@@ -57,7 +102,9 @@ First release: the next generation of `@oriolrius/node-red-contrib-s7`.
|
|
|
57
102
|
- CI: tests on Node-RED 4 and 5, gitleaks, GitGuardian, RustSec and npm audit, CodeQL,
|
|
58
103
|
OpenSSF Scorecard, Dependabot. License LGPL-3.0-only.
|
|
59
104
|
|
|
60
|
-
[Unreleased]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.0.
|
|
105
|
+
[Unreleased]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.0.5...HEAD
|
|
106
|
+
[1.0.5]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.0.4...v1.0.5
|
|
107
|
+
[1.0.4]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.0.3...v1.0.4
|
|
61
108
|
[1.0.3]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.0.2...v1.0.3
|
|
62
109
|
[1.0.2]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.0.1...v1.0.2
|
|
63
110
|
[1.0.1]: https://github.com/oriolrius/node-red-contrib-s7-rust/compare/v1.0.0...v1.0.1
|
package/README.md
CHANGED
|
@@ -5,6 +5,8 @@
|
|
|
5
5
|
[](https://github.com/oriolrius/node-red-contrib-s7-rust/actions/workflows/security.yml)
|
|
6
6
|
[](https://github.com/oriolrius/node-red-contrib-s7-rust/actions/workflows/codeql.yml)
|
|
7
7
|
[](https://scorecard.dev/viewer/?uri=github.com/oriolrius/node-red-contrib-s7-rust)
|
|
8
|
+
[](https://www.bestpractices.dev/projects/16456)
|
|
9
|
+
[](https://github.com/oriolrius/node-red-contrib-s7-rust/actions/workflows/fuzz.yml)
|
|
8
10
|
[](LICENSE)
|
|
9
11
|
|
|
10
12
|
Siemens S7 nodes for [Node-RED](https://nodered.org). The two S7 protocols are written in Rust and
|
|
@@ -20,6 +22,16 @@ package ships prebuilt binaries for **Linux x64** (glibc and musl/Alpine).
|
|
|
20
22
|
|
|
21
23
|
This is the next generation of
|
|
22
24
|
[@oriolrius/node-red-contrib-s7](https://www.npmjs.com/package/@oriolrius/node-red-contrib-s7).
|
|
25
|
+
|
|
26
|
+
> [!TIP]
|
|
27
|
+
> **Reviewers and contributors wanted.** The goal is an S7 connector that covers the S7comm and
|
|
28
|
+
> S7CommPlus functions as close to 100% as possible, with every change reviewed by someone other
|
|
29
|
+
> than its author. A single maintainer cannot approve their own pull requests, so the OpenSSF
|
|
30
|
+
> Scorecard [Code-Review](https://github.com/ossf/scorecard/blob/main/docs/checks.md#code-review)
|
|
31
|
+
> score stays low. If you know Siemens S7, Rust or Node-RED, please
|
|
32
|
+
> [review an open pull request](https://github.com/oriolrius/node-red-contrib-s7-rust/pulls) or
|
|
33
|
+
> take a ❌ item of the [protocol coverage](#protocol-coverage) map. See
|
|
34
|
+
> [CONTRIBUTING.md](CONTRIBUTING.md).
|
|
23
35
|
See [Migration](#migration-from-oriolriusnode-red-contrib-s7).
|
|
24
36
|
|
|
25
37
|
## Contents
|
|
@@ -160,6 +172,9 @@ This map shows each protocol function and where it is available. It is strict: a
|
|
|
160
172
|
|
|
161
173
|
**S7CommPlus (S7-1200/1500)**: no PUT/GET, optimized DBs are fine. Use symbols. If the CPU has an
|
|
162
174
|
access level password, set it in the endpoint. TLS needs S7-1500 FW ≥ 2.9 or S7-1200 FW ≥ 4.5.
|
|
175
|
+
Some CPUs accept only TLS sessions (PLCSIM Advanced V8 with FW S4.1, or a CPU with "Only allow
|
|
176
|
+
secure PG/PC and HMI communication"): without TLS the connection fails with "the PLC refused the
|
|
177
|
+
session without TLS". Turn on TLS in the endpoint.
|
|
163
178
|
|
|
164
179
|
## Addresses
|
|
165
180
|
|
|
Binary file
|
|
Binary file
|
|
@@ -15,6 +15,8 @@
|
|
|
15
15
|
<h4>S7CommPlus</h4>
|
|
16
16
|
<p>Symbols are resolved once per session (a reconnect resolves them again). The PLC
|
|
17
17
|
certificate is not verified. The password is stored as a Node-RED credential.</p>
|
|
18
|
+
<p>Some CPUs accept only TLS sessions (for example PLCSIM Advanced V8, FW S4.1). If the
|
|
19
|
+
connection fails with "the PLC refused the session without TLS", turn on TLS.</p>
|
|
18
20
|
<h4>Log</h4>
|
|
19
21
|
<p>Messages go to the Node-RED log. <code>trace</code> logs every frame in hex.</p>
|
|
20
22
|
<h3>References</h3>
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "node-red-contrib-s7-rust",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.5",
|
|
4
4
|
"description": "Siemens S7 nodes for Node-RED: S7comm and S7CommPlus (S7-1200/1500 symbolic access) clients written in Rust, running in-process (Node-API). Linux x64.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"node-red",
|
|
@@ -70,6 +70,7 @@
|
|
|
70
70
|
},
|
|
71
71
|
"devDependencies": {
|
|
72
72
|
"node-red": "^5.0.0",
|
|
73
|
+
"node-red-4": "npm:node-red@^4.1.17",
|
|
73
74
|
"node-red-node-test-helper": "^0.3.6"
|
|
74
75
|
},
|
|
75
76
|
"publishConfig": {
|