An enable password is defined as follows:<\/p>\n
\u2022Must contain from 1 to 25 uppercase and lowercase alphanumeric characters.<\/p>\n
\u2022Must not have a number as the first character.<\/p>\n
\u2022Can have leading spaces, but they are ignored. However, intermediate and trailing spaces are recognized.<\/p>\n
\u2022Can contain the question mark (?) character if you precede the question mark with the key combination <\/strong>Crtl-v when you create the password; for example, to create the password abc?123, <\/em>do the following:<\/p>\n \u2013Enter abc<\/strong>.<\/p>\n \u2013Type Crtl-v<\/strong>.<\/p>\n \u2013Enter ?123<\/strong>.<\/p>\n When the system prompts you to enter the enable password, you need not precede the question mark with the Ctrl-v; you can simply enter abc?123 at the password prompt.<\/p>\n The following example enables the password “pswd2” for privilege level 2:<\/p>\n The following example sets the encrypted password “$1$i5Rkls3LoyxzS8t9”, which has been copied from a router configuration file, for privilege level 2 using encryption type 7:<\/p>\n Command <\/strong><\/p>\n<\/td>\n Description <\/strong><\/p>\n<\/td>\n<\/tr>\n <\/p>\n To specify an additional layer of security over the enable password<\/strong> command, use the enable secret<\/strong> command in global configuration mode. To turn off the enable secret function, use the no<\/strong> form of this command.<\/p>\n enable secret <\/strong>[level<\/strong> level<\/em>] {password <\/em>| [encryption-type<\/em>] encrypted-password<\/em>}<\/p>\n no enable secret <\/strong>[level<\/strong> level<\/em>]<\/p>\n An enable password is defined as follows: \u2022Must contain from 1 to 25 uppercase and lowercase alphanumeric characters. \u2022Must not have a number as the first character. \u2022Can have leading spaces, but they are ignored. However, intermediate and trailing spaces are recognized. \u2022Can contain the question mark (?) character if you precede the question mark […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[47],"tags":[],"class_list":["post-341","post","type-post","status-publish","format-standard","hentry","category-asa5505"],"_links":{"self":[{"href":"https:\/\/www.thedarktimes.us\/wordpress\/wp-json\/wp\/v2\/posts\/341","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.thedarktimes.us\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.thedarktimes.us\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.thedarktimes.us\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thedarktimes.us\/wordpress\/wp-json\/wp\/v2\/comments?post=341"}],"version-history":[{"count":1,"href":"https:\/\/www.thedarktimes.us\/wordpress\/wp-json\/wp\/v2\/posts\/341\/revisions"}],"predecessor-version":[{"id":342,"href":"https:\/\/www.thedarktimes.us\/wordpress\/wp-json\/wp\/v2\/posts\/341\/revisions\/342"}],"wp:attachment":[{"href":"https:\/\/www.thedarktimes.us\/wordpress\/wp-json\/wp\/v2\/media?parent=341"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thedarktimes.us\/wordpress\/wp-json\/wp\/v2\/categories?post=341"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thedarktimes.us\/wordpress\/wp-json\/wp\/v2\/tags?post=341"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Examples<\/h3>\n
enable password level 2 pswd2<\/pre>\n
\u00a0<\/pre>\n
enable password level 2 5 $1$i5Rkls3LoyxzS8t9<\/pre>\n
Related Commands<\/h3>\n
\n\n
\n \u00a0<\/td>\n<\/tr>\n \n \n \n \n disable<\/strong><\/td>\n Exits privileged EXEC mode and returns to user EXEC mode.<\/td>\n<\/tr>\n \n enable<\/strong><\/td>\n Enters privileged EXEC mode.<\/td>\n<\/tr>\n \n enable secret<\/strong><\/td>\n Specifies an additional layer of security over the enable password<\/strong> command.<\/td>\n<\/tr>\n \n privilege<\/strong><\/td>\n Configures a new privilege level for users and associate commands with that privilege level.<\/td>\n<\/tr>\n \n service password-encryption<\/strong><\/td>\n Encrypts passwords.<\/td>\n<\/tr>\n \n show privilege<\/strong><\/td>\n Displays your current level of privilege.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n enable secret<\/h2>\n
Syntax Description<\/h3>\n
\n\n
\n \u00a0<\/td>\n<\/tr>\n \n level<\/strong> level<\/em><\/td>\n (Optional) Level for which the password applies. You can specify up to sixteen privilege levels, using numbers 0 through 15. Level 1 is normal EXEC-mode user privileges. If this argument is not specified in the command or in the no<\/strong> form of the command, the privilege level defaults to 15 (traditional enable privileges). The same holds true for the no<\/strong> form of the command.<\/td>\n<\/tr>\n \n password<\/em><\/td>\n Password for users to enter enable mode. This password should be different from the password created with the enable password<\/strong> command.<\/td>\n<\/tr>\n \n encryption-type<\/em><\/td>\n (Optional) Cisco-proprietary algorithm used to encrypt the password. Currently the only encryption type available for this command is 5. If you specify encryption-type<\/em>, the next argument you supply must be an encrypted password (a password encrypted by a Cisco router).<\/td>\n<\/tr>\n \n encrypted-password<\/em><\/td>\n Encrypted password you enter, copied from another router configuratio<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"