5 Commits

Author	SHA1	Message	Date
AlinMoldovean	8b374a7448	Copyright year set to 2019 in license notices.	2019-02-14 12:34:33 +02:00
Martin Regen	d007a41d15	Add Aes profile support (#574) ... * add the Aes128 and Aes256 profiles * Aes profies were tested on IoP workshop against Ascolab, Softing, Matrikon, Milo, ProSys and others * Pss padding is not supported on all platforms, so autodetect if it is supported and filter out Aes256 if not * not a breaking change: not specifying the SecurityProfileUri in the config xml will automatically add all supported profiles but not deprecated profiles (e.g. Basic256Sha256, Aes128, Aes256). Aes256 is only added if the platform supports Pss padding. This will simplify the maintenance of config xml, since automatically all supported and secure profiles are exposed.	2018-10-29 09:58:45 +01:00
Martin Regen	a62d11c3fb	Basic256Sha256 support	2016-12-02 22:35:00 +01:00
Martin Regen	92ff201f4e	Small fixes for UWP apps, mainly polish. ... -Move command button in status bar -fix a ui thread exception -clean up Publisher server list	2016-09-19 14:04:41 +02:00
Erich Barnstedt	2901d8e5bb	1. Added definition of supported frameworks into project jason to get compiletime issues on missing classes. ... 2. Removed client cert validation from HTTPS client and server as this is not supported on all platforms, e.g. .Net4.6. 3. Reverted back to XmlDocument from XDocument as this is now supported via a NuGet package on UWP and XDocument is not supported on .Net4.6. 4. Baseline .Net4.6 samples and assoc. controls project check-in, not working yet. 5. Moved UWP client controls from SDK to Samples directly.	2016-07-10 23:27:41 +02:00