Cbridge setup - Versionsgeschichte

Sv: update SSL settings: client cert stored in prefs, load/inspect/clear buttons, chain validation

2026-05-27T13:48:21Z

update SSL settings: client cert stored in prefs, load/inspect/clear buttons, chain validation

← Nächstältere Version		Version vom 27. Mai 2026, 13:48 Uhr
Zeile 128:		Zeile 128:
	In expecco, configure the CBridge connection under "''Extras''" → "''Settings''" → "''Execution''" → "''External Script Interpreters''" → "''CBridge''":		In expecco, configure the CBridge connection under "''Extras''" → "''Settings''" → "''Execution''" → "''External Script Interpreters''" → "''CBridge''":
	* '''Use SSL''': enable encrypted connection		* '''Use SSL''': enable encrypted connection
	* '''Certificate File''': the server certificate PEM (~~for~~ the bridge process)		* '''Certificate File''': the server certificate PEM (used by the bridge process)
	* '''Client Certificate ~~File~~''': ~~the~~ client certificate PEM ~~(presented~~ to the ~~server~~ ~~for~~ ~~mTLS~~)		* '''Client Certificate''': load a client certificate PEM for mutual TLS authentication. The certificate is stored in the expecco preferences (not as a file path). Use the buttons:
			** '''"..."''' to load a certificate from a PEM file
			** '''"?"''' to inspect the certificate chain (shows subject, issuer, validity, algorithm, CA flag, private key presence, and chain verification via AuthorityKeyIdentifier)
			** '''"X"''' to remove the stored certificate
			: On load, the certificate chain is validated: the leaf certificate must not be expired, the CA must have the BasicConstraints CA flag set, and the AuthorityKeyIdentifier must match the CA's SubjectKeyIdentifier (or the issuer DN must match).

	When the client certificate PEM includes the CA certificate in the chain, the CA is automatically trusted for server certificate verification.		When the client certificate PEM includes the CA certificate in the chain, the CA is automatically trusted for server certificate verification — no need to enable "Allow Self-Signed Certificates".

			The same SSL and client certificate settings are also available in the Python bridge settings dialog ("''Extras''" → "''Settings''" → "''Execution''" → "''External Script Interpreters''" → "''Python''").

	==== File Transfer and Directory Operations ====		==== File Transfer and Directory Operations ====

Sv: document SSL/TLS, certificate generation, mTLS, file transfer, makeDirectory

2026-05-27T07:01:30Z

document SSL/TLS, certificate generation, mTLS, file transfer, makeDirectory

← Nächstältere Version		Version vom 27. Mai 2026, 07:01 Uhr
Zeile 93:		Zeile 93:


	=== SSL Connection to ~~the~~ Remote CBridge ===		=== SSL/TLS Connection to a Remote CBridge ===
	You'll need certificate and key files to be generated on the expecco side and manually transport them to the target system.

			The cBridge supports encrypted TLS connections with optional mutual certificate authentication (mTLS).
	Details to be documented...

			==== Generating Certificates ====
			The cBridge can generate Ed25519 CA and server/client certificates directly:

			cBridge --generateCA ~/.ssl/ca.pem --cn "My CA" --days 3650
			cBridge --generateCert ~/.ssl/server.pem --ca ~/.ssl/ca.pem --cn myhost
			cBridge --generateCert ~/.ssl/client.pem --ca ~/.ssl/ca.pem --cn expecco

			Each generated PEM file contains the certificate, private key, and the CA certificate chain. The <code>--cn</code> option sets the common name (default: localhost), <code>--days</code> sets the validity period (default: 3650).

			The same certificate generation is also available via the Python bridge script (<code>--generateCA</code> / <code>--generateCert</code>).

			==== Starting the CBridge with SSL ====

			cBridge --port 8855 --ssl --cert ~/.ssl/server.pem

			A combined PEM file (certificate + key in one file) is used by default. Separate files are also supported:

			cBridge --port 8855 --ssl --cert server.crt --key server.key

			==== Mutual TLS (Client Certificate Authentication) ====

			To require clients to present a certificate signed by the same CA:

			cBridge --port 8855 --ssl --cert ~/.ssl/server.pem --ca ~/.ssl/ca.pem --clientAuth

			Clients must then be configured with a client certificate (see the expecco CBridge settings dialog).

			==== Expecco Settings for SSL ====

			In expecco, configure the CBridge connection under "''Extras''" → "''Settings''" → "''Execution''" → "''External Script Interpreters''" → "''CBridge''":
			* '''Use SSL''': enable encrypted connection
			* '''Certificate File''': the server certificate PEM (for the bridge process)
			* '''Client Certificate File''': the client certificate PEM (presented to the server for mTLS)

			When the client certificate PEM includes the CA certificate in the chain, the CA is automatically trusted for server certificate verification.

			==== File Transfer and Directory Operations ====
			All bridges (C, Python, NodeJS, Ruby, Dart, Smalltalk) support file transfer to and from the remote bridge:
			* <code>putFile: localPath to: remotePath</code> — upload a file
			* <code>getFile: remotePath to: localPath</code> — download a file
			* <code>makeDirectory: remotePath</code> — create a directory (including parent directories)

			These operations work over the bridge's existing connection (including SSL if enabled).

	= Step-by-Step Problem Finding/Fixing =		= Step-by-Step Problem Finding/Fixing =

Cg: /* Remote C-Bridges */

2026-04-20T08:14:30Z

Remote C-Bridges

@@ Zeile 66: / Zeile 66: @@
 = Remote C-Bridges =
-You can run any number of cBridges on any machine within your network, and execute C-actions there. For this, the following setup steps are to be performed:
+You can run any number of cBridges on any machine within your network (and also multiple cBridges on your local or a remote machine), and execute C-actions there. For this, the following setup steps are to be performed:
 * copy the cbridge executable and its support files to a new folder on the target machine; the files are found below the expecco installation folder<br>(eg. "<code>c:\Program Files\exept\expecco</code>") in "<code>packages\bridgeFramework\cBridge\cLibrary</code>".
@@ Zeile 75: / Zeile 75: @@
 * if in doubt, start the cBridge with a "<code>--help</code>" option.
 === SSL Connection to the Remote CBridge ===

Cg: /* Ensure that the compilation works */

2026-03-23T13:09:36Z