CiscoルータやCatalystのcrypto key generate rsaコマンドについて、構文や使い方を利用例交えて説明しています。
crypto key generate rsaコマンドはホスト名とドメイン名を元となるキーとして暗号化用の鍵を作成します。
ドメイン名が必須という訳ではありませんが、ドメイン名を設定する事で別途キーを指定せずに鍵を作成出来ます。
Feb 05, 2014 crypto key generate rsa modulus 1024 on cisco 1800 series to create a Trustpoints Gustavo Jan 24, 2014 12:53 PM tengo un problema al querer configurar un tunnel con PKI. Crypto key generate rsa exportable label ipsec modulus 2048 crypto ca trustpoint tpipsec2017 enrollment terminal pem crl optional fqdn rtr.example.net rsakeypair ipsec subject-name C=BE,ST=city,L=area,O=Private,OU=Familly,CN=rtr.example.net crypto ca enroll tpipsec2017! Save the csr and submit to CA crypto ca authenticate tpipsec2017.
このコマンドは鍵を作成するために使われ、コンフィグには保存されません。
Crypto key generate rsa general-keys label tokenkey1 storage usbtoken0: The following example specifies the redundancy keyword: Router(config)# crypto key generate rsa label MYKEYS redundancy. The name for the keys will be: MYKEYS Choose the size of the key modulus in the range of 360 to 2048 for your General Purpose Keys.
尚、公開鍵と秘密鍵については応用編の企業向け無線LAN「公開鍵暗号方式」をご参照下さい。
crypto key generate rsaコマンドの構文は以下の通りです。
先にip domain-nameでドメイン名が設定されている必要があります。
デフォルトでは鍵は作成されていません。
crypto key generate rsaコマンドの利用例は以下の通りです。
crypto key generate rsa実行後は鍵長を求められます。上記では2048を設定していますが、セキュリティ強度から1024以上をお奨めします。
・グローバルコンフィギュレーションモード
作成した鍵を削除するためには以下を実行します。
・設定編「初期設定」Microsoft flight simulator x product key generator.
Catalystのパスワード、ホスト名、telnet、ssh接続等の初期設定について説明しています。
「Ciscoルータ/Catalystコマンド一覧」に戻る
Use this command to generate RSA key pairs for your Cisco device (such as a router). keys are generated in pairs–one public RSA key and one private RSA key.
If your router already has RSA keys when you issue this command, you will be warned and prompted to replace the existing keys with new keys.
The SSH key needs to be added to Bitbucket Server, and your Bitbucket Server administrator must have enabled SSH access to Git repositories, before you can make use of the key. Bitbucket Server supports DSA, RSA2, and Ed25519 key types. RSA1 is not supported. You can use an existing SSH key with Bitbucket Server if you want, in which case you can go straight to either SSH user keys for personal. Bitbucket Server provides a simple way for user accounts and other systems to connect securely to Bitbucket Server repositories, using SSH keys, in order to perform Git operations. You can: add a personal key to a Bitbucket Server user account to allow a developer to easily authenticate when performing read operations from his or her local machine. A Bitbucket Server user can add any number of keys to their account. Read more at SSH. There are two ways to load a remote git repository: using SSH and using HTTPS. SSH will use a key pair, and requires the public key to be added to your BitBucket/GitHub profile. HTTPS requires your BitBucket/GitHub username and password. You will be promoted for your password every time you interact with the remote server (clone, fetch, push, pull). SSH keys are used to authenticate secure connections. Following this guide, you will be able to create and start using an SSH key. Git is capable of using SSH keys instead of traditional password authentication when pushing or pulling to remote repositories. Modern hosted git solutions like Bitbucket support SSH key authentication. Git generate ssh key bitbucket.
NOTE: Before issuing this command, ensure that your router has a hostname and IP domain name configured (with the hostname and ipdomain-name commands).
You will be unable to complete the cryptokeygeneratersacommand without a hostname and IP domain name. (This situation is not true when you generate only a named key pair.)
router (Config) # Line VTY 0 15
router (Config-line)# login local
router (Config-line)# Exit
router (Config)# username [loginid] password [cisco]
router (Config)# username loginid1 password cisco1
router (Config)# crypto key generate rsa
how many bits in the modulus [512] :1024
router (Config)# ip ssh version2
router (Config)# CTRL Z
Note | Secure Shell (SSH) may generate an additional RSA key pair if you generate a key pair on a router having no RSA keys. The additional key pair is used only by SSH and will have a name such as {router_FQDN }.server. For example, if a router name is “router1.cisco.com,” the key name is “router1.cisco.com.server.” |
This command is not saved in the router configuration; however, the RSA keys generated by this command are saved in the private configuration in NVRAM (which is never displayed to the user or backed up to another device) the next time the configuration is written to NVRAM.
When you generate RSA keys, you will be prompted to enter a modulus length. The longer the modulus, the stronger the security. However, a longer modules take longer to generate (see the table below for sample times) and takes longer to use.
The size of Key Modulus range from 360 to 2048. Choosing modulus greater than 512 will take longer time.
Router | 360 bits | 512 bits | 1024 bits | 2048 bits (maximum) |
---|---|---|---|---|
Cisco 2500 | 11 seconds | 20 seconds | 4 minutes, 38 seconds | More than 1 hour |
Cisco 4700 | Less than 1 second | 1 second | 4 seconds | 50 seconds |
Cisco IOS software does not support a modulus greater than 4096 bits. A length of less than 512 bits is normally not recommended. In certain situations, the shorter modulus may not function properly with IKE, so we recommend using a minimum modulus of 2048 bits.
general-keys | (Optional) Specifies that a general-purpose key pair will be generated, which is the default. | ||
usage-keys | (Optional) Specifies that two RSA special-usage key pairs, one encryption pair and one signature pair, will be generated. | ||
signature | (Optional) Specifies that the RSA public key generated will be a signature special usage key. | ||
encryption | (Optional) Specifies that the RSA public key generated will be an encryption special usage key. | ||
labelkey-label | (Optional) Specifies the name that is used for an RSA key pair when they are being exported.If a key label is not specified, the fully qualified domain name (FQDN) of the router is used. | ||
exportable | (Optional) Specifies that the RSA key pair can be exported to another Cisco device, such as a router. | ||
modulusmodulus-size | (Optional) Specifies the IP size of the key modulus.By default, the modulus of a certification authority (CA) key is 1024 bits. The recommended modulus for a CA key is 2048 bits. The range of a CA key modulus is from 350 to 4096 bits.
| ||
storagedevicename: | (Optional) Specifies the key storage location. The name of the storage device is followed by a colon (:). | ||
redundancy | (Optional) Specifies that the key should be synchronized to the standby CA. | ||
ondevicename: | (Optional) Specifies that the RSA key pair will be created on the specified device, including a Universal Serial Bus (USB) token, local disk, or NVRAM. The name of the device is followed by a colon (:).Keys created on a USB token must be 2048 bits or less. |
Command | Description |
---|---|
copy | Copies any file from a source to a destination, use the copy command in privileged EXEC mode. |
cryptokeystorage | Sets the default storage location for RSA key pairs. |
debugcryptoengine | Displays debug messages about crypto engines. |
hostname | Specifies or modifies the hostname for the network server. |
ipdomain-name | Defines a default domain name to complete unqualified hostnames (names without a dotted-decimal domain name). |
showcryptokeymypubkeyrsa | Displays the RSA public keys of your router. |
show crypto pki certificates | Displays information about your PKI certificate, certification authority, and any registration authority certificates. |