summaryrefslogtreecommitdiff
path: root/upgrading
diff options
context:
space:
mode:
authorLukas Fleischer <lfleischer@archlinux.org>2015-06-26 08:52:58 +0200
committerLukas Fleischer <lfleischer@archlinux.org>2015-06-27 13:04:03 +0200
commitb036b436aa64be000481f8d1da30ff53d4bcb889 (patch)
tree152fe703c11a79a1904e362271d5022b9d784a5b /upgrading
parentdbe56342a19692cba6a6cd8e79a4e6b65a6d659e (diff)
Add support for multiple SSH public keys
Attaching more than one SSH public key to the same account is useful, e.g. if one uses different machines to access the AUR SSH interface. Multiple keys can now be specified by adding multiple lines to the text area on the account edit form. Implements FS#45469. Signed-off-by: Lukas Fleischer <lfleischer@archlinux.org> Acked-by: Leonidas Spyropoulos <artafinde@gmail.com>
Diffstat (limited to 'upgrading')
-rw-r--r--upgrading/4.0.0.txt10
1 files changed, 8 insertions, 2 deletions
diff --git a/upgrading/4.0.0.txt b/upgrading/4.0.0.txt
index 637c4b9..74e167b 100644
--- a/upgrading/4.0.0.txt
+++ b/upgrading/4.0.0.txt
@@ -3,10 +3,16 @@ want to keep the package contents, please create a backup before starting the
upgrade process and import the source tarballs into the Git repositories
afterwards.
-1. Add a field for the SSH public key to the Users table:
+1. Add a table to store SSH public keys:
----
-ALTER TABLE Users ADD COLUMN SSHPubKey VARCHAR(4096) NULL DEFAULT NULL;
+CREATE TABLE SSHPubKeys (
+ UserID INTEGER UNSIGNED NOT NULL,
+ Fingerprint VARCHAR(44) NOT NULL,
+ PubKey VARCHAR(4096) NOT NULL,
+ PRIMARY KEY (Fingerprint),
+ FOREIGN KEY (UserID) REFERENCES Users(ID) ON DELETE CASCADE
+) ENGINE = InnoDB;
----
2. Create a new user and configure Git/SSH as described in INSTALL.