Difference between revisions of "Welcome to regify wiki"
Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
− | <p style="font-size: 40px; text-align: center; | + | <p style="font-size: 40px; text-align: center; background:#EEEEEE; padding: 20px; color:#505050; text-shadow: -1px -1px 0px #202020, 1px 1px 0px #fff; border-bottom: 2px solid #AAAAAA">[[File:Logo.png|RTENOTITLE]] Welcome to the regify wiki pages.</p> |
− | + | <p style="color: white; background-color: #aa3333; border: 2px solid #330000; padding: 10px;"> | |
− | + | Regarding '''Spectre''' and '''Meltdown''' attacks.<br> | |
− | + | <br> | |
− | + | We investigated the impact of the currently discussed security flaws CVE-2017-5753 (Spectre 1, Bounds Check Bypass), CVE-2017-5715 (Spectre 2, Branch Target Injection) and CVE-2017-5754 (Meltdown, Rogue Data Cache Load). In order to attack a system using these flaws, a rogue executable has to be copied to the affected server system and then executed. For the '''regify provider appliance''', the '''regigate appliance''' and other servers of the regify infrastructure, this is not possible by default. The only way to do this would be a serious data breach on the platform. And if this happened, the attacker does not need to utilize one of these flaws to get data or create serious damage. Due to this, the systems are neither more or less secure than before.<br> | |
− | + | <br> | |
− | [[File:Logo.png]] Welcome to the regify wiki pages. | + | Of course, the next patch updates of your regify appliances will contain the respecting kernel patches anyway.<br> |
+ | <br> | ||
+ | From what we know today, your '''regify client software''' is not affected, as these are hardware related issues and the fixes have to be applied by the Operating System or Web-Browsers. Please keep your systems up to date. | ||
</p> | </p> | ||
− | |||
The target audience for this wiki are '''administrators of regify providers''' and '''technical interested persons''' who want to get extra information on regify software and technology. | The target audience for this wiki are '''administrators of regify providers''' and '''technical interested persons''' who want to get extra information on regify software and technology. | ||
Line 17: | Line 18: | ||
{| class="wikitable" width="100%" | {| class="wikitable" width="100%" | ||
|- | |- | ||
− | | | + | | style="vertical-align:top" width="50%" | |
+ | === regify-provider === | ||
− | |||
[[Changelog_Provider|The current regify-provider changelog]] (history) | [[Changelog_Provider|The current regify-provider changelog]] (history) | ||
− | [[ | + | [[Provider_appliance|Information about the regify Provider Appliance]] |
− | [[ | + | [[Hardware|Find information about regify-provider hardware requirements]] |
− | [[Update Guide]] | + | [[Update_Guide|Update Guide]] |
− | [[ | + | [[Update_4.1|Updating provider from V4.0.x to V4.1]] |
− | [[ | + | [[Update_4.2|Updating provider from V4.1.x to V4.2]] |
− | | | + | | style="vertical-align:top" width="50%" | |
+ | === regify client === | ||
− | |||
[[Changelog_Client|The current regify-client changelog]] (history) | [[Changelog_Client|The current regify-client changelog]] (history) | ||
Line 40: | Line 41: | ||
|- | |- | ||
− | | | + | | style="vertical-align:top" width="50%" | |
+ | === regipay === | ||
− | + | [[Regipay_Desktop|regipay Desktop]] | |
− | [[regipay Desktop]] | ||
[[Changelog_Desktop|regipay Desktop changelog]] | [[Changelog_Desktop|regipay Desktop changelog]] | ||
− | [[ | + | [[Regipay|regipay FAQ]] |
− | |||
− | |||
+ | | style="vertical-align:top" width="50%" | | ||
=== regimail === | === regimail === | ||
[[Changelog_Desktop|regimail Desktop changelog]] | [[Changelog_Desktop|regimail Desktop changelog]] | ||
− | [[ | + | [[Regimail|regimail FAQ]] |
|- | |- | ||
− | | | + | | style="vertical-align:top" width="50%" | |
+ | === regibill === | ||
− | + | [[Regibill_Desktop|regibill Desktop]] | |
− | [[regibill Desktop]] | ||
[[Changelog_Desktop|regibill Desktop changelog]] | [[Changelog_Desktop|regibill Desktop changelog]] | ||
− | [[ | + | [[Regibill|regibill FAQ]] |
− | |||
− | |||
+ | | style="vertical-align:top" width="50%" | | ||
=== Mobile clients === | === Mobile clients === | ||
Line 74: | Line 73: | ||
|- | |- | ||
− | | | + | | style="vertical-align:top" width="50%" | |
+ | === regibox === | ||
− | |||
[[Changelog_Regibox|regibox changelog]] | [[Changelog_Regibox|regibox changelog]] | ||
− | [[ | + | [[Regibox_Faq|regibox FAQ]] |
− | | | + | | style="vertical-align:top" width="50%" | |
+ | === regigate === | ||
− | |||
[[Changelog_regigate|The regigate changelog]] | [[Changelog_regigate|The regigate changelog]] | ||
− | [[ | + | [[Regigate_information|Information about the regigate appliance]] |
− | [[ | + | [[Regigate_requirements|regigate hardware requirements and performance]] |
|} | |} | ||
== troubleshooting == | == troubleshooting == | ||
+ | |||
=== Client Software === | === Client Software === | ||
+ | |||
{| class="wikitable" width="100%" | {| class="wikitable" width="100%" | ||
|- | |- | ||
− | | | + | | style="vertical-align:top" width="50%" | |
− | |||
[[Troubleshoot_Connectivity|General connectivity issues]] | [[Troubleshoot_Connectivity|General connectivity issues]] | ||
Line 108: | Line 108: | ||
[[Troubleshoot_Outlook|Outlook AddIn]] | [[Troubleshoot_Outlook|Outlook AddIn]] | ||
− | | | + | | style="vertical-align:top" width="50%" | |
[[Troubleshoot_regibox|regibox manager (Desktop)]] | [[Troubleshoot_regibox|regibox manager (Desktop)]] | ||
Line 125: | Line 125: | ||
{| class="wikitable" width="100%" | {| class="wikitable" width="100%" | ||
|- | |- | ||
− | | | + | | style="vertical-align:top" width="50%" | |
− | |||
[[Troubleshoot_regify_account|regify account issues]] | [[Troubleshoot_regify_account|regify account issues]] | ||
− | | | + | | style="vertical-align:top" width="50%" | |
− | |||
[[Troubleshoot_regify_portal|User portal (web interface)]] | [[Troubleshoot_regify_portal|User portal (web interface)]] | ||
Line 139: | Line 137: | ||
{| class="wikitable" width="100%" | {| class="wikitable" width="100%" | ||
|- | |- | ||
− | | | + | | style="vertical-align:top" width="50%" | |
− | |||
[[Troubleshooting_Provider_Appliance|regify provider appliance]] | [[Troubleshooting_Provider_Appliance|regify provider appliance]] | ||
[[Troubleshooting_AntiVirus_false_positives|AntiVirus false positives]] | [[Troubleshooting_AntiVirus_false_positives|AntiVirus false positives]] | ||
− | | | + | | style="vertical-align:top" width="50%" | |
− | |||
[[ErrorCodes|regify error codes]] | [[ErrorCodes|regify error codes]] | ||
Line 186: | Line 182: | ||
== other information == | == other information == | ||
+ | |||
[[Authentication-levels|list of all authentication levels]] | [[Authentication-levels|list of all authentication levels]] | ||
[[Security|Answers to different security questions]] (professionals only) | [[Security|Answers to different security questions]] (professionals only) | ||
− | [[ | + | [[Provider_Setup|Installation hints for provider-setup]] (Outdated! Only for Windows) |
Revision as of 08:54, 11 January 2018
Welcome to the regify wiki pages.
Regarding Spectre and Meltdown attacks.
We investigated the impact of the currently discussed security flaws CVE-2017-5753 (Spectre 1, Bounds Check Bypass), CVE-2017-5715 (Spectre 2, Branch Target Injection) and CVE-2017-5754 (Meltdown, Rogue Data Cache Load). In order to attack a system using these flaws, a rogue executable has to be copied to the affected server system and then executed. For the regify provider appliance, the regigate appliance and other servers of the regify infrastructure, this is not possible by default. The only way to do this would be a serious data breach on the platform. And if this happened, the attacker does not need to utilize one of these flaws to get data or create serious damage. Due to this, the systems are neither more or less secure than before.
Of course, the next patch updates of your regify appliances will contain the respecting kernel patches anyway.
From what we know today, your regify client software is not affected, as these are hardware related issues and the fixes have to be applied by the Operating System or Web-Browsers. Please keep your systems up to date.
The target audience for this wiki are administrators of regify providers and technical interested persons who want to get extra information on regify software and technology.
If you have any further technical questions about regify technology, please contact us at support (AT) regify.com.
product information
regify-providerThe current regify-provider changelog (history) Information about the regify Provider Appliance Find information about regify-provider hardware requirements |
regify clientThe current regify-client changelog (history) |
regipay |
regimail |
regibill |
Mobile clients |
regibox |
regigate |
troubleshooting
Client Software
regify account and Web-Portal
Other
technical articles
other information
list of all authentication levels
Answers to different security questions (professionals only)
Installation hints for provider-setup (Outdated! Only for Windows)