expecco Wiki (Version 25.x) - Letzte Änderungen [de]

FAQ on Bridges/en

2026-05-27T13:48:26Z

update SSL section: client cert in prefs, load/inspect/clear UI, chain validation on load

← Nächstältere Version		Version vom 27. Mai 2026, 13:48 Uhr
Zeile 212:		Zeile 212:
	All bridges support SSL/TLS encrypted connections. This provides both confidentiality and (with mutual TLS) authentication.		All bridges support SSL/TLS encrypted connections. This provides both confidentiality and (with mutual TLS) authentication.

	To enable SSL for a bridge connection, configure the following in the expecco bridge settings:		To enable SSL for a bridge connection, configure the following in the expecco bridge settings (under "''Extras''" → "''Settings''" → "''Execution''" → "''External Script Interpreters''" → "''CBridge''" or "''Python''"):
	* '''Use SSL''': enable TLS encryption		* '''Use SSL''': enable TLS encryption
	* '''Certificate File''': PEM file containing the server certificate and private key (used by the bridge process)		* '''Certificate File''': PEM file containing the server certificate and private key (used by the bridge process)
			* '''Client Certificate''': the client certificate for mutual TLS authentication. The PEM content is stored directly in the expecco preferences. Use the '''"..."''' button to load from a file, '''"?"''' to inspect the certificate chain, and '''"X"''' to clear it. On load, the certificate chain is validated (expiry, CA flag, key identifier match).
	* '''Client Certificate File''': PEM file containing the client certificate and private key (presented to servers that require client authentication)

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

	Certificate generation is built into the cBridge and Python bridge executables using Ed25519 keys:		Certificate generation is built into the cBridge and Python bridge executables using Ed25519 keys:
Zeile 222:		Zeile 224:
	cBridge --generateCert client.pem --ca ca.pem --cn expecco		cBridge --generateCert client.pem --ca ca.pem --cn expecco

	Generated PEM files include the full certificate chain~~, so the CA is automatically trusted without additional configuration~~.		Generated PEM files include the full certificate chain.

	For mutual TLS (mTLS), start the remote bridge with the <code>--clientAuth</code> flag:		For mutual TLS (mTLS), start the remote bridge with the <code>--clientAuth</code> flag:

Cbridge setup

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 ====

FAQ on Bridges/en

2026-05-27T07:02:32Z

