Secret Strings/en - Versionsgeschichte

Cg: /* Secret Values */

2021-02-16T20:54:18Z

Secret Values

← Nächstältere Version		Version vom 16. Februar 2021, 20:54 Uhr
Zeile 10:		Zeile 10:
	someValue.beSecret(true)		someValue.beSecret(true)

	~~hat~~ is an attribute of the object (i.e. the String or ByteArray), and will be preserved and remain persistently attached to the object as it gets passed to other pins or actions.		that is an attribute of the object (i.e. the String or ByteArray), and will be preserved and remain persistently attached to the object as it gets passed to other pins or actions.

	The activity logger and other expecco tools will not show the real value of objects marked as being secret. However, as the datum is actually physically present somewhere in memory, a knowledgable user may be able to recover the original value while expecco is running. Thus, this does not provide 100% security; it does however prevent those values from being exposed by accident eg. in a report or while looking at an activity log.		The activity logger and other expecco tools will not show the real value of objects marked as being secret. However, as the datum is actually physically present somewhere in memory, a knowledgable user may be able to recover the original value while expecco is running. Thus, this does not provide 100% security; it does however prevent those values from being exposed by accident eg. in a report or while looking at an activity log.

			There is a minor restriction in that numbers and booleans cannot be marked as secret (because these are implemented as singletons in the underlying runtime system).
			In that case, you should pass the printed string marked as secret if required.

	== The PasswordString Datatype ==		== The PasswordString Datatype ==

Cg: /* Secret Values */

2021-02-16T20:52:27Z

Secret Values

← Nächstältere Version		Version vom 16. Februar 2021, 20:52 Uhr
Zeile 7:		Zeile 7:
	Any object can be given a "''secret''" attribute via the Smalltalk expression:		Any object can be given a "''secret''" attribute via the Smalltalk expression:
	someValue beSecret:true		someValue beSecret:true
			or in JavaScript:
			someValue.beSecret(true)

	hat is an attribute of the object (i.e. the String or ByteArray), and will be preserved and remain persistently attached to the object as it gets passed to other pins or actions.		hat is an attribute of the object (i.e. the String or ByteArray), and will be preserved and remain persistently attached to the object as it gets passed to other pins or actions.

Cg: /* Secret Variables */

2021-02-16T20:51:46Z

Secret Variables

← Nächstältere Version		Version vom 16. Februar 2021, 20:51 Uhr
Zeile 16:		Zeile 16:

	== Secret Variables ==		== Secret Variables ==
	If a variable (an expecco environment variable) is declared as secret or secret from user, it will also be marked as such.		If a variable (an expecco environment variable) is declared as being initialized as secret or secret from user, it will also be marked as such.

Cg am 16. Februar 2021 um 20:51 Uhr

2021-02-16T20:51:19Z

← Nächstältere Version		Version vom 16. Februar 2021, 20:51 Uhr
Zeile 3:		Zeile 3:
	Examples for such are passwords as entered by the operator or		Examples for such are passwords as entered by the operator or
	cryptographic keys as used temporarily.		cryptographic keys as used temporarily.

		⚫	== Secret Values ==
			Any object can be given a "''secret''" attribute via the Smalltalk expression:
			someValue beSecret:true
		⚫	hat is an attribute of the object (i.e. the String or ByteArray), and will be preserved and remain persistently attached to the object as it gets passed to other pins or actions.

		⚫	The activity logger and other expecco tools will not show the real value of objects marked as being secret. However, as the datum is actually physically present somewhere in memory, a knowledgable user may be able to recover the original value while expecco is running. Thus, this does not provide 100% security; it does however prevent those values from being exposed by accident eg. in a report or while looking at an activity log.

	== The PasswordString Datatype ==		== The PasswordString Datatype ==
	By declaring the datatype of an output pin as <CODE>PasswordString</CODE>,		By declaring the datatype of an output pin as <CODE>PasswordString</CODE>,
	the value written to the pin will get the secret attribute.		the value written to the pin will get the secret attribute.
⚫	~~That~~ is an attribute of the ~~datum~~ (i.e. the String), and will be preserved and remain persistently attached to the ~~string~~ as it gets passed to other pins.

	The activity logger and other expecco tools will not show the real value of those strings.
⚫	However, as the datum is actually present somewhere in memory, a knowledgable user ~~will actually~~ be able to recover the ~~string~~ while expecco is running. Thus, this does not provide a 100% security; it does prevent ~~printing~~ those values by accident eg. in a report.

	== Secret Variables ==		== Secret Variables ==
			If a variable (an expecco environment variable) is declared as secret or secret from user, it will also be marked as such.

⚫	== Secret Values ==

Cg: /* The PasswordString Datatype */

2021-02-16T20:47:29Z

The PasswordString Datatype

← Nächstältere Version		Version vom 16. Februar 2021, 20:47 Uhr
Zeile 5:		Zeile 5:

	== The PasswordString Datatype ==		== The PasswordString Datatype ==
			By declaring the datatype of an output pin as <CODE>PasswordString</CODE>,
			the value written to the pin will get the secret attribute.
			That is an attribute of the datum (i.e. the String), and will be preserved and remain persistently attached to the string as it gets passed to other pins.

			The activity logger and other expecco tools will not show the real value of those strings.
			However, as the datum is actually present somewhere in memory, a knowledgable user will actually be able to recover the string while expecco is running. Thus, this does not provide a 100% security; it does prevent printing those values by accident eg. in a report.

	== Secret Variables ==		== Secret Variables ==

Cg am 16. Februar 2021 um 20:42 Uhr

2021-02-16T20:42:48Z

← Nächstältere Version		Version vom 16. Februar 2021, 20:42 Uhr
Zeile 6:		Zeile 6:
	== The PasswordString Datatype ==		== The PasswordString Datatype ==

	== Secret Variables ===		== Secret Variables ==

	== Secret Values ===		== Secret Values ==

Cg: Die Seite wurde neu angelegt: „During execution, strings might be needed or generated which should not be shown in the activity log or in the final report. Examples for such are passwords as…“

2021-02-16T20:42:29Z

Die Seite wurde neu angelegt: „During execution, strings might be needed or generated which should not be shown in the activity log or in the final report. Examples for such are passwords as…“

Neue Seite

During execution, strings might be needed or generated which should not
be shown in the activity log or in the final report.
Examples for such are passwords as entered by the operator or
cryptographic keys as used temporarily.

== The PasswordString Datatype ==

== Secret Variables ===

== Secret Values ===