Jenja (487a0c0d) at 26 Oct 16:57
Added legacy support for sha1
We definitely should also support sha1 on the client-facing side for the time being, and
The problem is, since we have no control over our clients, we'll need to support sha1 along with sha256 on that side for some time. Upstream BBB had that same issue in 2.5.7, which is why they released 2.5.8 shortly after, re-adding sha1 support.
Cargo Update war nötig, um socket2 auf eine neuere Version zu bringen. Gab vorher folgenden Fehler:
error[E0512]: cannot transmute between types of different sizes, or dependently-sized types
176 | mem::transmute::<SocketAddrV4, sockaddr_in>(v4);
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Jenja (eaa16710) at 25 Oct 11:00
Update from sha1 to sha256
Jenja (519a8b73) at 25 Oct 10:59
Jenja (519a8b73) at 25 Oct 10:58
Update from sha1 to sha256
Jenja (cc3d9afe) at 25 Oct 10:54
Jenja (cc3d9afe) at 25 Oct 10:54
Fixed unittest
Jenja (519a8b73) at 25 Oct 10:44
Update from sha1 to sha256
Johannes Barthel (0a4e5da8) at 22 Dec 08:23
fix 100% cpu usage while waiting for signals, improve readme
Johannes Barthel (ce07a277) at 22 Dec 08:00
implement config live reload via sighup
Johannes Barthel (50ed15eb) at 11 Nov 22:27
increase backend response buffer size so getMeetings does not fail ...
Johannes Barthel (f1d473af) at 30 Oct 00:17
update Cargo.lock
Johannes Barthel (cd8e7a4b) at 28 Aug 13:09
increment version number