From 056a6dd3479fe1e5cc5981ac51a458b015d3e9cb Mon Sep 17 00:00:00 2001
From: Thialfihar <thi@thialfihar.org>
Date: Wed, 14 May 2014 14:14:02 +0200
Subject: Don't guess keybase key algorithm and size

Once keybase reports them, we can display them. Until then we simply
don't know and shouldn't lie about it.
---
 .../org/sufficientlysecure/keychain/keyimport/KeybaseKeyServer.java | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

(limited to 'OpenKeychain/src/main/java/org/sufficientlysecure/keychain/keyimport')

diff --git a/OpenKeychain/src/main/java/org/sufficientlysecure/keychain/keyimport/KeybaseKeyServer.java b/OpenKeychain/src/main/java/org/sufficientlysecure/keychain/keyimport/KeybaseKeyServer.java
index d1755fa12..da47c32c6 100644
--- a/OpenKeychain/src/main/java/org/sufficientlysecure/keychain/keyimport/KeybaseKeyServer.java
+++ b/OpenKeychain/src/main/java/org/sufficientlysecure/keychain/keyimport/KeybaseKeyServer.java
@@ -98,10 +98,8 @@ public class KeybaseKeyServer extends KeyServer {
         entry.setExtraData(keybaseId);
 
         // TODO: Fix; have suggested keybase provide this value to avoid search-time crypto calls
-        entry.setBitStrength(4096);
-        entry.setAlgorithm("RSA");
-        entry.setKeyIdHex("0x" + key_fingerprint);
-        entry.setRevoked(false);
+        //entry.setBitStrength(4096);
+        //entry.setAlgorithm("RSA");
 
         // ctime
         final long creationDate = JWalk.getLong(match, "them", "public_keys", "primary", "ctime");
-- 
cgit v1.2.3