bump version to 5.1-10

[pve-access-control.git] / debian / changelog

diff --git a/debian/changelog b/debian/changelog
index 89a7a8abd3451a33bc50eac512f32a6ceb54702a..f3887c93ac665cdcb734f0523e930785a8f6eb6d 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,32 @@
+libpve-access-control (5.1-10) unstable; urgency=medium
+
+  * add /access/user/{id}/tfa api call to get tfa types
+
+ -- Proxmox Support Team <support@proxmox.com>  Wed, 15 May 2019 16:21:10 +0200
+
+libpve-access-control (5.1-9) unstable; urgency=medium
+
+  * store the tfa type in user.cfg allowing to get it without proxying the call
+    to a higher priviledged daemon.
+
+  * tfa: realm required TFA should lock out users without TFA configured, as it
+    was done before Proxmox VE 5.4
+
+ -- Proxmox Support Team <support@proxmox.com>  Tue, 30 Apr 2019 14:01:00 +0000
+
+libpve-access-control (5.1-8) unstable; urgency=medium
+
+  * U2F: ensure we save correct public key on registration
+
+ -- Proxmox Support Team <support@proxmox.com>  Tue, 09 Apr 2019 12:47:12 +0200
+
+libpve-access-control (5.1-7) unstable; urgency=medium
+
+  * verify_ticket: allow general non-challenge tfa to be run as two step
+    call
+
+ -- Proxmox Support Team <support@proxmox.com>  Mon, 08 Apr 2019 16:56:14 +0200
+
 libpve-access-control (5.1-6) unstable; urgency=medium
 
   * more general 2FA configuration via priv/tfa.cfg