You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Background: BBB-Server below 3.0 are using SHA1-algorithm for hooks. The current planning for
222
-
* BBB-Server 3.0 (and on) is to align the hashing algorithm for hooks with the rest
223
-
* of the system. Having this in mind the two situations need to be covered:
224
-
* - BBB-Server < 3.0 ==> SHA1 is default for hooks (even rest is using other algorithm)
225
-
* - BBB-Server >= 3.0 ==> same algorithm everywhere (according to planning).
223
+
* This function defines the algorithm to be used for hooks.
226
224
*
227
225
* This function will evolve in phases:
228
-
* - Phase 1: SHA1 as default (or superseded by environment-variable HASH_ALGO_FOR_HOOKS).
229
-
* - Phase 2: same algo everywhere as default (or superseded by environment-variable HASH_ALGO_FOR_HOOKS and which will trigger in this case a deprecation-warning).
230
-
* - Phase 3: removal of this function, the class-property '$hashAlgoForHooks' and the use of env-variable HASH_ALGO_FOR_HOOKS.
226
+
* - Phase 1: SHA1 as default (or superseded by environment-variable HASH_ALGO_FOR_HOOKS).
227
+
* - Phase 2: same algo everywhere as default (or superseded by environment-variable HASH_ALGO_FOR_HOOKS and which will trigger in this case a deprecation-warning).
228
+
* - Phase 3: removal of this function, adaptation of the other hook-functions in this class and remove the use of env-variable HASH_ALGO_FOR_HOOKS.
229
+
*
230
+
* Background:
231
+
* BB-Server below 3.0 are using SHA1-algorithm for hooks only, but allow higher algorithms for
232
+
* other APIs. This is creating issues since the algorithm of choice is used in the urlBuilder-class
233
+
* for the hashing of the checksum. This is resulting in denied requests for hooks if the algorithm
234
+
* of choice is not SHA1.
235
+
* The current planning for BBB-Server 3.0 (and on) is to align the hashing algorithm for hooks with
236
+
* the rest of the system. Having this in mind two situations need to be covered:
237
+
* - BBB-Server < 3.0 ==> SHA1 is default for hooks (even rest is using other algorithm)
238
+
* - BBB-Server >= 3.0 ==> same algorithm everywhere (according to planning).
231
239
*
232
240
* @deprecated This function will evolve in phases and will later disappear
* trigger_error('The environment variable HASH_ALGO_FOR_HOOKS will be removed soon. This will require you to run a BBB-Server 3.0 or higher!', E_USER_DEPRECATED);
245
252
* }
253
+
*
254
+
* // in case this env-variable is not set, the 'normal' algorithm shall be used as default (phase 2)
0 commit comments