执行:gpg --gen-key 显示:Not enough random bytes available.

简介:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
[root@clovemzone ~]$ gpg --gen-key
gpg (GnuPG) 1.4.5; Copyright (C) 2006 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is  free  software, and you are welcome to redistribute it
under certain conditions. See the  file  COPYING  for  details.
Please  select  what kind of key you want:
    (1) DSA and Elgamal (default)
    (2) DSA (sign only)
    (5) RSA (sign only)
Your selection? 1
DSA keypair will have 1024 bits.
ELG-E keys may be between 1024 and 4096 bits long.
What keysize  do  you want? (2048)
Requested keysize is 2048 bits
Please specify how long the key should be valid.
          0 = key does not expire
       <n>  = key expires  in  n days
       <n>w = key expires  in  n weeks
       <n>m = key expires  in  n months
       <n>y = key expires  in  n years
Key is valid  for ? (0) 0
Key does not expire at all
Is this correct? (y /N ) y
You need a user ID to identify your key; the software constructs the user ID
from the Real Name, Comment and Email Address  in  this form:
     "Heinrich Heine (Der Dichter) <heinrichh@duesseldorf.de>"
Real name: clovemzone
Email address: clovem@gmail.com
Comment: clovem key
You selected this USER-ID:
     "clovemzone (fdfd) <clovem@gmail.com>"
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
You need a Passphrase to protect your secret key.
You don't want a passphrase - this is probably a *bad* idea!
I will  do  it anyway.  You can change your passphrase at any  time ,
using this program with the option  "--edit-key" .
We need to generate a lot of random bytes. It is a good idea to perform
some other action ( type  on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
.+++++.+++++++++++++++.+++++..+++++++++++++++++++++++++..+++++..+++++.++++++++++++++++++++.++++++++++++++++++++++++++++++..++++++++++++++++++++>.++++++++++..........................................+++++
Not enough random bytes available.  Please  do  some other work to give
the OS a chance to collect  more  entropy! (Need 274  more  bytes)





解决方法:

1.原有进程不退出

2.对一个稍大的tar.gz包解压

[root@clovemzone ~]# tar zxvf mysql-5.5.29.tar.gz

会发现执行完成,稍等片刻的时间,上面的进程会继续下去了

1
2
3
4
5
6
7
8
9
10
+++++++++++++++..+++++++++++++++..++++++++++.+++++.+++++++++++++++.+++++..++++++++++++++++++++++++++++++..++++++++++++++++++++++++++++++++++++++++++++++++++>.++++++++++>+++++....................+++++^^^^
gpg: key 2914933F marked as ultimately trusted
public and secret key created and signed.
gpg: checking the trustdb
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   5  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 5u
pub   1024D /2914933F  2013-06-11
       Key fingerprint = C718 A91B 00EE 9FBF 8FB2  4F22 B564 CAFC 2914 933F
uid                  clovemzone (fdfd) <clovem@gmail.com>
sub   2048g /CFF2F8BB  2013-06-11



至此问题解决,问题解决的关键就在于这个进程需要更多的随机数什么的,那就给系统点随机字符即可。










本文转自 暗黑魔君 51CTO博客,原文链接:http://blog.51cto.com/clovemfong/1220455,如需转载请自行联系原作者
目录
相关文章
|
9月前
|
存储 关系型数据库 MySQL
1071 - Specified key was too long; max key length is 767 bytes
【2月更文挑战第5天】1071 - Specified key was too long; max key length is 767 bytes 问题处理
|
关系型数据库 MySQL 索引
【Database】排错:Mysql5.6报错Specified key was too long; max key length is 767 bytes
在某个实验系统部署的过程中,出现mysql报错,是特定版本的处理错误,在查阅官网文档时得到解决方案
1580 0
【Database】排错:Mysql5.6报错Specified key was too long; max key length is 767 bytes
|
9月前
|
关系型数据库 MySQL
MySQL创建表出现 Specified key was too long; max key length is 767 bytes
MySQL创建表出现 Specified key was too long; max key length is 767 bytes
202 2
|
9月前
|
关系型数据库 MySQL 数据库
Specified key was too long; max key length is 767 bytes导入mysql数据库表报错
Specified key was too long; max key length is 767 bytes导入mysql数据库表报错
485 0
|
关系型数据库 MySQL 索引
(1071, ‘Specified key was too long; max key length is 767 bytes‘)
(1071, ‘Specified key was too long; max key length is 767 bytes‘)
59 0
|
关系型数据库 MySQL 索引
MySQL添加索引Specified key was too long; max key length is 767 bytes
MySQL添加索引Specified key was too long; max key length is 767 bytes
187 0
torch.distributed.init_process_group(‘gloo’, init_method=‘file://tmp/somefile’, rank=0, world_size=1
torch.distributed.init_process_group(‘gloo’, init_method=‘file://tmp/somefile’, rank=0, world_size=1
619 0
torch.distributed.init_process_group(‘gloo’, init_method=‘file://tmp/somefile’, rank=0, world_size=1
|
关系型数据库 MySQL PHP
laravel5.5报错:1071 Specified key was too long; max key length is 767 bytes
laravel5.5报错:1071 Specified key was too long; max key length is 767 bytes

热门文章

最新文章