add SSL/TLS section and file transfer/makeDirectory documentation

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

	All bridges support command line arguments to only accept connections from a particular host; this option should be used if a remote bridge is started via a remote shell command.		All bridges support command line arguments to only accept connections from a particular host; this option should be used if a remote bridge is started via a remote shell command.

			=== SSL/TLS Encrypted Connections ===
			All bridges support SSL/TLS encrypted connections. This provides both confidentiality and (with mutual TLS) authentication.

			To enable SSL for a bridge connection, configure the following in the expecco bridge settings:
			* '''Use SSL''': enable TLS encryption
			* '''Certificate File''': PEM file containing the server certificate and private key (used by the bridge process)
			* '''Client Certificate File''': PEM file containing the client certificate and private key (presented to servers that require client authentication)

			Certificate generation is built into the cBridge and Python bridge executables using Ed25519 keys:
			cBridge --generateCA ca.pem --cn "My CA"
			cBridge --generateCert server.pem --ca ca.pem --cn myhost
			cBridge --generateCert client.pem --ca ca.pem --cn expecco

			Generated PEM files include the full certificate chain, so the CA is automatically trusted without additional configuration.

			For mutual TLS (mTLS), start the remote bridge with the <code>--clientAuth</code> flag:
			cBridge --port 8855 --ssl --cert server.pem --clientAuth

			See [[Cbridge_setup#SSL/TLS_Connection_to_a_Remote_CBridge\|CBridge Setup: SSL/TLS Connection]] for detailed instructions.

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

			These operations use the existing bridge connection and work over SSL if enabled. They are useful for deploying test data, collecting results, or transferring compiled binaries.

	== [OS X Only] CrashReporter Dialog Boxes ==		== [OS X Only] CrashReporter Dialog Boxes ==

Cbridge setup

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 =

Release Notes 26.x

2026-05-26T23:45:27Z

Release 26.1 (Q2 2026)

← Nächstältere Version		Version vom 26. Mai 2026, 23:45 Uhr
(Eine dazwischenliegende Version desselben Benutzers wird nicht angezeigt)
Zeile 19:		Zeile 19:
	* Feature: Qt-Plugin supports Qt6.8 ([[QT_Testing/en#ExpeccoTestService_Library%3A_Delivery_in_Expecco_Versions\|Delivered versions for QT and build environment]])		* Feature: Qt-Plugin supports Qt6.8 ([[QT_Testing/en#ExpeccoTestService_Library%3A_Delivery_in_Expecco_Versions\|Delivered versions for QT and build environment]])
	* Feature: improved search text box behavior in text editors (type RETURN, CMD-f or CMD-b while box is open) and back to original position button added.		* Feature: improved search text box behavior in text editors (type RETURN, CMD-f or CMD-b while box is open) and back to original position button added.
	* Feature: Improved/Fixed the [[Number_API_Functions\|Number]] stack:		* Feature: Improved/Fixed the [[Number_API_Functions\|Number]] stack (see also in [[Numeric_Limits/en\| Numeric Limits]]):
	** Enhanced multiprecision numbers (eg. <float>q, <float>Q constants in freeze values)		** Enhanced multiprecision numbers (eg. <float>q, <float>Q constants in freeze values)
	** Float32 numbers (<float>f)		** Float32 numbers (<float>f)
	** Integer freezeValues in exponential notation (eg. 1e5)		** Integer freezeValues in exponential notation (eg. 1e5)
	** Recognize type specific infinities eg. "inf.0", "inf.0f", "inf.0q" etc. and type specific NaNs eg. "nan.0", "nan.0f", "nan.0q" etc. (useful when parsing/receiving values from the outside world)		** Recognize type specific infinities eg. "inf.0", "inf.0f", "inf.0q" etc. and type specific NaNs eg. "nan.0", "nan.0f", "nan.0q" etc. (useful when parsing/receiving values from the outside world)
	** fixed/added missing trigonometric functions for multiprecision floats and complex numbers (eg. arcTan)		** fixed/added missing trigonometric functions for multiprecision floats and complex numbers (eg. arcTan). Now all test cases produce a result within the precision limits of their type
	** inspector (and activitylog as a consequence) show the type of a float (suffix 'f', 'q', 'Q' etc.)		** inspector (and activitylog as a consequence) show the type of a float (suffix 'f', 'q', 'Q' etc.)

DiagramElements-FreezeValue/en

2026-05-26T22:06:27Z

Float

← Nächstältere Version		Version vom 26. Mai 2026, 22:06 Uhr
Zeile 30:		Zeile 30:

	By default, floats are represented as double-precision IEEE limited precision rationals (64 bit).		By default, floats are represented as double-precision IEEE limited precision rationals (64 bit).
	You can force single precision floats by using the 'f' exponent indicator.		You can force single precision floats by using the 'f' exponent indicator (or an 'f' suffix).

	* double precision (64bit) floats such as: "<code>123.0</code>", "<code>+123.0</code>", "<code>-123.0</code>", "<code>.123</code>", "<code>123.</code>", "<code>123.0e+2</code>", "<code>123.0e-2</code>"		* double precision (64bit) floats such as: "<code>123.0</code>", "<code>+123.0</code>", "<code>-123.0</code>", "<code>.123</code>", "<code>123.</code>", "<code>123.0e+2</code>", "<code>123.0e-2</code>"
Zeile 40:		Zeile 40:
	* quadruple precision (128 bit): "<code>123.0Q+2</code>" or "<code>-123.0Q</code>"		* quadruple precision (128 bit): "<code>123.0Q+2</code>" or "<code>-123.0Q</code>"

	Do not expect any speed or other advantages when using single precision floats. Actually, expect problems due to larger errors, non-stable series computations etc. Use them only if you need to emulate less precise computations.		Do not expect any speed or other advantages when using single precision floats (depends on the CPU). Actually, expect problems due to larger errors, non-stable series computations etc. Use them only if you need to emulate less precise computations.

	Extended precision floats may not be supported by all CPU types (these use the underlying machine's "long double" data type, which is either an 80-bit extended IEEE or a 128-bit quadruple IEEE float (eg. on Sparc CPUs). Not all CPUs do support these and we can not guarantee that future machines will dp. However, currently all supported architectures do.		Extended precision floats may not be supported by all CPU types (these use the underlying machine's "long double" data type, which is either an 80-bit extended IEEE or a 128-bit quadruple IEEE float (eg. on Sparc CPUs). Not all CPUs do support these and we can not guarantee that future machines will. However, currently all supported architectures do.

	Notice that depending on the CPU, quadruple precision arithmetic might be performed by software and will therefore be slow (currently the case for all supported architectures)		Notice that depending on the CPU, quadruple precision arithmetic might be performed by software and will therefore be slow (currently the case for all supported architectures)

Release Notes 26.x

2026-05-26T22:01:22Z

Release 26.1 (Q2 2026)

Remote Access/en

2026-05-26T18:52:47Z

Fold the Automatic-Refresh bullets onto single physical lines

← Nächstältere Version		Version vom 26. Mai 2026, 18:52 Uhr
Zeile 56:		Zeile 56:
	detect external changes. The default depends on the current root:		detect external changes. The default depends on the current root:

	* Local filesystem → '''on''' (10-second cycle, matches the		* Local filesystem → '''on''' (10-second cycle, matches the long-standing behaviour).
			* SFTP → '''off'''. Each cycle costs one STAT round-trip per child, which is fine for a handful of local directories but painful over the network. Click Refresh manually when you need to pick up remote changes.
	long-standing behaviour).
	* SFTP → '''off'''. Each cycle costs one STAT round-trip
	per child, which is fine for a handful of local directories but
	painful over the network. Click Refresh manually when you need
	to pick up remote changes.

	When you navigate between local and SFTP roots the toggle flips		When you navigate between local and SFTP roots the toggle flips

Remote Access

2026-05-26T18:52:45Z

Fold the Automatic-Refresh bullets onto single physical lines

← Nächstältere Version		Version vom 26. Mai 2026, 18:52 Uhr
Zeile 62:		Zeile 62:
	sich nach der aktuellen Wurzel:		sich nach der aktuellen Wurzel:

	* Lokales Dateisystem → '''an''' (10-Sekunden-Zyklus,		* Lokales Dateisystem → '''an''' (10-Sekunden-Zyklus, entspricht dem bisherigen Verhalten).
			* SFTP → '''aus'''. Jeder Zyklus kostet einen STAT-Roundtrip pro Kind — für eine Handvoll lokaler Verzeichnisse harmlos, über das Netz schmerzhaft. Bei Bedarf manuell auf Refresh klicken, um Änderungen zu sehen.
	entspricht dem bisherigen Verhalten).
	* SFTP → '''aus'''. Jeder Zyklus kostet einen
	STAT-Roundtrip pro Kind — für eine Handvoll lokaler
	Verzeichnisse harmlos, über das Netz schmerzhaft. Bei Bedarf
	manuell auf Refresh klicken, um Änderungen zu sehen.

	Beim Wechsel zwischen lokalen und SFTP-Wurzeln wird der Schalter		Beim Wechsel zwischen lokalen und SFTP-Wurzeln wird der Schalter

Remote Access/en

2026-05-26T18:50:31Z

Document the Automatic Refresh dropdown toggle and its root-type default

← Nächstältere Version		Version vom 26. Mai 2026, 18:50 Uhr
Zeile 43:		Zeile 43:
	<code>/</code>.		<code>/</code>.

		⚫	The '''Refresh''' button in the toolbar (the round-arrow icon
	The directory tree does '''not''' auto-update: previously a background
		⚫	between ''Forward'' and ''DirectoryUp'') re-reads both the
	task walked every expanded item every 10 seconds, which over SFTP
		⚫	directory tree and the contents pane on demand. Works uniformly
	meant one STAT round-trip per child on every cycle. Click the
		⚫	for local and SFTP paths; for SFTP it also flushes the per-file
⚫	'''Refresh''' button in the toolbar (the round-arrow icon ~~between~~
		⚫	STAT cache, so changes made directly on the remote side become
⚫	''Forward'' and ''DirectoryUp'') to re-~~read~~ ~~the tree and~~ the
		⚫	visible immediately rather than waiting for the 5-second cache TTL
⚫	contents pane on demand. ~~Refresh works~~ uniformly ~~for local and~~
		⚫	to expire.
⚫	SFTP paths; for SFTP it also flushes the per-file ~~STAT cache, so~~

⚫	changes made directly on the remote side become ~~visible~~
			The small arrow next to the Refresh icon opens a dropdown with a
⚫	immediately rather than waiting for the 5-second cache TTL to
			single checkbox, '''Automatic Refresh''', controlling the
⚫	expire.
			background polling task that walks every expanded tree item to
			detect external changes. The default depends on the current root:

			* Local filesystem → '''on''' (10-second cycle, matches the
			long-standing behaviour).
			* SFTP → '''off'''. Each cycle costs one STAT round-trip
			per child, which is fine for a handful of local directories but
			painful over the network. Click Refresh manually when you need
			to pick up remote changes.

			When you navigate between local and SFTP roots the toggle flips
			automatically — but only if you haven't overridden it for
			the previous root. An explicit user choice is preserved across
			navigations.

	The Tools menu offers four browser actions, three of them gated on		The Tools menu offers four browser actions, three of them gated on

Remote Access

2026-05-26T18:50:28Z

Document the Automatic Refresh dropdown toggle and its root-type default

← Nächstältere Version		Version vom 26. Mai 2026, 18:50 Uhr
Zeile 48:		Zeile 48:
	ist standardmäßig 22, Pfad standardmäßig <code>/</code>.		ist standardmäßig 22, Pfad standardmäßig <code>/</code>.

		⚫	Die Schaltfläche '''Refresh''' in der Symbolleiste
	Der Verzeichnisbaum aktualisiert sich '''nicht''' automatisch:
		⚫	(Pfeil-Kreis-Symbol zwischen ''Forward'' und ''DirectoryUp'') liest
	früher lief im Hintergrund alle 10 Sekunden ein Task über jeden
		⚫	Baum und Inhalts-Panel auf Anforderung neu ein. Funktioniert
	expandierten Eintrag, was bei SFTP einen STAT-Roundtrip pro Kind
		⚫	einheitlich für lokale und SFTP-Pfade; bei SFTP wird zusätzlich der
⚫	~~und Zyklus bedeutete. Mit der~~ Schaltfläche '''Refresh''' in der
		⚫	per-Datei-STAT-Cache geleert, sodass Änderungen, die direkt auf
⚫	~~Symbolleiste~~ (Pfeil-Kreis-Symbol zwischen ''Forward'' und
		⚫	der Gegenseite gemacht wurden, sofort sichtbar werden — ohne auf
⚫	~~''DirectoryUp'') werden~~ Baum und Inhalts-Panel auf Anforderung
		⚫	den Ablauf der 5-Sekunden-Cache-TTL zu warten.
	neu eingelesen. Refresh funktioniert einheitlich für lokale und

⚫	SFTP-Pfade; bei SFTP wird zusätzlich der ~~per-Datei-STAT-Cache~~
			Der kleine Pfeil neben dem Refresh-Symbol öffnet ein Aufklappmenü
⚫	geleert, sodass Änderungen, die direkt auf ~~der Gegenseite~~
			mit einem einzelnen Kontrollkästchen, '''Automatic Refresh''', das
⚫	gemacht wurden, sofort sichtbar werden — ohne auf ~~den Ablauf der~~
			den Hintergrund-Task an- bzw. abschaltet, der alle expandierten
⚫	5-Sekunden-Cache-TTL zu warten.
			Baumeinträge auf externe Änderungen prüft. Die Vorgabe richtet
			sich nach der aktuellen Wurzel:

			* Lokales Dateisystem → '''an''' (10-Sekunden-Zyklus,
			entspricht dem bisherigen Verhalten).
			* SFTP → '''aus'''. Jeder Zyklus kostet einen
			STAT-Roundtrip pro Kind — für eine Handvoll lokaler
			Verzeichnisse harmlos, über das Netz schmerzhaft. Bei Bedarf
			manuell auf Refresh klicken, um Änderungen zu sehen.

			Beim Wechsel zwischen lokalen und SFTP-Wurzeln wird der Schalter
			automatisch umgelegt — aber nur, sofern man ihn für die
			vorherige Wurzel nicht selbst verstellt hat. Eine explizite
			Benutzerwahl bleibt über Navigationen hinweg erhalten.

	Das Menü '''Tools''' im FileBrowserV2 bietet vier Aktionen — die		Das Menü '''Tools''' im FileBrowserV2 bietet vier Aktionen — die

Tools FileBrowser/en

2026-05-26T16:45:39Z

Overview

← Nächstältere Version		Version vom 26. Mai 2026, 16:45 Uhr
(8 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 1:		Zeile 1:
	== Overview ==		== Overview ==
	The File Browser provides useful functions to search, manipulate and edit files. In expecco, its main use is to provide a simple but powerful editor to look at traces, test data attachments or to edit configuration files. The editor supports Unicode and various common encodings and can also display binary data (hex dumps), bitmap images, XML, HTML and some other common file formats.		The File Browser provides useful functions to search, manipulate and edit files. In expecco, its main use is to provide a simple but powerful editor to look at traces, test data attachments or to edit configuration files. The editor supports Unicode and various common encodings and can also display binary data (hex dumps), bitmap images, XML, HTML and some other common file formats.

			Notice that this is not meant as a replacement for a powerful specialized text editor. However, it is light weight, starts fast and provides many utilities for day to day tasks. <br><small> (actually, its origins go back almost 40 years, long before other systems even had a graphical user interface !).</small>

	The tool's [http://live.exept.de/doc/online/english/tools/fbrowserV2/TOP.html documentation] is part of the official [http://live.exept.de/doc/online/english/TOP.html Smalltalk/X Online Documentation].		The tool's [http://live.exept.de/doc/online/english/tools/fbrowserV2/TOP.html documentation] is part of the official [http://live.exept.de/doc/online/english/TOP.html Smalltalk/X Online Documentation].
Zeile 35:		Zeile 37:

	The search is usually recursive. Use this e.g. to find all files with a particular suffix, which contain a particular string pattern or which have been modified before/after some particular time/date. In many situations, this search is faster than using "find \| grep" on Unix, and - unless indexed - also faster than corresponding search functions under MS Windows.		The search is usually recursive. Use this e.g. to find all files with a particular suffix, which contain a particular string pattern or which have been modified before/after some particular time/date. In many situations, this search is faster than using "find \| grep" on Unix, and - unless indexed - also faster than corresponding search functions under MS Windows.

			== Editing Multiple Files ==
			The "''Add Text Editor Page''" menu function in the main menu's ''Browser'' entry adds additional text editor tabs.

	== Embedded VT100 Terminal Emulator ==		== Embedded VT100 Terminal Emulator ==

	The File Browser includes a vt100 emulator, in which shell or cmd consoles are shown. The emulation is not 100% perfect, so please be tolerant when some cursor-movements are not accurate or leave garbage characters on the screen (especially cursor movements at the right/bottom may wrap differently than the "real thing"). For real editor work, use xterm under Unix or a cmd window under MS Windows.		The File Browser includes a vt100 emulator, in which shell or cmd consoles are shown. The emulation is not 100% perfect, so please be tolerant when some cursor-movements are not accurate or leave garbage characters on the screen (especially cursor movements at the right/bottom may wrap differently than the "real thing"). For real editor work, use xterm under Unix or a cmd window under MS Windows.

			== SSH Remote Login ==
			Starting with expecco 26.1, remote login and remote file transfer via secure sockets is available both via toolbar buttons and the ''Tools'' menu. In addition, keypair generation is provided via the menu.

	== Advanced File Operations ==		== Advanced File Operations ==
Zeile 61:		Zeile 69:
	=== Copying Corrupted Files ===		=== Copying Corrupted Files ===

	This operation may be helpful to extract as much as possible data from partially broken files. I.e. to copy files ~~form~~ a ~~disks~~ or ~~tapes~~ with errors.		This operation may be helpful to extract as much as possible data from partially broken files. I.e. to copy files from an old disk or tape with errors.
	It will copy the file ~~blockwise~~ and skip over bad blocks when an error is encountered (instead of the regular copy operation, which stops when a read error happens). Instead ~~of stopping~~, it will retry to copy the bad data block a few times, and then write a block of zeros to the output and continue to copy (or try to copy) the rest of the file or tape.		It will copy the file block wise and skip over bad blocks when an error is encountered (instead of the regular copy operation, which stops when a read error happens). Instead, it will retry to copy the bad data block a few times, and then write a block of zeros to the output and continue to copy (or try to copy) the rest of the file or tape.

	=== Truncate File ===		=== Truncate File ===

	This truncates a file to a given size, effectively cutting off the tail of a file.		This truncates a file to a given size, effectively cutting off the tail of a file.

			=== Erase File ===
			Will write zero bytes over an existing file in order to really clear files with security data (such as cryptographic keys or passwords) as opposed to removal or truncation (which will leave the blocks untouched and only put them onto a freelist unless the OS provides specal mount/disk options. Not all operating systems will actually make the original data unrecoverable (journalling file systems), so this may not be effective, depending on your OS.

	=== File Differences ===		=== File Differences ===

Release Notes 26.x

2026-05-26T16:13:11Z

Release 26.1 (Q2 2026)

← Nächstältere Version		Version vom 26. Mai 2026, 16:13 Uhr
(Eine dazwischenliegende Version desselben Benutzers wird nicht angezeigt)
Zeile 36:		Zeile 36:
	* Feature: file transfer (getFile/putFile) and makeDirectory for all bridges (C, Python, NodeJS, Ruby, Dart, Smalltalk)		* Feature: file transfer (getFile/putFile) and makeDirectory for all bridges (C, Python, NodeJS, Ruby, Dart, Smalltalk)
	* Feature: defineFunction/callFunction support for NodeJS, Ruby and Smalltalk bridges		* Feature: defineFunction/callFunction support for NodeJS, Ruby and Smalltalk bridges
⚫	* Performance: execution of elementary Smalltalk and JavaScript actions tuned for speed (Jitter improvements)
	* Feature: OLE for 64 bit architectures		* Feature: OLE for 64 bit architectures
	* Feature: optional HTTPS for the AIDYMO and license server — drop a PEM cert+key into <code>--workDir</code> (combined <code>server.pem</code>, or split<code>fullchain.pem</code>+<code>privkey.pem</code> / <code>cert.pem</code>+<code>key.pem</code>) and the service binds TLS automatically; informational hostname is derived from the certificate (SAN-aware, wildcard- and multi-SAN-safe)		* Feature: optional HTTPS for the AIDYMO and license server — drop a PEM cert+key into <code>--workDir</code> (combined <code>server.pem</code>, or split<code>fullchain.pem</code>+<code>privkey.pem</code> / <code>cert.pem</code>+<code>key.pem</code>) and the service binds TLS automatically; informational hostname is derived from the certificate (SAN-aware, wildcard- and multi-SAN-safe)
	* Feature: more search options in the [[How_to_Program/en#MethodFinder:_Find_Functions_by_Example \| MethodFinder]].		* Feature: more search options in the [[How_to_Program/en#MethodFinder:_Find_Functions_by_Example \| MethodFinder]].
	*Fix: many fixes related to DPI scaling. I.e. when multiple monitors are configured with different scaling (especially different from 100%). Includes scaling of fonts, bitmap and UI components (widgets).		* Fix: many fixes related to DPI scaling. I.e. when multiple monitors are configured with different scaling (especially different from 100%). Includes scaling of fonts, bitmap and UI components (widgets).
	*Fix: display of very long lines in a text editor/inspector (workaround a Windows 16bit line limit)		* Fix: display of very long lines in a text editor/inspector (workaround a Windows 16bit line limit)
	*Fix: due to a bug in enumeration datatypes, the size of ".ets" files grew over time to huge sizes (some information was redundantly and identically written twice). This had no effect on the execution, but made load/save times almost unacceptably long by storing/reloading unneeded data. When loaded and saved again, this will fix those ets files automatically (there is also a patch for older versions)		* Fix: due to a bug in enumeration datatypes, the size of ".ets" files grew over time to huge sizes (some information was redundantly and identically written twice). This had no effect on the execution, but made load/save times almost unacceptably long by storing/reloading unneeded data. When loaded and saved again, this will fix those ets files automatically (there is also a patch for older versions)
		⚫	* Performance: execution of elementary Smalltalk and JavaScript actions tuned for speed (Jitter improvements)
			* Performance: speedup of cryptographic algorithms (affects key generation and other)
			* Performance: tuned loading of stored ets/elf files (30-40% speedup)

Release Notes 26.x

2026-05-26T14:42:30Z

update bridge features: SSL for all bridges incl. Dart+Smalltalk, getFile/putFile/makeDirectory for all bridges, defineFunction/callFunction for NodeJS/Ruby/Smalltalk

Remote Access/en

2026-05-26T13:46:08Z

Document the Refresh toolbar button (and the disabled tree auto-poll)

@@ Zeile 42: / Zeile 42: @@
 User defaults to the local login name, port to 22, path to
 <code>/</code>.
 The Tools menu offers four browser actions, three of them gated on

Remote Access

2026-05-26T13:46:07Z

Document the Refresh toolbar button (and the disabled tree auto-poll)

@@ Zeile 47: / Zeile 47: @@
 Fehlt <code>user</code>, wird der lokale Login-Name verwendet, Port
 ist standardmäßig 22, Pfad standardmäßig <code>/</code>.
 Das Menü '''Tools''' im FileBrowserV2 bietet vier Aktionen — die

Release Notes 26.x

2026-05-26T13:41:16Z

Release 26.1 (Q2 2026)

← Nächstältere Version		Version vom 26. Mai 2026, 13:41 Uhr
Zeile 14:		Zeile 14:
	** model, API key, endpoint and max-tokens are configurable via the Claude settings dialog		** model, API key, endpoint and max-tokens are configurable via the Claude settings dialog
	* Feature: SSL1.3 support (without external SSL library)		* Feature: SSL1.3 support (without external SSL library)
			* Feature: SSL support for C, Python, NodeJS and Ruby bridges
	* Feature: SSH builtin, plus SSH and SFTP clients (both via FileBrowser)		* Feature: SSH builtin, plus SSH and SFTP clients (both via FileBrowser)
	* Feature: public/private keypair generation via a FileBrowser menu (for easy SSH setup)		* Feature: public/private keypair generation via a FileBrowser menu (for easy SSH setup)

Remote Access/en

2026-05-26T10:33:01Z

Fold bullet continuation lines onto a single physical line so MediaWiki keeps them inside <li>

Änderungen zeigen

Remote Access

2026-05-26T10:33:00Z

Fold bullet continuation lines onto a single physical line so MediaWiki keeps them inside <li>

Änderungen zeigen

Remote Access/en

2026-05-26T10:29:04Z

Remove 2-space continuation-line indent (was triggering MediaWiki <pre>)

Änderungen zeigen

Remote Access

2026-05-26T10:29:02Z

Remove 2-space continuation-line indent (was triggering MediaWiki <pre>)

Änderungen zeigen

Vorlage:Languages

2026-05-26T10:22:02Z

Add /en to the enumerated language subpages (for non-English master pages)

← Nächstältere Version		Version vom 26. Mai 2026, 10:22 Uhr
Zeile 17:		Zeile 17:
	}}{{Languages/Lang\|diq\|{{{1\|}}}\|		}}{{Languages/Lang\|diq\|{{{1\|}}}\|
	}}{{Languages/Lang\|el\|{{{1\|}}}\|		}}{{Languages/Lang\|el\|{{{1\|}}}\|
			}}{{Languages/Lang\|en\|{{{1\|}}}\|
	}}{{Languages/Lang\|eo\|{{{1\|}}}\|		}}{{Languages/Lang\|eo\|{{{1\|}}}\|
	}}{{Languages/Lang\|es\|{{{1\|}}}\|		}}{{Languages/Lang\|es\|{{{1\|}}}\|
Zeile 85:		Zeile 86:
	}}{{Languages/Lang\|diq\|{{{1\|}}}\|		}}{{Languages/Lang\|diq\|{{{1\|}}}\|
	}}{{Languages/Lang\|el\|{{{1\|}}}\|		}}{{Languages/Lang\|el\|{{{1\|}}}\|
			}}{{Languages/Lang\|en\|{{{1\|}}}\|
	}}{{Languages/Lang\|eo\|{{{1\|}}}\|		}}{{Languages/Lang\|eo\|{{{1\|}}}\|
	}}{{Languages/Lang\|es\|{{{1\|}}}\|		}}{{Languages/Lang\|es\|{{{1\|}}}\|

Remote Access/en

2026-05-26T10:20:13Z

Use label= for the bold language link (after Template:Languages patch)

← Nächstältere Version		Version vom 26. Mai 2026, 10:20 Uhr
Zeile 1:		Zeile 1:
	{{Languages~~\|Remote Access~~\|Remote Access/en}}		{{Languages\|Remote Access/en\|label=English}}

	'''Remote access''' is the ability to drive a remote computer or		'''Remote access''' is the ability to drive a remote computer or

Remote Access

2026-05-26T10:20:11Z

Use label= for the bold language link (after Template:Languages patch)

← Nächstältere Version		Version vom 26. Mai 2026, 10:20 Uhr
Zeile 1:		Zeile 1:
	{{Languages\|Remote Access\|~~Remote Access/en~~}}		{{Languages\|Remote Access\|label=Deutsch}}

	'''Fernzugriff''' bezeichnet die Möglichkeit, einen entfernten		'''Fernzugriff''' bezeichnet die Möglichkeit, einen entfernten

Vorlage:Languages

2026-05-26T10:19:27Z

Make bold-link label parameterizable (default English) — see Talk for rationale

← Nächstältere Version		Version vom 26. Mai 2026, 10:19 Uhr
Zeile 2:		Zeile 2:
	\| header = '''[[Project:Language policy\|{{Languages/Title\|{{SUBPAGENAME}}}}]]'''		\| header = '''[[Project:Language policy\|{{Languages/Title\|{{SUBPAGENAME}}}}]]'''
	\| text =		\| text =
	'''[[{{{1\|:{{NAMESPACE}}:{{BASEPAGENAME}}}}}\|English]]''' {{Languages/Lang\|af\|{{{1\|}}}\|		'''[[{{{1\|:{{NAMESPACE}}:{{BASEPAGENAME}}}}}\|{{{label\|English}}}]]''' {{Languages/Lang\|af\|{{{1\|}}}\|
	}}{{Languages/Lang\|ar\|{{{1\|}}}\|		}}{{Languages/Lang\|ar\|{{{1\|}}}\|
	}}{{Languages/Lang\|ast\|{{{1\|}}}\|		}}{{Languages/Lang\|ast\|{{{1\|}}}\|

Remote Access/en

2026-05-26T09:53:07Z

Add Filesystem Info feature; document OpenSSH SFTP extensions (posix-rename, hardlink, statvfs, fsync); correct stale limitations/future-work entries.

@@ Zeile 1: / Zeile 1: @@
 '''Remote access''' is the ability to drive a remote computer or
@@ Zeile 52: / Zeile 53: @@
 <code>/</code>.
-The Tools menu offers three SSH-related actions, all gated on the
+The Tools menu offers four browser actions, three of them gated on
-SSH library being loaded:
+the SSH library being loaded:
 * '''Generate SSH Key Pair...''' — opens the same key-generation
@@ Zeile 61: / Zeile 62: @@
 * '''SFTP Connect...''' — points this browser tab at a remote
   filesystem via SFTP.
 == From expecco actions ==
@@ Zeile 372: / Zeile 381: @@
   no SSH_FXP_READLINK exposed (<code>#isSymbolicLink</code> always
   <code>false</code>, <code>#linkInfo</code> returns the regular
-  stat info).  SFTPv5+ features (atomic-overwrite rename via
+  stat info).  Several SFTPv5+ niceties are nevertheless picked up
 * '''Per-host serialisation.'''  Two concurrent operations on the
   same host queue through the host mutex.  See [[#Future work]].
-* '''<code>#renameTo:</code> has a TOCTOU window.'''  POSIX-style
+* '''<code>#renameTo:</code> fallback has a TOCTOU window.'''  On
 * '''<code>#isNonEmptyDirectory</code> is heuristic.'''  Always
   returns <code>#isDirectory</code> (the accurate answer would cost
@@ Zeile 412: / Zeile 424: @@
 heartbeat, SSH_MSG_DISCONNECT.
 |}
 === Connection pooling ===
@@ Zeile 448: / Zeile 496: @@
   + READ_DIR (first batch only) + CLOSE — three RTTs per probe;
   needs SftpClient to pipeline requests before this pays off.
-* '''SFTP v5/v6 negotiation''' for atomic-overwrite rename,
+* '''SFTP v5/v6 negotiation''' for extended attrs and FTP-style
 = Command Shell =

Remote Access

2026-05-26T09:53:04Z

Add Filesystem Info feature; document OpenSSH SFTP extensions (posix-rename, hardlink, statvfs, fsync); correct stale limitations/future-work entries.

@@ Zeile 1: / Zeile 1: @@
 '''Fernzugriff''' bezeichnet die Möglichkeit, einen entfernten
 Rechner oder ein entferntes Netzwerk aus diesem expecco-Image heraus
@@ Zeile 56: / Zeile 58: @@
 ist standardmäßig 22, Pfad standardmäßig <code>/</code>.
-Das Menü '''Tools''' im FileBrowserV2 bietet drei SSH-Aktionen,
+Das Menü '''Tools''' im FileBrowserV2 bietet vier Aktionen — die
-sichtbar nur bei geladener SSH-Bibliothek:
+drei SSH-spezifischen sind nur bei geladener SSH-Bibliothek
 * '''Generate SSH Key Pair...''' — öffnet den
@@ Zeile 66: / Zeile 69: @@
 * '''SFTP Connect...''' — navigiert diesen Browser-Tab über SFTP
   auf ein entferntes Dateisystem.
 == Aus expecco-Aktionen ==
@@ Zeile 399: / Zeile 411: @@
   chmod / chown / utime), kein SSH_FXP_READLINK exponiert
   (<code>#isSymbolicLink</code> liefert immer <code>false</code>,
-  <code>#linkInfo</code> die normale stat-Info).  SFTPv5+-Features
+  <code>#linkInfo</code> die normale stat-Info).  Einige
 * '''Serialisierung pro Host.'''  Zwei gleichzeitige Operationen
   am selben Host stehen am Host-Mutex an.  Siehe [[#Ausblick]].
-* '''<code>#renameTo:</code> hat ein TOCTOU-Fenster.'''
+* '''<code>#renameTo:</code>-Fallback hat ein TOCTOU-Fenster.'''
 * '''<code>#isNonEmptyDirectory</code> ist eine Heuristik.'''
   Liefert immer <code>#isDirectory</code> (die genaue Antwort
@@ Zeile 441: / Zeile 457: @@
 recvSeq, Heartbeat, SSH_MSG_DISCONNECT.
 |}
 === Verbindungs-Pooling ===
@@ Zeile 481: / Zeile 539: @@
   Sondierung; lohnt erst, wenn der SftpClient Anfragen pipelinen
   kann.
-* '''SFTP-v5/v6-Aushandlung''' für atomares Überschreibungs-
+* '''SFTP-v5/v6-Aushandlung''' für erweiterte Attribute und
-  rename, erweiterte Attribute und FTP-artige Kanonisierung.
+  FTP-artige Kanonisierung.  (Atomares Überschreibungs-rename
 = Kommando-Shell =

Remote Access/en

2026-05-26T08:49:01Z

Die Seite wurde neu angelegt: „ '''Remote access''' is the ability to drive a remote computer or network from this expecco image — opening shells, running commands, moving files, or driving a test target. Three protocol families are supported, listed in current-recommended order: * '''SSH and SFTP''' (recommended) — encrypted shell + secure file transfer over an SSH-2 tunnel. Pure-Smalltalk implementation in <code>exept:libcrypt/ssh</code>; no external dependency on OpenSS…“

Neue Seite

'''Remote access''' is the ability to drive a remote computer or
network from this expecco image — opening shells, running commands,
moving files, or driving a test target. Three protocol families are
supported, listed in current-recommended order:

* '''SSH and SFTP''' (recommended) — encrypted shell + secure
file transfer over an SSH-2 tunnel. Pure-Smalltalk implementation
in <code>exept:libcrypt/ssh</code>; no external dependency on
OpenSSL or libssh. Use this for anything that touches credentials
or sensitive payloads.
* '''Local Command Shell''' — fork + exec on the local machine.
Used for local-tool integration and for the local end of a remote
workflow that bridges via another protocol.
* '''Telnet''' (legacy) — plain-text terminal session. No
encryption, passwords on the wire in clear. Use only when the
target hardware has no other option.

= SSH and SFTP =

The SSH stack covers the full SSH-2 protocol (RFC 4251–4254,
RFC 5656, RFC 8709, RFC 8731) plus OpenSSH's chacha20-poly1305
transport cipher and the SFTP v3 file-transfer subsystem
(draft-ietf-secsh-filexfer-02). Two layers:

* '''<code>SSH::Client</code>''' — programmatic SSH access (remote
<code>exec</code>, TTY shell, agent forwarding, ProxyJump bastion).
* '''<code>SSH::SftpFilename</code>''' — a <code>Filename</code>
subclass that lets the rest of ST/X treat a remote SFTP path the
same way it treats a local file.

The rest of this section is organised user-task-first: what the user
sees and does, the expecco-library hooks below that, then the
implementation detail at the end for the curious.

== From the FileBrowserV2 ==

Open the location dropdown and paste an <code>sftp://</code> URL.
The browser tab populates as if it were a local path. Tree
expansion, column sort (name / size / mtime), preview, and
double-click-to-open-in-editor all behave normally. The first
click on a host takes ~200–500 ms (TCP + KEX + auth); subsequent
clicks reuse the pooled connection.

URL syntax:

<pre>
sftp://[user@]host[:port]/remote/path
</pre>

User defaults to the local login name, port to 22, path to
<code>/</code>.

The Tools menu offers three SSH-related actions, all gated on the
SSH library being loaded:

* '''Generate SSH Key Pair...''' — opens the same key-generation
dialog described under [[#Generating an SSH key pair]] below.
* '''SSH Connect...''' — opens an interactive VT100 terminal to a
remote host.
* '''SFTP Connect...''' — points this browser tab at a remote
filesystem via SFTP.

== From expecco actions ==

The Expecco RemoteAccess plugin
([[Expecco::RemoteAccessImportPlugin]]) exposes the following test
actions to the expecco action palette:

* '''CmdShell - Open SSH Remote Connection''' — opens an SSH session
via the platform's <code>ssh</code> binary (PuTTY's
<code>plink</code> on Windows).
* '''CmdShell - Open SSH Remote Connection and PublicKey''' — same
but with explicit public-key authentication.

To run these you need a configured keypair (private key on this
machine, public key in the remote host's
<code>~/.ssh/authorized_keys</code>). Generate one via the dialog
below or via <code>ssh-keygen</code>.

The plugin also adds a settings page at '''Extras → Settings →
Plugins → Remote Access — SSH Keys''' carrying a single
'''Generate SSH Key Pair...''' button that opens the same dialog.

== Generating an SSH key pair ==

=== The dialog (FileBrowserV2 / settings page) ===

The dialog asks for all parameters in one form:

* '''Comment''' — embedded in the generated key (defaults to
<code>stx@<hostname></code>).
* '''Storage''':
** ''Save to disk file only'' — writes <code>~/.ssh/id_ed25519_stx</code>
(or wherever) plus a matching <code>.pub</code> companion.
** ''Save to disk AND load into ssh-agent'' — writes the file and
also hands the key to the running ssh-agent.
** ''Load into ssh-agent only'' — key lives in agent memory only;
gone on agent restart.
* '''Private key file''' — full path; disabled in agent-only mode.
* '''Passphrase / Confirm''' — empty leaves the on-disk file
unencrypted (agent-only mode ignores the passphrase, since the
OpenSSH agent wire protocol carries only the decrypted key).

On '''Generate''', the public-key line (the same
<code>ssh-ed25519 AAAA... comment</code> string ssh-keygen
emits) is copied to the system clipboard for pasting into the
remote host's <code>~/.ssh/authorized_keys</code>.

=== From a workspace ===

For headless deployments, sandboxed builds, or scripts,
<code>SSH::Client</code> exposes a pure-Smalltalk key generator
that produces output bit-compatible with
<code>ssh-keygen -t ed25519</code>:

<pre>
| seed comment priv |
seed := SSH::Client generateEd25519Seed.
comment := 'stx@', OperatingSystem getHostName.

"/ Save passphrase-encrypted to disk"
priv := (Filename homeDirectory / '.ssh' / 'id_ed25519_stx') pathName.
SSH::Client
saveOpenSshEd25519Seed:seed
toFile:priv
comment:comment
passphrase:'choose-something-long'.

"/ AND load into the running agent"
SSH::Client addEd25519SeedToAgent:seed comment:comment.

"/ Print the public-key line to paste into authorized_keys"
Transcript showCR:
(SSH::Client authorizedKeysLineForEd25519Seed:seed comment:comment).
</pre>

Keys generated this way are interoperable with OpenSSH's own
tooling (<code>ssh-keygen -y -f ...</code> re-derives the public
key, <code>ssh-keygen -p -f ...</code> changes the passphrase,
etc.).

=== Using the shell tools instead ===

The traditional path also works:

<pre>
ssh-keygen -t ed25519 -C "stx@your.host"
ssh-copy-id user@remotehost
ssh-add ~/.ssh/id_ed25519
</pre>

== Preparing ssh-agent ==

The agent path is strongly preferred over reading raw keyfiles: it
keeps encrypted private keys unlocked once per session, and handles
identities (hardware-token-backed keys, KeePassXC entries) that
ST/X should never see directly.

ST/X picks the agent path automatically when
<code>$SSH_AUTH_SOCK</code> is set in the process environment
'''at the time stx is launched'''. Setting it later from a
workspace does not help.

=== Linux / macOS ===

Most desktop distributions launch an agent automatically as part of
the session (gnome-keyring on GNOME, ssh-agent.service on systemd,
KWallet on KDE). Verify in a terminal:

<pre>
echo $SSH_AUTH_SOCK # /run/user/1000/keyring/ssh or similar
ssh-add -l # lists loaded identities
ssh-add ~/.ssh/id_ed25519 # load yours if not loaded
</pre>

If no agent runs at all, add this snippet to your shell rc:

<pre>
# ~/.bashrc or ~/.zshrc
if [ -z "$SSH_AUTH_SOCK" ]; then
eval "$(ssh-agent -s)" > /dev/null
fi
</pre>

ST/X must be launched from a shell that has seen this rc — a
desktop launcher started from the file manager does NOT inherit
the variable. Wrap the stx start command in a small script under
<code>~/.local/bin/</code> that sources the rc first.

The Remote Access settings page ('''Extras → Settings → Plugins
→ Remote Access — SSH Keys''') shows whether the running image
sees an agent.

==== Permanent setup via systemd ====

For a truly cross-session agent (survives desktop logouts, comes
up automatically at next login), enable the per-user systemd
unit shipped with most distros' <code>openssh-clients</code>
package:

<pre>
systemctl --user enable --now ssh-agent.service
</pre>

Then point <code>SSH_AUTH_SOCK</code> at the user-service socket
in your shell rc (this replaces the <code>eval $(ssh-agent -s)</code>
snippet above):

<pre>
export SSH_AUTH_SOCK="${XDG_RUNTIME_DIR}/ssh-agent.socket"
</pre>

==== Auto-loading keys on first use ====

To skip the manual <code>ssh-add</code> step, let OpenSSH load
keys into the agent automatically the first time they are needed.
Add to <code>~/.ssh/config</code>:

<pre>
Host *
AddKeysToAgent yes
IdentityFile ~/.ssh/id_ed25519
</pre>

The first SSH connection then prompts for the key passphrase
once and hands the unlocked key to the agent; subsequent
connections use the cached identity without prompting.

=== Windows ===

Windows 10+ ships native OpenSSH including an agent service.
One-time setup:

# Open '''Services''' (<code>services.msc</code>) as Administrator.
# Find '''OpenSSH Authentication Agent''', set Startup Type to
'''Automatic''', click '''Start'''.
# In PowerShell: <code>ssh-add $HOME\.ssh\id_ed25519</code>.
# Verify: <code>ssh-add -l</code>.

The Windows OpenSSH agent listens on a named pipe
(<code>\\.\pipe\openssh-ssh-agent</code>), not a Unix socket. ST/X
supports both transports, but Windows ssh-add does '''not''' set
<code>SSH_AUTH_SOCK</code> for you. Add it manually:

# Press {{Key|Win}} → type "environment" → "Edit the system environment variables".
# '''Environment Variables''' → under '''User variables''', '''New'''.
# Name: <code>SSH_AUTH_SOCK</code>
# Value: <code>\\.\pipe\openssh-ssh-agent</code>
# Log out and back in (or restart stx) so the new env propagates.

==== PowerShell quick-setup ====

The same setup from an '''elevated''' PowerShell prompt, for
scripts or unattended provisioning:

<pre>
# Start the agent now AND on every reboot (permanent).
Set-Service -Name ssh-agent -StartupType Automatic
Start-Service ssh-agent

# Persist SSH_AUTH_SOCK for the user (survives reboots).
[Environment]::SetEnvironmentVariable(
'SSH_AUTH_SOCK',
'\\.\pipe\openssh-ssh-agent',
'User')

# Load a key (prompts for the passphrase if the file is encrypted).
ssh-add $HOME\.ssh\id_ed25519
</pre>

For a one-shot agent start without making it persistent (e.g.
single-session test), drop the <code>Set-Service</code> line and
just run <code>Start-Service ssh-agent</code>. The env-var line
can also be omitted if <code>SSH_AUTH_SOCK</code> is only needed
in the current shell — use <code>$env:SSH_AUTH_SOCK = '...'</code>
instead for that session-local form.

On stripped-down Windows installs the ssh-agent service may not
be present. Add it once via '''Settings → Apps → Optional
features → OpenSSH Client'''.

Alternative agents:

* '''PuTTY pageant''' — uses its own protocol; NOT supported by
ST/X's SSH::Agent. Migrate the keys to OpenSSH.
* '''Git for Windows ssh-agent''' — works; point
<code>SSH_AUTH_SOCK</code> at the socket it publishes.
* '''WSL 2''' — a ST/X inside WSL sees WSL's Linux agent normally;
a ST/X on the Windows side does not. Bridging needs a helper
like <code>npiperelay</code> + <code>socat</code>.

Verify in the Remote Access settings page
('''Extras → Settings → Plugins → Remote Access — SSH Keys''') —
the agent indicator there reports whether the running image sees
the agent.

==== Auto-loading keys on first use ====

Windows OpenSSH does '''not''' persist agent-loaded keys across
agent restarts. To avoid running <code>ssh-add</code> manually
after each reboot, add the same lazy-load configuration to
<code>%USERPROFILE%\.ssh\config</code>:

<pre>
Host *
AddKeysToAgent yes
IdentityFile ~/.ssh/id_ed25519
</pre>

OpenSSH then loads the key into the agent on first use (prompts
for the passphrase once) and reuses it for the rest of the
session.

== Configuration ==

All tunables are class-side on <code>SSH::SftpFilename</code>:

{| class="wikitable"
! Accessor !! Default !! What it controls
|-
| <code>#idleEvictionSeconds:</code> || 240 (4 min) || How long a pooled
connection sits idle before the next access proactively closes +
reopens it. Just under typical sshd
<code>ClientAliveInterval × ClientAliveCountMax</code> so we recycle
before the server TCP-RESETs us. Pass <code>nil</code> to restore
the default.
|-
| <code>#attrsCacheTtlSeconds:</code> || 5 || Max age (s) of a
cached STAT before <code>#ensureAttrs</code> refetches. Parent
listDir always re-stamps fresh attrs onto children, so navigating
an open directory does not pay the TTL. Set to <code>0</code> to
disable caching.
|-
| <code>#closeAllConnections</code> || (action) || Tears down every
pooled connection. Useful after a known-bad network event, before
a deliberate identity swap, or as part of a clean image shutdown.
|}

== Diagnostics ==

=== SemaphoreMonitor ===

Open <code>SemaphoreMonitor</code> from the Launcher's "Status"
sub-menu. Per-host SFTP mutex appears as
<code>SFTP/<user@host:port></code>; the pool-wide mutex as
<code>SFTP/pool</code>. Right-click a row:

* '''Copy Waiters Stack to Clipboard''' — dumps the last-owner's
walkback plus each waiter's, formatted as plain text. Use when
a process is wedged in <code>readWait</code> inside
<code>withSftpClientDo:</code> and you need to see which SFTP
request it is on.
* '''Copy List to Clipboard''' — the whole table, for an
email-this-to-someone diagnosis.
* '''Detect Deadlocks''' — DFS over the wait-for graph, reports
cycles.

=== Logger ===

The SSH stack logs interesting events:

* <code>warning:</code> on auto-reconnect after a dead connection.
* <code>warning:</code> when a pool entry is idle-evicted.
* <code>warning:</code> when an SSH key file cannot be parsed
(e.g. legacy PEM, encrypted-without-agent) — the file is skipped,
others tried.

== Limitations ==

* '''SFTP v3 only.''' No SETSTAT (no remote chmod / chown / utime),
no SSH_FXP_READLINK exposed (<code>#isSymbolicLink</code> always
<code>false</code>, <code>#linkInfo</code> returns the regular
stat info). SFTPv5+ features (atomic-overwrite rename via
<code>SSH_FXF_OVERWRITE</code>) not supported.
* '''Per-host serialisation.''' Two concurrent operations on the
same host queue through the host mutex. See [[#Future work]].
* '''<code>#renameTo:</code> has a TOCTOU window.''' POSIX-style
overwrite is emulated as delete-then-rename; another process can
race in between.
* '''<code>#isNonEmptyDirectory</code> is heuristic.''' Always
returns <code>#isDirectory</code> (the accurate answer would cost
three round-trips per directory icon, which made the original tree
expansion unbearably slow).

== Implementation details ==

For readers wanting the architecture. Five classes, top-down:

{| class="wikitable"
! Class !! Role
|-
| <code>SSH::SftpFilename</code> || Filename subclass; the public
API. Maps <code>sftp://...</code> URLs to remote files; exposes
<code>directoryContents</code>, <code>readingFileDo:</code>,
<code>renameTo:</code> etc.
|-
| <code>SSH::SftpClient</code> || SFTP-v3 protocol
(request/response codec, listDir, stat, open, read, write, mkdir).
Driven by SftpFilename.
|-
| <code>SSH::Channel</code> || SSH channel multiplexer
(CHANNEL_OPEN, DATA, EOF, CLOSE, WINDOW_ADJUST). One logical
session per Channel instance.
|-
| <code>SSH::Client</code> || High-level SSH client: opens the
transport, runs KEX, host-key check, userauth, then dispenses
Channels.
|-
| <code>SSH::Transport</code> || Wire layer. Banner + KEXINIT
exchange, ChaCha20-Poly1305 packet framing, sendSeq / recvSeq,
heartbeat, SSH_MSG_DISCONNECT.
|}

=== Connection pooling ===

Every <code>SftpFilename</code> instance pointing at the same
<code>user@host:port</code> triple shares one
<code>SSH::Client</code> plus one <code>SSH::SftpClient</code>.
Pool is class-side, guarded by a single
<code>ConnectionPoolMutex</code>:

* '''Lazy bring-up''' — TCP + KEX + userauth + SFTP INIT happens
on the first SFTP operation, not on <code>forUrl:</code>.
* '''Per-host serialisation''' — SFTP requests on a given host
are serialised through a <code>RecursionLock</code> named
<code>SFTP/<user@host:port></code> (visible in
SemaphoreMonitor).
* '''Idle eviction''' — unused for longer than
<code>idleEvictionSeconds</code>, the entry is proactively
closed + reopened on the next access.
* '''Auto-reconnect''' — a transport-level failure (broken pipe,
EOF, MNU on nil socket) evicts the dead pool entry, opens a
fresh client, retries the request '''once'''. Application-level
SFTP STATUS errors propagate immediately.

== Future work ==

Tracked but not yet implemented:

* '''Multi-channel parallelism per host''' — today one TCP +
one SFTP channel per host means N concurrent requests
serialise. Pipelining over multiple SshClients in the pool
(preferred), or a transport-level reader process demultiplexing
to per-channel inboxes, would let the tree pane keep listing
while the content pane reads a large file.
* '''Accurate <code>#isNonEmptyDirectory</code>''' via OPEN_DIR
+ READ_DIR (first batch only) + CLOSE — three RTTs per probe;
needs SftpClient to pipeline requests before this pays off.
* '''SFTP v5/v6 negotiation''' for atomic-overwrite rename,
extended attrs, FTP-style canonicalisation.

= Command Shell =

Local command shell on this expecco machine. Typical applications:
local command-line, running a local helper tool, bridging a
remote workflow to a local utility.

The Expecco RemoteAccess plugin exposes:

* '''CmdShell - Open'''
* '''CmdShell - Close'''

No credentials, no network — runs as the expecco process's own
user. Output streams to expecco's log.

= Telnet =

[[File:Warning.svg|24px|Warning]] '''Telnet is a legacy protocol
with no encryption.''' Passwords are transmitted in plain text on
the wire; anyone on the network path can read them. Use Telnet
ONLY when the target device has no other option (typically: old
industrial controllers, lab instruments, embedded measurement
equipment without an SSH stack). For everything else use
[[#SSH and SFTP]].

The expecco plugin exposes:

* '''Telnet - Open Remote Connection With Login'''
* '''Telnet - Execute Remote Command'''
* '''Example - Remote Device Control via Telnet''' (internal demo)

The Telnet protocol (RFC 854) is a bidirectional 8-bit byte stream
over TCP, with in-band control sequences for terminal options.
A connection is established to a target host:port; after optional
in-band login, both sides can send data.

= See also =

* [[SSH Client/en|SSH::Client]] — the SSH layer (exec, TTY, agent
forwarding, ProxyJump).
* [[FileBrowserV2/en|FileBrowserV2]] — the main UI client of
this stack.
* [[ClaudeCode plugin/en|Claude Code]] — uses the same SSH stack
for its HTTPS transport.
* [[Wikipedia:Secure Shell|RFC 4251 (SSH-2 Architecture)]]
* [[Wikipedia:Telnet|RFC 854 (Telnet Protocol)]]

[[Category:Plugins]]
[[Category:Network]]
[[Category:SSH]]

Remote Access/

2026-05-26T08:46:04Z

Die Seite wurde neu angelegt: „'''Fernzugriff''' bezeichnet die Möglichkeit, einen entfernten Rechner oder ein entferntes Netzwerk aus diesem expecco-Image heraus zu bedienen — Shells zu öffnen, Befehle abzusetzen, Dateien zu verschieben oder ein Testgerät anzusteuern. Drei Protokoll-Familien sind unterstützt, in absteigender Empfehlungsreihenfolge: * '''SSH und SFTP''' (empfohlen) — verschlüsselte Shell und sichere Dateiübertragung über einen SSH-2-Tunnel. Reine Smal…“

Neue Seite

'''Fernzugriff''' bezeichnet die Möglichkeit, einen entfernten
Rechner oder ein entferntes Netzwerk aus diesem expecco-Image heraus
zu bedienen — Shells zu öffnen, Befehle abzusetzen, Dateien zu
verschieben oder ein Testgerät anzusteuern. Drei Protokoll-Familien
sind unterstützt, in absteigender Empfehlungsreihenfolge:

* '''SSH und SFTP''' (empfohlen) — verschlüsselte Shell und sichere
Dateiübertragung über einen SSH-2-Tunnel. Reine
Smalltalk-Implementierung in <code>exept:libcrypt/ssh</code>;
keine externe Abhängigkeit von OpenSSL oder libssh. Für alles
mit Zugangsdaten oder sensiblen Nutzdaten.
* '''Lokale Kommando-Shell''' — fork + exec auf der lokalen
Maschine. Für die Anbindung lokaler Werkzeuge und für die
lokale Seite eines hybriden Workflows.
* '''Telnet''' (veraltet) — Klartext-Terminalsitzung. Keine
Verschlüsselung, Passwörter im Klartext auf der Leitung. Nur
einsetzen, wenn die Gegenstelle keine Alternative bietet.

= SSH und SFTP =

Der SSH-Stack deckt das vollständige SSH-2-Protokoll ab
(RFC 4251–4254, RFC 5656, RFC 8709, RFC 8731) inklusive der
chacha20-poly1305-Transportchiffrierung von OpenSSH sowie das
SFTP-v3-Subsystem (draft-ietf-secsh-filexfer-02). Zwei Schichten:

* '''<code>SSH::Client</code>''' — programmatischer SSH-Zugriff
(entferntes <code>exec</code>, TTY-Shell, Agent-Weiterleitung,
ProxyJump-Bastion).
* '''<code>SSH::SftpFilename</code>''' — eine
<code>Filename</code>-Unterklasse, die es dem restlichen ST/X
erlaubt, einen entfernten SFTP-Pfad zu behandeln wie eine lokale
Datei.

Die folgenden Abschnitte sind nutzeraufgaben-zuerst aufgebaut:
zuerst das, was der Anwender sieht und tut, darunter die
expecco-Bibliotheks-Anbindung, ganz unten Implementierungsdetails
für Interessierte.

== Aus dem FileBrowserV2 ==

Im Adress-Dropdown eine <code>sftp://</code>-URL einfügen. Der
Browser-Tab füllt sich wie bei einem lokalen Pfad.
Baum-Ausklappen, Spaltensortierung (Name / Größe / mtime),
Vorschau und Doppelklick zum Öffnen im Editor verhalten sich
normal. Der erste Klick auf einen Host dauert ~200–500 ms
(TCP + KEX + Auth); folgende Klicks nutzen die gepoolte
Verbindung weiter.

URL-Syntax:

<pre>
sftp://[user@]host[:port]/remote/path
</pre>

Fehlt <code>user</code>, wird der lokale Login-Name verwendet, Port
ist standardmäßig 22, Pfad standardmäßig <code>/</code>.

Das Menü '''Tools''' im FileBrowserV2 bietet drei SSH-Aktionen,
sichtbar nur bei geladener SSH-Bibliothek:

* '''Generate SSH Key Pair...''' — öffnet den
Schlüsselerzeugungs-Dialog, siehe
[[#Einen SSH-Schlüssel erzeugen]] unten.
* '''SSH Connect...''' — öffnet ein interaktives VT100-Terminal
zu einem entfernten Host.
* '''SFTP Connect...''' — navigiert diesen Browser-Tab über SFTP
auf ein entferntes Dateisystem.

== Aus expecco-Aktionen ==

Das Expecco-RemoteAccess-Plugin
([[Expecco::RemoteAccessImportPlugin]]) stellt folgende Testaktionen
in der expecco-Aktionspalette bereit:

* '''CmdShell - Open SSH Remote Connection''' — öffnet eine
SSH-Sitzung über das plattformeigene <code>ssh</code>-Binary
(PuTTYs <code>plink</code> unter Windows).
* '''CmdShell - Open SSH Remote Connection and PublicKey''' —
dasselbe, jedoch mit expliziter Public-Key-Authentifizierung.

Voraussetzung: ein eingerichtetes Schlüsselpaar (privater
Schlüssel auf dieser Maschine, öffentlicher Teil in der
<code>~/.ssh/authorized_keys</code> des Zielhosts). Schlüssel
erzeugen entweder über den Dialog unten oder über
<code>ssh-keygen</code>.

Das Plugin fügt zusätzlich eine Settings-Seite hinzu:
'''Extras → Settings → Plugins → Remote Access — SSH Keys''' mit
einer einzelnen Schaltfläche '''Generate SSH Key Pair...''', die
denselben Dialog öffnet.

== Einen SSH-Schlüssel erzeugen ==

=== Der Dialog (FileBrowserV2 / Settings-Seite) ===

Der Dialog fragt alle Parameter in einem Formular ab:

* '''Comment''' — wird in den erzeugten Schlüssel eingebettet
(Voreinstellung <code>stx@<hostname></code>).
* '''Storage''':
** ''Save to disk file only'' — schreibt
<code>~/.ssh/id_ed25519_stx</code> (oder wohin man will) samt
zugehöriger <code>.pub</code>-Datei daneben.
** ''Save to disk AND load into ssh-agent'' — schreibt die Datei
UND übergibt den Schlüssel dem laufenden ssh-agent.
** ''Load into ssh-agent only'' — der Schlüssel lebt nur im
Speicher des Agents; nach Agent-Neustart ist er verloren.
* '''Private key file''' — vollständiger Pfad; ausgegraut im
Agent-only-Modus.
* '''Passphrase / Confirm''' — leer lässt die On-Disk-Datei
unverschlüsselt (Agent-only-Modus ignoriert die Passphrase, da
das OpenSSH-Agent-Wire-Protokoll nur den entschlüsselten
Schlüssel transportiert).

Bei '''Generate''' wird die Public-Key-Zeile (dieselbe
<code>ssh-ed25519 AAAA... comment</code>-Zeichenfolge, die
ssh-keygen ausgibt) in die System-Zwischenablage kopiert — zum
direkten Einfügen in die <code>~/.ssh/authorized_keys</code> des
Zielhosts.

=== Aus einem Workspace ===

Für Headless-Deployments, Sandbox-Builds oder Skripte stellt
<code>SSH::Client</code> einen reinen Smalltalk-Schlüsselgenerator
bereit, dessen Ausgabe bit-kompatibel zu
<code>ssh-keygen -t ed25519</code> ist:

<pre>
| seed comment priv |
seed := SSH::Client generateEd25519Seed.
comment := 'stx@', OperatingSystem getHostName.

"/ Passphrase-verschlüsselt auf Platte speichern"
priv := (Filename homeDirectory / '.ssh' / 'id_ed25519_stx') pathName.
SSH::Client
saveOpenSshEd25519Seed:seed
toFile:priv
comment:comment
passphrase:'choose-something-long'.

"/ UND in den laufenden Agent laden"
SSH::Client addEd25519SeedToAgent:seed comment:comment.

"/ Public-Key-Zeile zum Einfügen in authorized_keys ausgeben"
Transcript showCR:
(SSH::Client authorizedKeysLineForEd25519Seed:seed comment:comment).
</pre>

Die so erzeugten Schlüssel sind mit den OpenSSH-Werkzeugen voll
interoperabel (<code>ssh-keygen -y -f ...</code> rekonstruiert den
öffentlichen Schlüssel, <code>ssh-keygen -p -f ...</code> ändert
die Passphrase usw.).

=== Mit den Shell-Werkzeugen ===

Der klassische Weg funktioniert weiterhin:

<pre>
ssh-keygen -t ed25519 -C "stx@your.host"
ssh-copy-id user@remotehost
ssh-add ~/.ssh/id_ed25519
</pre>

== ssh-agent vorbereiten ==

Der Weg über den Agent ist dem direkten Lesen von Schlüsseldateien
deutlich vorzuziehen: er hält verschlüsselte private Schlüssel
einmal pro Sitzung entsperrt und kann Identitäten verwalten
(hardware-tokengestützte Schlüssel, KeePassXC-Einträge), die ST/X
nie direkt sehen soll.

ST/X erkennt den Agent-Pfad automatisch, sobald
<code>$SSH_AUTH_SOCK</code> '''zum Zeitpunkt des Starts von stx'''
in der Prozessumgebung gesetzt ist. Eine spätere Zuweisung aus
einem Workspace nützt nichts.

=== Linux / macOS ===

Die meisten Desktop-Distributionen starten einen Agent automatisch
beim Login (gnome-keyring unter GNOME, ssh-agent.service unter
systemd, KWallet unter KDE). Prüfen im Terminal:

<pre>
echo $SSH_AUTH_SOCK # /run/user/1000/keyring/ssh oder ähnlich
ssh-add -l # listet geladene Identitäten
ssh-add ~/.ssh/id_ed25519 # eigene laden, falls nicht da
</pre>

Läuft gar kein Agent, dieses Snippet in die Shell-rc-Datei
aufnehmen:

<pre>
# ~/.bashrc oder ~/.zshrc
if [ -z "$SSH_AUTH_SOCK" ]; then
eval "$(ssh-agent -s)" > /dev/null
fi
</pre>

ST/X muss aus einer Shell gestartet werden, die diese rc bereits
gelesen hat — ein Desktop-Launcher aus dem Dateimanager erbt die
Variable nicht. Empfehlung: ein kleines Wrapper-Skript unter
<code>~/.local/bin/</code>, das die rc sourcet und dann stx
startet.

Die Settings-Seite ('''Extras → Settings → Plugins → Remote
Access — SSH Keys''') zeigt an, ob das laufende Image einen
Agent sieht.

==== Permanente Einrichtung via systemd ====

Für einen wirklich sitzungsübergreifenden Agent (überlebt Desktop-
Abmeldung, kommt beim nächsten Login wieder hoch) die bei den
meisten Distros mit dem Paket <code>openssh-clients</code>
ausgelieferte Per-User-systemd-Unit aktivieren:

<pre>
systemctl --user enable --now ssh-agent.service
</pre>

Anschließend <code>SSH_AUTH_SOCK</code> in der Shell-rc auf den
User-Service-Socket zeigen lassen (ersetzt das
<code>eval $(ssh-agent -s)</code>-Snippet oben):

<pre>
export SSH_AUTH_SOCK="${XDG_RUNTIME_DIR}/ssh-agent.socket"
</pre>

==== Schlüssel automatisch beim ersten Einsatz laden ====

Um den manuellen <code>ssh-add</code>-Schritt zu sparen, kann
OpenSSH Schlüssel beim ersten Bedarf selbst in den Agent laden.
In <code>~/.ssh/config</code> eintragen:

<pre>
Host *
AddKeysToAgent yes
IdentityFile ~/.ssh/id_ed25519
</pre>

Die erste SSH-Verbindung fragt dann einmal nach der Passphrase und
übergibt den entsperrten Schlüssel an den Agent; weitere
Verbindungen nutzen die gespeicherte Identität ohne Prompt.

=== Windows ===

Windows 10+ bringt das native OpenSSH inklusive Agent-Dienst mit.
Einmalige Einrichtung:

# '''Dienste''' (<code>services.msc</code>) als Administrator öffnen.
# '''OpenSSH Authentication Agent''' suchen, Starttyp auf
'''Automatisch''' setzen, '''Starten''' anklicken.
# In PowerShell: <code>ssh-add $HOME\.ssh\id_ed25519</code>.
# Prüfen: <code>ssh-add -l</code>.

Der Windows-OpenSSH-Agent lauscht auf einer Named Pipe
(<code>\\.\pipe\openssh-ssh-agent</code>), nicht auf einem
Unix-Socket. ST/X unterstützt beide Transporte, jedoch setzt das
Windows-ssh-add <code>SSH_AUTH_SOCK</code> '''nicht''' selbst.
Daher einmalig systemweit setzen:

# {{Key|Win}} drücken → "Umgebungsvariablen" → „Systemumgebungs-
variablen bearbeiten".
# '''Umgebungsvariablen''' → unter '''Benutzervariablen''',
'''Neu''' klicken.
# Name: <code>SSH_AUTH_SOCK</code>
# Wert: <code>\\.\pipe\openssh-ssh-agent</code>
# Ab- und wieder anmelden (oder stx neu starten), damit die neue
Umgebung übernommen wird.

==== PowerShell-Schnelleinrichtung ====

Derselbe Aufbau aus einer '''Administrator-PowerShell''' heraus,
z.B. für Skripte oder unbeaufsichtigte Bereitstellung:

<pre>
# Agent jetzt und bei jedem Neustart starten (permanent).
Set-Service -Name ssh-agent -StartupType Automatic
Start-Service ssh-agent

# SSH_AUTH_SOCK dauerhaft für den Benutzer setzen (übersteht Reboots).
[Environment]::SetEnvironmentVariable(
'SSH_AUTH_SOCK',
'\\.\pipe\openssh-ssh-agent',
'User')

# Schlüssel laden (fragt nach Passphrase, falls die Datei verschlüsselt ist).
ssh-add $HOME\.ssh\id_ed25519
</pre>

Für einen einmaligen Agent-Start ohne dauerhafte Aktivierung
(z.B. Einzelsitzung) die <code>Set-Service</code>-Zeile weglassen
und nur <code>Start-Service ssh-agent</code> ausführen. Die
env-var-Zeile lässt sich ebenfalls weglassen, wenn
<code>SSH_AUTH_SOCK</code> nur in der aktuellen Shell gebraucht
wird — dann statt der <code>[Environment]</code>-Variante
<code>$env:SSH_AUTH_SOCK = '...'</code> verwenden.

Auf stark abgespeckten Windows-Installationen ist der
ssh-agent-Dienst eventuell nicht vorhanden. Einmalig nachrüsten
über '''Einstellungen → Apps → Optionale Features → OpenSSH-
Client'''.

Alternative Agenten:

* '''PuTTY pageant''' — eigenes Protokoll; von ST/X's
<code>SSH::Agent</code> '''nicht''' unterstützt. Schlüssel zu
OpenSSH migrieren.
* '''Git für Windows ssh-agent''' — funktioniert;
<code>SSH_AUTH_SOCK</code> auf den dort veröffentlichten Socket
zeigen lassen.
* '''WSL 2''' — ein ST/X innerhalb der WSL sieht den WSL-eigenen
Agent normal; ein ST/X auf der Windows-Seite nicht. Eine
Brücke per <code>npiperelay</code> + <code>socat</code> ist
möglich.

Prüfung über die Settings-Seite
('''Extras → Settings → Plugins → Remote Access — SSH Keys''') —
die Anzeige dort meldet, ob das laufende Image den Agent sieht.

==== Schlüssel automatisch beim ersten Einsatz laden ====

Windows-OpenSSH speichert agent-geladene Schlüssel '''nicht'''
über Agent-Neustarts hinweg. Um nicht nach jedem Reboot manuell
<code>ssh-add</code> aufrufen zu müssen, dieselbe Lazy-Load-
Konfiguration in <code>%USERPROFILE%\.ssh\config</code>
eintragen:

<pre>
Host *
AddKeysToAgent yes
IdentityFile ~/.ssh/id_ed25519
</pre>

OpenSSH lädt den Schlüssel dann beim ersten Einsatz in den Agent
(fragt einmal nach der Passphrase) und nutzt ihn für die übrige
Sitzung weiter.

== Konfiguration ==

Alle Stellschrauben sind klassenseitig auf
<code>SSH::SftpFilename</code> erreichbar:

{| class="wikitable"
! Accessor !! Voreinstellung !! Steuert
|-
| <code>#idleEvictionSeconds:</code> || 240 (4 Min) || Wie lange
eine gepoolte Verbindung im Leerlauf liegen darf, bevor sie beim
nächsten Zugriff proaktiv geschlossen und neu geöffnet wird.
Liegt knapp unter dem typischen
<code>ClientAliveInterval × ClientAliveCountMax</code> des sshd,
damit wir uns recyceln, bevor der Server uns mit TCP-RESET
trennt. <code>nil</code> setzt auf Voreinstellung zurück.
|-
| <code>#attrsCacheTtlSeconds:</code> || 5 || Maximales Alter (s)
eines gecachten STAT, bevor <code>#ensureAttrs</code> neu am
Server fragt. Eltern-listDir stempelt ohnehin frische Attribute
auf alle Kinder, daher zahlt das Navigieren im offenen
Verzeichnis das TTL nicht. <code>0</code> schaltet den Cache
ab.
|-
| <code>#closeAllConnections</code> || (Aktion) || Reißt jede
gepoolte Verbindung ab. Nützlich nach einem bekannt schlechten
Netzereignis, vor einem bewussten Identitätswechsel oder zum
sauberen Image-Shutdown.
|}

== Diagnose ==

=== SemaphoreMonitor ===

<code>SemaphoreMonitor</code> über das Untermenü „Status" des
Launchers öffnen. Der pro-Host-SFTP-Mutex erscheint als
<code>SFTP/<user@host:port></code>, der pool-weite Mutex als
<code>SFTP/pool</code>. Per Rechtsklick:

* '''Copy Waiters Stack to Clipboard''' — schreibt den Walkback
des letzten Eigners samt aller Waiter als Text in die
Zwischenablage. Unverzichtbar, wenn ein Prozess in
<code>readWait</code> innerhalb von
<code>withSftpClientDo:</code> klemmt.
* '''Copy List to Clipboard''' — die ganze Tabelle, ideal für eine
E-Mail-Diagnose.
* '''Detect Deadlocks''' — DFS über den Wait-for-Graph, meldet
Zyklen.

=== Logger ===

Interessante Ereignisse werden über <code>Logger</code> geloggt:

* <code>warning:</code> bei automatischem Reconnect nach toter
Verbindung.
* <code>warning:</code> bei Idle-Verdrängung eines Pool-Eintrags.
* <code>warning:</code> wenn eine SSH-Schlüsseldatei nicht
geparst werden konnte — die Datei wird übersprungen.

== Einschränkungen ==

* '''Nur SFTP v3.''' Kein SETSTAT (kein entferntes
chmod / chown / utime), kein SSH_FXP_READLINK exponiert
(<code>#isSymbolicLink</code> liefert immer <code>false</code>,
<code>#linkInfo</code> die normale stat-Info). SFTPv5+-Features
(atomares Überschreibungs-rename via
<code>SSH_FXF_OVERWRITE</code>) werden nicht unterstützt.
* '''Serialisierung pro Host.''' Zwei gleichzeitige Operationen
am selben Host stehen am Host-Mutex an. Siehe [[#Ausblick]].
* '''<code>#renameTo:</code> hat ein TOCTOU-Fenster.'''
POSIX-typisches Überschreiben wird als Delete-dann-Rename
emuliert; ein anderer Prozess kann sich dazwischenschieben.
* '''<code>#isNonEmptyDirectory</code> ist eine Heuristik.'''
Liefert immer <code>#isDirectory</code> (die genaue Antwort
würde drei Roundtrips pro Verzeichnis-Symbol kosten, was das
ursprüngliche Baum-Ausklappen unerträglich gebremst hatte).

== Implementierungsdetails ==

Für Leser, die die Architektur verstehen wollen. Fünf Klassen,
von oben nach unten:

{| class="wikitable"
! Klasse !! Aufgabe
|-
| <code>SSH::SftpFilename</code> || Filename-Unterklasse, die
öffentliche API. Bildet <code>sftp://...</code>-URLs auf
entfernte Dateien ab und stellt <code>directoryContents</code>,
<code>readingFileDo:</code>, <code>renameTo:</code> usw. bereit.
|-
| <code>SSH::SftpClient</code> || SFTP-v3-Protokoll
(Request/Response-Codec, listDir, stat, open, read, write, mkdir).
Wird von SftpFilename angesteuert.
|-
| <code>SSH::Channel</code> || SSH-Kanal-Multiplexer (CHANNEL_OPEN,
DATA, EOF, CLOSE, WINDOW_ADJUST). Eine logische Sitzung pro
Channel-Instanz.
|-
| <code>SSH::Client</code> || High-Level-SSH-Client: öffnet den
Transport, führt KEX, Hostschlüssel-Prüfung und userauth durch und
verteilt anschließend Kanäle.
|-
| <code>SSH::Transport</code> || Drahtschicht. Banner- und
KEXINIT-Austausch, ChaCha20-Poly1305-Paket-Framing, sendSeq /
recvSeq, Heartbeat, SSH_MSG_DISCONNECT.
|}

=== Verbindungs-Pooling ===

Alle <code>SftpFilename</code>-Instanzen, die auf dasselbe Tripel
<code>user@host:port</code> zeigen, teilen sich einen
<code>SSH::Client</code> samt einem <code>SSH::SftpClient</code>.
Der Pool ist klassenseitig und wird von einem einzigen
<code>ConnectionPoolMutex</code> bewacht:

* '''Lazy-Aufbau''' — TCP + KEX + userauth + SFTP-INIT laufen
erst beim ersten SFTP-Aufruf, nicht in <code>forUrl:</code>.
* '''Serialisierung pro Host''' — SFTP-Anfragen an einen
bestimmten Host werden durch einen <code>RecursionLock</code>
mit dem Namen <code>SFTP/<user@host:port></code>
serialisiert (sichtbar im SemaphoreMonitor).
* '''Idle-Verdrängung''' — ein Pool-Eintrag, der länger als
<code>idleEvictionSeconds</code> ungenutzt liegt, wird beim
nächsten Zugriff proaktiv geschlossen und neu geöffnet.
* '''Automatischer Reconnect''' — ein Fehler auf Transportebene
(Broken Pipe, EOF, MNU auf nil-Socket) verdrängt den
Pool-Eintrag, öffnet einen frischen Client und wiederholt die
Anfrage '''einmal'''. Anwendungsfehler aus
SFTP-STATUS-Antworten werden sofort durchgereicht.

== Ausblick ==

Geplant, aber noch nicht umgesetzt:

* '''Multi-Channel-Parallelität pro Host''' — aktuell bedeutet
eine TCP- plus eine SFTP-Verbindung pro Host, dass N
gleichzeitige Anfragen serialisieren. Pipelining über mehrere
SshClients im Pool (bevorzugt) oder ein transport-seitiger
Reader-Prozess, der eingehende Pakete in
Pro-Kanal-Postfächer demultiplext, würde es dem Baum-Panel
erlauben, weiter aufzulisten, während das Inhalts-Panel eine
große Datei liest.
* '''Genaues <code>#isNonEmptyDirectory</code>''' via OPEN_DIR
+ READ_DIR (nur erstes Batch) + CLOSE — drei Roundtrips pro
Sondierung; lohnt erst, wenn der SftpClient Anfragen pipelinen
kann.
* '''SFTP-v5/v6-Aushandlung''' für atomares Überschreibungs-
rename, erweiterte Attribute und FTP-artige Kanonisierung.

= Kommando-Shell =

Lokale Kommando-Shell auf dieser expecco-Maschine. Typische
Anwendungen: lokale Kommandozeile, lokales Hilfsprogramm,
Brücke zwischen entferntem Workflow und lokalem Tool.

Das RemoteAccess-Plugin stellt bereit:

* '''CmdShell - Open'''
* '''CmdShell - Close'''

Keine Zugangsdaten, kein Netzwerk — läuft als der Benutzer des
expecco-Prozesses. Ausgaben gehen in das expecco-Log.

= Telnet =

[[File:Warning.svg|24px|Warnung]] '''Telnet ist ein veraltetes
Protokoll ohne Verschlüsselung.''' Passwörter werden im Klartext
über die Leitung übertragen; jeder im Netzpfad kann sie lesen.
Telnet NUR einsetzen, wenn die Gegenstelle keine Alternative
bietet (typisch: alte Industriesteuerungen, Laborgeräte,
eingebettete Messgeräte ohne SSH-Stack). Für alles andere
[[#SSH und SFTP]] verwenden.

Das expecco-Plugin stellt bereit:

* '''Telnet - Open Remote Connection With Login'''
* '''Telnet - Execute Remote Command'''
* '''Example - Remote Device Control via Telnet''' (interne Demo)

Das Telnet-Protokoll (RFC 854) ist ein bidirektionaler
8-Bit-Byte-Strom über TCP, mit In-Band-Steuersequenzen für
Terminal-Optionen. Verbindungsaufbau zum Ziel-Host:Port; nach
optionalem In-Band-Login können beide Seiten Daten senden.

= Siehe auch =

* [[SSH Client|SSH::Client]] — die SSH-Schicht (exec, TTY,
Agent-Weiterleitung, ProxyJump).
* [[FileBrowserV2]] — die Haupt-UI dieses Stacks.
* [[ClaudeCode plugin|Claude Code]] — nutzt denselben SSH-Stack
als HTTPS-Transport.
* [[Wikipedia:Secure Shell|RFC 4251 (SSH-2 Architecture)]]
* [[Wikipedia:Telnet|RFC 854 (Telnet Protocol)]]

[[Category:Plugins]]
[[Category:Netz]]
[[Category:SSH]]

Remote Access

2026-05-26T08:44:55Z

Native SSH/SFTP

Änderungen zeigen

Hauptseite

2026-05-26T07:27:38Z

← Nächstältere Version		Version vom 26. Mai 2026, 07:27 Uhr
Zeile 85:		Zeile 85:
	<li>[[Schnittstellen zum SUT]]</li>		<li>[[Schnittstellen zum SUT]]</li>
	<li>[[ManualTest]]</li>		<li>[[ManualTest]]</li>
			<li>[[Remote Access\|<b>NEU: native SSH/SFTP</b> Remote Access via SSH/telnet]]
	<li>Produktivität		<li>Produktivität
	<ul>		<ul>

Installing additional Frameworks/en

2026-05-25T14:45:12Z

AI (Tensorflow)

← Nächstältere Version		Version vom 25. Mai 2026, 14:45 Uhr
(2 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 421:		Zeile 421:

	== AI (Tensorflow) ==		== AI (Tensorflow) ==
	These are typically used via Python actions, and installed using a Python package manager (eg. "pip install tensorflow"). Please refer to Tensorflow web pages for details.		These are typically used via Python actions, and installed using a Python package manager (eg. "pip install tensorflow").<br>Please refer to Tensorflow web pages for details.

	== AI (Ollama) ==		== AI (Ollama) ==
	Goto [https://ollama.com/download ollama.com/download] and get the installer for your operating system. The loaded Setup/Install procedure should install ollama on your local machine as a background service.<br>It will also open an Ollama interactive chat and configuration window, which is not needed in the future, but will be useful to verify that the installation worked and especially to download new models.		Goto [https://ollama.com/download ollama.com/download] and get the installer for your operating system. The loaded Setup/Install procedure should install ollama on your local machine as a background service.<br>It will also open an Ollama interactive chat and configuration window, which is not needed in the future, but will be useful to verify that the installation worked and especially to download new models.
	<br>Models to consider: we tried qwen3.6, gemma4 and [https://ollama.com/library/codellama:7b codellama]. We are currently investigating which model is best suited for our AI tasks, but tend to codellama (if you prefer a free model running on your local machine).<br>Models are to be placed into the ''Model Location'' folder, which is found in the Ollama window under ''Settings''.		<br>Models are to be placed into the ''Model Location'' folder, which is found in the Ollama window under ''Settings''.
	<br>You can also pull models with "<CODE>ollama pull <modelName></CODE>" or "<CODE>ollama run <modelName></CODE>". On Windows, the ollama command is typically found in your personal "<CODE>AppData\Local\Programs\Ollama</CODE>" folder.		<br>You can also pull models with "<CODE>ollama pull <modelName></CODE>" or "<CODE>ollama run <modelName></CODE>". On Windows, the ollama command is typically found in your personal "<CODE>AppData\Local\Programs\Ollama</CODE>" folder.

			Models to consider (as of May 2026): we tried qwen3.6, gemma4 and [https://ollama.com/library/codellama:7b codellama]. We are currently investigating which model is best suited for our AI tasks, but tend to codellama (if you prefer a free model running on your local machine).
			<br>Be aware that models are huge, typically in the order of tens of gigabytes.

KI Coding Plugin

2026-05-25T14:27:19Z

KI Coding Plugin

← Nächstältere Version		Version vom 25. Mai 2026, 14:27 Uhr
Zeile 9:		Zeile 9:
	* '''Anthropic Claude''' (claude-opus-4-7, claude-sonnet-4-6, claude-haiku-4-5)		* '''Anthropic Claude''' (claude-opus-4-7, claude-sonnet-4-6, claude-haiku-4-5)
	* '''OpenAI ChatGPT''' (gpt-4o, gpt-4o-mini, gpt-4.1, gpt-4.1-mini, gpt-4.1-nano, o1, o3)		* '''OpenAI ChatGPT''' (gpt-4o, gpt-4o-mini, gpt-4.1, gpt-4.1-mini, gpt-4.1-nano, o1, o3)
			* '''Ollama''' (codellama:7b, codellama:13b)

	Je nach gewähltem Anbieter erscheint die Toolbar-Schaltfläche als		Je nach gewähltem Anbieter erscheint die Toolbar-Schaltfläche als
	'''"Ask Claude"''' bzw. '''"Ask ChatGPT"'''; das Einstellungs-Tab		'''"Ask Claude"''' bzw. '''"Ask ChatGPT"'''; das Einstellungs-Tab

Installing additional Frameworks/en

2026-05-25T14:25:06Z

AI (Ollama)

← Nächstältere Version		Version vom 25. Mai 2026, 14:25 Uhr
(2 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 421:		Zeile 421:

	== AI (Tensorflow) ==		== AI (Tensorflow) ==
	These are typically used via Python actions, and installed using a Python package manager (pip). Please refer to Tensorflow web pages for details.		These are typically used via Python actions, and installed using a Python package manager (eg. "pip install tensorflow"). Please refer to Tensorflow web pages for details.

	== AI (Ollama) ==		== AI (Ollama) ==
	Goto [https://ollama.com/download ollama.com/download] and get the installer for your operating system. The loaded Setup/Install procedure should install ollama on your local machine as a background service.<br>It will also open an Ollama interactive chat and configuration window, which is not needed in the future, but will be useful to verify that the installation worked and especially to download new models.		Goto [https://ollama.com/download ollama.com/download] and get the installer for your operating system. The loaded Setup/Install procedure should install ollama on your local machine as a background service.<br>It will also open an Ollama interactive chat and configuration window, which is not needed in the future, but will be useful to verify that the installation worked and especially to download new models.
	<br>Models to consider: we tried qwen3.6, gemma4 and [https://ollama.com/library/codellama:7b codellama]. We are currently investigating which model is best suited for our AI tasks, but tend to codellama (if you prefer a free model). Models are to be placed into the ''Model ~~Localtion~~'' folder, which is found in the ~~ollama~~ window under ''Settings''.		<br>Models to consider: we tried qwen3.6, gemma4 and [https://ollama.com/library/codellama:7b codellama]. We are currently investigating which model is best suited for our AI tasks, but tend to codellama (if you prefer a free model running on your local machine).<br>Models are to be placed into the ''Model Location'' folder, which is found in the Ollama window under ''Settings''.
			<br>You can also pull models with "<CODE>ollama pull <modelName></CODE>" or "<CODE>ollama run <modelName></CODE>". On Windows, the ollama command is typically found in your personal "<CODE>AppData\Local\Programs\Ollama</CODE>" folder.

← Nächstältere Version		Version vom 26. Mai 2026, 10:22 Uhr
Zeile 17:		Zeile 17:
	}}{{Languages/Lang\|diq\|{{{1\|}}}\|		}}{{Languages/Lang\|diq\|{{{1\|}}}\|
	}}{{Languages/Lang\|el\|{{{1\|}}}\|		}}{{Languages/Lang\|el\|{{{1\|}}}\|
			}}{{Languages/Lang\|en\|{{{1\|}}}\|
	}}{{Languages/Lang\|eo\|{{{1\|}}}\|		}}{{Languages/Lang\|eo\|{{{1\|}}}\|
	}}{{Languages/Lang\|es\|{{{1\|}}}\|		}}{{Languages/Lang\|es\|{{{1\|}}}\|
Zeile 85:		Zeile 86:
	}}{{Languages/Lang\|diq\|{{{1\|}}}\|		}}{{Languages/Lang\|diq\|{{{1\|}}}\|
	}}{{Languages/Lang\|el\|{{{1\|}}}\|		}}{{Languages/Lang\|el\|{{{1\|}}}\|
			}}{{Languages/Lang\|en\|{{{1\|}}}\|
	}}{{Languages/Lang\|eo\|{{{1\|}}}\|		}}{{Languages/Lang\|eo\|{{{1\|}}}\|
	}}{{Languages/Lang\|es\|{{{1\|}}}\|		}}{{Languages/Lang\|es\|{{{1\|}}}\|

← Nächstältere Version		Version vom 26. Mai 2026, 10:19 Uhr
Zeile 2:		Zeile 2:
	\| header = '''[[Project:Language policy\|{{Languages/Title\|{{SUBPAGENAME}}}}]]'''		\| header = '''[[Project:Language policy\|{{Languages/Title\|{{SUBPAGENAME}}}}]]'''
	\| text =		\| text =
	'''[[{{{1\|:{{NAMESPACE}}:{{BASEPAGENAME}}}}}\|English]]''' {{Languages/Lang\|af\|{{{1\|}}}\|		'''[[{{{1\|:{{NAMESPACE}}:{{BASEPAGENAME}}}}}\|{{{label\|English}}}]]''' {{Languages/Lang\|af\|{{{1\|}}}\|
	}}{{Languages/Lang\|ar\|{{{1\|}}}\|		}}{{Languages/Lang\|ar\|{{{1\|}}}\|
	}}{{Languages/Lang\|ast\|{{{1\|}}}\|		}}{{Languages/Lang\|ast\|{{{1\|}}}\|

← Nächstältere Version		Version vom 26. Mai 2026, 22:01 Uhr
(2 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 15:		Zeile 15:
	* Feature: SSL1.3 support (without external SSL library)		* Feature: SSL1.3 support (without external SSL library)
	* Feature: SSL support for C, Python, NodeJS, Ruby, Dart and Smalltalk bridges (combined cert+key PEM files supported)		* Feature: SSL support for C, Python, NodeJS, Ruby, Dart and Smalltalk bridges (combined cert+key PEM files supported)
	* Feature: SSH builtin, plus SSH and SFTP clients (both via FileBrowser)		* Feature: SSH builtin, plus SSH and SFTP clients (both via [[Tools_FileBrowser/en\|FileBrowser]])
	* Feature: public/private keypair generation via a FileBrowser menu (for easy SSH setup)		* Feature: public/private keypair generation via a [[Tools_FileBrowser/en\|FileBrowser]] menu (for easy SSH setup)
	* Feature: Qt-Plugin supports Qt6.8 ([[QT_Testing/en#ExpeccoTestService_Library%3A_Delivery_in_Expecco_Versions\|Delivered versions for QT and build environment]])		* Feature: Qt-Plugin supports Qt6.8 ([[QT_Testing/en#ExpeccoTestService_Library%3A_Delivery_in_Expecco_Versions\|Delivered versions for QT and build environment]])
	* Feature: improved search text box behavior in text editors (type RETURN, CMD-f or CMD-b while box is open) and back to original position button added.		* Feature: improved search text box behavior in text editors (type RETURN, CMD-f or CMD-b while box is open) and back to original position button added.
	* Feature: Improved/Fixed Number stack:		* Feature: Improved/Fixed the [[Number_API_Functions\|Number]] stack:
	** Enhanced multiprecision numbers (eg. <float>q, <float>Q constants in freeze values)		** Enhanced multiprecision numbers (eg. <float>q, <float>Q constants in freeze values)
	** Float32 numbers (<float>f)		** Float32 numbers (<float>f)
	** Integer freezeValues in exponential notation (eg. 1e5)		** Integer freezeValues in exponential notation (eg. 1e5)
	** Recognize type specific infinities eg. "inf.0", "inf.0f", "inf.0q" etc. (useful when parsing/receiving values from the outside world)		** Recognize type specific infinities eg. "inf.0", "inf.0f", "inf.0q" etc. and type specific NaNs eg. "nan.0", "nan.0f", "nan.0q" etc. (useful when parsing/receiving values from the outside world)
	** Recognize type specific NaNs eg. "nan.0", "nan.0f", "nan.0q" etc. (useful when parsing/receiving values from the outside world)
	** fixed/added missing trigonometric functions for multiprecision floats and complex numbers (eg. arcTan)		** fixed/added missing trigonometric functions for multiprecision floats and complex numbers (eg. arcTan)
	** inspector (and activitylog as a consequence) show the type of a float (suffix 'f', 'q', 'Q' etc.)		** inspector (and activitylog as a consequence) show the type of a float (suffix 'f', 'q', 'Q' etc.)

← Nächstältere Version		Version vom 26. Mai 2026, 14:42 Uhr
Zeile 14:		Zeile 14:
	** model, API key, endpoint and max-tokens are configurable via the Claude settings dialog		** model, API key, endpoint and max-tokens are configurable via the Claude settings dialog
	* Feature: SSL1.3 support (without external SSL library)		* Feature: SSL1.3 support (without external SSL library)
	* Feature: SSL support for C, Python, NodeJS and ~~Ruby~~ bridges		* Feature: SSL support for C, Python, NodeJS, Ruby, Dart and Smalltalk bridges (combined cert+key PEM files supported)
	* Feature: SSH builtin, plus SSH and SFTP clients (both via FileBrowser)		* Feature: SSH builtin, plus SSH and SFTP clients (both via FileBrowser)
	* Feature: public/private keypair generation via a FileBrowser menu (for easy SSH setup)		* Feature: public/private keypair generation via a FileBrowser menu (for easy SSH setup)
Zeile 34:		Zeile 34:
	** routing prefers the source-side bend when the source step has multiple sibling pins		** routing prefers the source-side bend when the source step has multiple sibling pins
	* Feature: Workflow editor — improved naïve autolayout: added horizontal and vertical expansion passes that spread adjacent blocks apart for clearer connection routing		* Feature: Workflow editor — improved naïve autolayout: added horizontal and vertical expansion passes that spread adjacent blocks apart for clearer connection routing
			* Feature: file transfer (getFile/putFile) and makeDirectory for all bridges (C, Python, NodeJS, Ruby, Dart, Smalltalk)
	* Feature: function to upload/download files from/to remote CBridges (for testData and binaries)
			* Feature: defineFunction/callFunction support for NodeJS, Ruby and Smalltalk bridges
	* Performance: execution of elementary Smalltalk and JavaScript actions tuned for speed (Jitter improvements)		* Performance: execution of elementary Smalltalk and JavaScript actions tuned for speed (Jitter improvements)
	* Feature: OLE for 64 bit architectures		* Feature: OLE for 64 bit architectures