<html><body><p><font size="2" face="sans-serif">Do you know of any good documentation to get tac_plus working with PAM? I am using this but it's not the most elaborate.</font><br><br><font size="2" face="sans-serif"><a href="http://www.shrubbery.net/pipermail/tac_plus/2009-January/000332.html">http://www.shrubbery.net/pipermail/tac_plus/2009-January/000332.html</a></font><br><br><br><img width="16" height="16" src="cid:1__=0ABBF418DFFAD6998f9e@AMERICAS.CORP.LOCAL" border="0" alt="Inactive hide details for Aaron Wasserott ---07/23/2015 12:41:44 PM---This email dist-list is for the shrubbery version of tac_"><font size="2" color="#424282" face="sans-serif">Aaron Wasserott ---07/23/2015 12:41:44 PM---This email dist-list is for the shrubbery version of tac_plus. <a href="http://www.shrubbery.net/tac_plus/">http://www.shrubbery.net/tac_plus/</a></font><br><br><font size="1" color="#5F5F5F" face="sans-serif">From: </font><font size="1" face="sans-serif">Aaron Wasserott <aaron.wasserott@viawest.com></font><br><font size="1" color="#5F5F5F" face="sans-serif">To: </font><font size="1" face="sans-serif">"Kevin.Cruse@Instinet.com" <Kevin.Cruse@Instinet.com>, </font><br><font size="1" color="#5F5F5F" face="sans-serif">Cc: </font><font size="1" face="sans-serif">"tac_plus@shrubbery.net" <tac_plus@shrubbery.net></font><br><font size="1" color="#5F5F5F" face="sans-serif">Date: </font><font size="1" face="sans-serif">07/23/2015 12:41 PM</font><br><font size="1" color="#5F5F5F" face="sans-serif">Subject: </font><font size="1" face="sans-serif">RE: [tac_plus] Cisco Nexus Authorization problem</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font size="2" color="#1F497D" face="Calibri">This email dist-list is for the shrubbery version of tac_plus.</font><br><font size="2" color="#1F497D" face="Calibri"> </font><br><a href="http://www.shrubbery.net/tac_plus/"><font size="2" color="#0000FF" face="Calibri"><u>http://www.shrubbery.net/tac_plus/</u></font></a><br><font size="2" color="#1F497D" face="Calibri"> </font><br><font size="2" color="#1F497D" face="Calibri">Reading the web page from where the MAVIS version is located I notice this:</font><br><font size="2" color="#1F497D" face="Calibri"> </font><br><font size="2" color="#1F497D" face="Calibri"><a href="http://www.pro-bono-publico.de/projects/index.html">http://www.pro-bono-publico.de/projects/index.html</a></font><br><font size="2" color="#1F497D" face="Calibri"> </font><br><a href="http://www.pro-bono-publico.de/projects/tac_plus.html"><font size="2" color="#1F497D" face="Calibri">tac_plus</font></a><font size="2" color="#1F497D" face="Calibri"> </font><a href="http://www.pro-bono-publico.de/projects/pdf/tac_plus.pdf"><font size="2" color="#1F497D" face="Calibri">[pdf]</font></a><font size="2" color="#1F497D" face="Calibri"> is an event-driven TACACS+ daemon which utilizes the MAVIS backend for authentication ***and authorization*** (and may get its user data from </font><a href="http://www.pro-bono-publico.de/projects/unpacked/mavis/perl/"><font size="2" color="#1F497D" face="Calibri">various</font></a><font size="2" color="#1F497D" face="Calibri"> </font><a href="http://www.pro-bono-publico.de/projects/unpacked/mavis/"><font size="2" color="#1F497D" face="Calibri">sources</font></a><font size="2" color="#1F497D" face="Calibri">, including PAM, LDAP, RADIUS and </font><a href="http://www.pro-bono-publico.de/projects/howto-tac_plus-ads.html"><font size="2" color="#1F497D" face="Calibri">ActiveDirectory</font></a><font size="2" color="#1F497D" face="Calibri">; suitable </font><a href="http://www.pro-bono-publico.de/projects/unpacked/mavis/perl/"><font size="2" color="#1F497D" face="Calibri">schema files</font></a><font size="2" color="#1F497D" face="Calibri"> for OpenLDAP are included). Supported features include IPv6, single-connection and much more.</font><br><font size="2" color="#1F497D" face="Calibri"> </font><br><font size="2" color="#1F497D" face="Calibri">Makes sense that some things won’t work the same across both version.</font><br><font size="2" color="#1F497D" face="Calibri"> </font><br><font size="2" face="Tahoma"><b>From:</b></font><font size="2" face="Tahoma"> Kevin.Cruse@Instinet.com [</font><font size="2" face="Tahoma"><a href="mailto:Kevin.Cruse@Instinet.com">mailto:Kevin.Cruse@Instinet.com</a></font><font size="2" face="Tahoma">] </font><font size="2" face="Tahoma"><b><br>Sent:</b></font><font size="2" face="Tahoma"> Thursday, July 23, 2015 10:35 AM</font><font size="2" face="Tahoma"><b><br>To:</b></font><font size="2" face="Tahoma"> Aaron Wasserott</font><font size="2" face="Tahoma"><b><br>Cc:</b></font><font size="2" face="Tahoma"> tac_plus@shrubbery.net</font><font size="2" face="Tahoma"><b><br>Subject:</b></font><font size="2" face="Tahoma"> RE: [tac_plus] Cisco Nexus Authorization problem</font><br><font size="3" face="Times New Roman"> </font><p><font size="2" face="Arial">I don't think mavvis build likes 'after authorization' I get an error when calling it. I used this documentation when setting up tac_plus:</font><font size="3" face="Times New Roman"><br></font><font size="2" color="#0000FF" face="Arial"><u><br></u></font><a href="http://sysmagazine.com/posts/217669/"><font size="2" color="#0000FF" face="Arial"><u>http://sysmagazine.com/posts/217669/</u></font></a><font size="3" face="Times New Roman"><br></font><font size="2" face="Arial"><br>error with above setup:<br>/usr/local/etc/tac_plus.cfg:449: Unrecognized keyword 'after' (user/group: snm)<br>8334: /usr/local/etc/tac_plus.cfg:449: Unrecognized keyword 'after' (user/group: snm)</font><font size="3" face="Times New Roman"><br></font><font size="2" face="Arial"><br>I tried same configuration in native tac_plus setup and there was no error. I am trying to get tac_plus to work with PAM but kept running into issues and it was not working seamlessly which is why i setup the mavvis version. I am working on getting PAM to work properly with native tac_plus since the mavvis build seems to introduce more problems then fixes.</font><font size="3" face="Times New Roman"><br><br><br></font><img src="cid:1__=0ABBF418DFFAD6998f9e@AMERICAS.CORP.LOCAL" width="16" height="16" alt="Inactive hide details for Aaron Wasserott ---07/23/2015 11:18:53 AM---It doesn’t look like Mavis would interfere with authoriz"><font size="2" color="#424282" face="Arial">Aaron Wasserott ---07/23/2015 11:18:53 AM---It doesn’t look like Mavis would interfere with authorization. Based on your configs authorization s</font><font size="3" face="Times New Roman"><br></font><font size="1" color="#5F5F5F" face="Arial"><br>From: </font><font size="1" face="Arial">Aaron Wasserott <</font><a href="mailto:aaron.wasserott@viawest.com"><font size="1" color="#0000FF" face="Arial"><u>aaron.wasserott@viawest.com</u></font></a><font size="1" face="Arial">></font><font size="1" color="#5F5F5F" face="Arial"><br>To: </font><font size="1" face="Arial">"</font><a href="mailto:Kevin.Cruse@Instinet.com"><font size="1" color="#0000FF" face="Arial"><u>Kevin.Cruse@Instinet.com</u></font></a><font size="1" face="Arial">" <</font><a href="mailto:Kevin.Cruse@Instinet.com"><font size="1" color="#0000FF" face="Arial"><u>Kevin.Cruse@Instinet.com</u></font></a><font size="1" face="Arial">>, </font><font size="1" color="#5F5F5F" face="Arial"><br>Cc: </font><font size="1" face="Arial">"</font><a href="mailto:tac_plus@shrubbery.net"><font size="1" color="#0000FF" face="Arial"><u>tac_plus@shrubbery.net</u></font></a><font size="1" face="Arial">" <</font><a href="mailto:tac_plus@shrubbery.net"><font size="1" color="#0000FF" face="Arial"><u>tac_plus@shrubbery.net</u></font></a><font size="1" face="Arial">></font><font size="1" color="#5F5F5F" face="Arial"><br>Date: </font><font size="1" face="Arial">07/23/2015 11:18 AM</font><font size="1" color="#5F5F5F" face="Arial"><br>Subject: </font><font size="1" face="Arial">RE: [tac_plus] Cisco Nexus Authorization problem</font><br><hr width="100%" size="2" align="left" noshade><br><font size="3" face="Times New Roman"><br><br></font><font size="2" color="#1F497D" face="Calibri"><br>It doesn’t look like Mavis would interfere with authorization. Based on your configs authorization should still be handled by tac_plus itself. <br> <br>Linking tac_plus.conf to do_auth is done with the stanza “</font><font size="2" face="Courier New">after authorization</font><font size="2" color="#1F497D" face="Calibri">“ inside a user or group definition.<br> <br>John Fraizer did a good write-up of how to use do_auth here:<br> </font><font size="3" color="#0000FF" face="Times New Roman"><u><br></u></font><a href="http://www.shrubbery.net/pipermail/tac_plus/2015-April/001622.html"><font size="2" color="#0000FF" face="Calibri"><u>http://www.shrubbery.net/pipermail/tac_plus/2015-April/001622.html</u></font></a><font size="2" color="#1F497D" face="Calibri"><br> <br>Locate your source for tac_plus and find the do_auth.py file. Inside that are some good instructions for setting it up. The web page for do_auth is here and has some specific examples:<br> </font><font size="2" color="#0000FF" face="Calibri"><u><br></u></font><a href="http://www.tacacs.org/"><font size="2" color="#0000FF" face="Calibri"><u>http://www.tacacs.org/</u></font></a><font size="2" color="#1F497D" face="Calibri"><br> </font><font size="2" face="Tahoma"><b><br>From:</b></font><font size="2" face="Tahoma"> </font><a href="mailto:Kevin.Cruse@Instinet.com"><font size="2" color="#0000FF" face="Tahoma"><u>Kevin.Cruse@Instinet.com</u></font></a><font size="2" face="Tahoma"> [</font><a href="mailto:Kevin.Cruse@Instinet.com"><font size="2" color="#0000FF" face="Tahoma"><u>mailto:Kevin.Cruse@Instinet.com</u></font></a><font size="2" face="Tahoma">] </font><font size="2" face="Tahoma"><b><br>Sent:</b></font><font size="2" face="Tahoma"> Thursday, July 23, 2015 8:59 AM</font><font size="2" face="Tahoma"><b><br>To:</b></font><font size="2" face="Tahoma"> Aaron Wasserott</font><font size="2" face="Tahoma"><b><br>Cc:</b></font><font size="2" face="Tahoma"> </font><a href="mailto:tac_plus@shrubbery.net"><font size="2" color="#0000FF" face="Tahoma"><u>tac_plus@shrubbery.net</u></font></a><font size="2" face="Tahoma"><b><br>Subject:</b></font><font size="2" face="Tahoma"> RE: [tac_plus] Cisco Nexus Authorization problem</font><font size="3" face="Times New Roman"><br> </font><p><font size="2" face="Arial">I am using the mavis backend and wonder if that is the problem? How do i configure do_auth? I am using tac_plus version 201503121920. I cannot find great example of how to use do_auth with existing configuration ie how do i tell the config file to use do_auth? <br><br>id = tac_plus {<br> debug = AUTHEN ACCT MAVIS PACKET<br> access log = /var/log/tac_plus/access/%Y%m%d.log<br> authentication log = /var/log/tac_plus/auth/%Y%m%d.log<br> accounting log = /var/log/tac_plus/acct/%Y%m%d.log<br> authorization log = /var/log/tac_plus/authorization/%Y%m%d.log<br><br> mavis module = external {<br> setenv LDAP_SERVER_TYPE = "microsoft"<br> setenv LDAP_HOSTS = "server:389"<br> setenv LDAP_BASE = "dc=domain,dc=corp,dc=local"<br> setenv LDAP_SCOPE = sub<br> #setenv LDAP_FILTER = "(&(objectclass=user) (sAMAccountName = % s))"<br> setenv LDAP_USER = "svcTacacs"<br> setenv LDAP_PASSWD = "T@c@c$!"<br> setenv AD_GROUP_PREFIX = "prv-AMS_Tacacs"<br> setenv EXPAND_AD_GROUP_MEMBERSHIP = 1<br> setenv FLAG_USE_MEMBEROF = 1<br> #setenv REQUIRE_TACACS_GROUP_PREFIX = 1<br> #setenv FLAG_USE_MEMBEROF = 1<br><br> exec = /usr/local/lib/mavis/mavis_tacplus_ldap.pl<br> }<br><br> login backend = mavis<br> user backend = mavis<br> pap backend = mavis</font><font size="3" face="Times New Roman"><br></font><font size="2" face="Arial"><br><br> host = world {<br> address = ::/0<br> prompt = "This is a protected device. Unauthorized access is prohibited\n"<br> enable 15 = clear secret<br> key = password<br> }<br><br> group = admin {<br> message = "[Admin Privileges]"<br> default service = permit<br> service = shell {<br> default command = permit<br> default attribute = permit<br> set priv-lvl = 15<br> cmd = debug{deny .*}<br><br> }<br> }</font><font size="3" face="Times New Roman"><br><br><br><br></font><img src="cid:1__=0ABBF418DFFAD6998f9e@AMERICAS.CORP.LOCAL" width="16" height="16" alt="Inactive hide details for Aaron Wasserott ---07/22/2015 03:28:27 PM---Kevin, I just tested this and it works for me. User can r"><font size="2" color="#424282" face="Arial">Aaron Wasserott ---07/22/2015 03:28:27 PM---Kevin, I just tested this and it works for me. User can run show commands, but not enter conf t mode</font><font size="1" color="#5F5F5F" face="Arial"><br><br>From: </font><font size="1" face="Arial">Aaron Wasserott <</font><a href="mailto:aaron.wasserott@viawest.com"><font size="1" color="#0000FF" face="Arial"><u>aaron.wasserott@viawest.com</u></font></a><font size="1" face="Arial">></font><font size="1" color="#5F5F5F" face="Arial"><br>To: </font><font size="1" face="Arial">"</font><a href="mailto:Kevin.Cruse@Instinet.com"><font size="1" color="#0000FF" face="Arial"><u>Kevin.Cruse@Instinet.com</u></font></a><font size="1" face="Arial">" <</font><a href="mailto:Kevin.Cruse@Instinet.com"><font size="1" color="#0000FF" face="Arial"><u>Kevin.Cruse@Instinet.com</u></font></a><font size="1" face="Arial">>, </font><font size="1" color="#5F5F5F" face="Arial"><br>Cc: </font><font size="1" face="Arial">"</font><a href="mailto:tac_plus@shrubbery.net"><font size="1" color="#0000FF" face="Arial"><u>tac_plus@shrubbery.net</u></font></a><font size="1" face="Arial">" <</font><a href="mailto:tac_plus@shrubbery.net"><font size="1" color="#0000FF" face="Arial"><u>tac_plus@shrubbery.net</u></font></a><font size="1" face="Arial">></font><font size="1" color="#5F5F5F" face="Arial"><br>Date: </font><font size="1" face="Arial">07/22/2015 03:28 PM</font><font size="1" color="#5F5F5F" face="Arial"><br>Subject: </font><font size="1" face="Arial">RE: [tac_plus] Cisco Nexus Authorization problem</font><br><hr width="100%" size="2" align="left" noshade><br><font size="3" face="Times New Roman"><br><br></font><font size="2" color="#1F497D" face="Calibri"><br><br>Kevin,<br><br>I just tested this and it works for me. User can run show commands, but not enter conf t mode. <br><br>Arista DCS-7050S-52-R running code 4.8.3. In production we run do_auth. It comes bundled with the latest version of tac_plus and makes tweaking authorization a lot easier. It’s more scalable, syntax is cleaner, and it has its own authorization logs which are easier to read.<br><br># tac_plus.conf<br><br>group = tier1 {<br> default service = permit<br> login = PAM<br> pap = PAM<br> default command = deny<br> cmd = show {permit .*}<br> service = exec {<br> priv-lvl = 15<br> }<br> service = raccess {<br> priv-lvl = 0<br> }<br>}<br><br>user = first.last {<br> member = tier1<br>}<br><br># switch AAA commands<br>aaa group server tacacs+ TacGroup<br>aaa authentication login default group TacGroup local<br>aaa authorization exec default group TacGroup none<br>aaa authorization commands 15 default group TacGroup none<br>aaa accounting exec default start-stop group TacGroup<br>aaa accounting commands 15 default start-stop group TacGroup<br>no aaa root<br><br>-Aaron</font><font size="2" face="Tahoma"><b><br><br>From:</b></font><font size="2" face="Tahoma"> </font><a href="mailto:Kevin.Cruse@Instinet.com"><font size="2" color="#0000FF" face="Tahoma"><u>Kevin.Cruse@Instinet.com</u></font></a><font size="2" face="Tahoma"> [</font><a href="mailto:Kevin.Cruse@Instinet.com"><font size="2" color="#0000FF" face="Tahoma"><u>mailto:Kevin.Cruse@Instinet.com</u></font></a><font size="2" face="Tahoma">] </font><font size="2" face="Tahoma"><b><br>Sent:</b></font><font size="2" face="Tahoma"> Wednesday, July 22, 2015 12:44 PM</font><font size="2" face="Tahoma"><b><br>To:</b></font><font size="2" face="Tahoma"> Aaron Wasserott</font><font size="2" face="Tahoma"><b><br>Cc:</b></font><font size="2" face="Tahoma"> </font><a href="mailto:tac_plus@shrubbery.net"><font size="2" color="#0000FF" face="Tahoma"><u>tac_plus@shrubbery.net</u></font></a><font size="2" face="Tahoma"><b><br>Subject:</b></font><font size="2" face="Tahoma"> RE: [tac_plus] Cisco Nexus Authorization problem</font><p><font size="2" face="Arial">Aaron<br><br>Do you have experience with Arista? It seems I am having similar problem with this device. Authentication works fine, but once i login and send enable password I can run any command i'd like. It's not restricting access to my preconfigured commands:<br><br><br>Arista1#sh run | i aaa<br>aaa group server tacacs+ CiscoACS<br>aaa authentication login default group CiscoACS local<br>aaa authorization exec default group CiscoACS local<br>aaa authorization commands all default group CiscoACS local<br>aaa accounting exec default start-stop group CiscoACS<br>aaa accounting commands all default start-stop group CiscoACS<br>no aaa root<br><br>----- <br><br> user = testuser {<br> login = clear "test123"<br> pap = clear "test123"<br> member = snm<br> }<br><br><br> group = snm {<br> default service = deny<br> service = shell {<br> set shell:roles="\"network-admin\""<br> default command = deny<br> default attribute = deny<br> set priv-lvl = 15<br> cmd = configure {deny .*}<br> cmd = clear {<br> permit "counters"<br> permit "qos stat"<br> permit "mls qos int"<br> }<br> cmd = disable {permit .*}<br> cmd = enable {permit .*}<br> cmd = end {permit .*}<br> cmd = exit {permit .*}<br> cmd = logout {permit .*}<br> cmd = ping {permit .*}<br> cmd = set {<br> permit "length 0"<br> }<br> cmd = show {<br> deny "controllers vip"<br> permit .*<br> }<br> cmd = skip-page-display {permit .*}<br> cmd = terminal {<br> permit "length 0"<br> }<br> cmd = write {<br> permit "network"<br> permit "terminal"<br> permit "memory"<br> }<br> }<br> }<br><br>----<br><br><br>Arista1 login: testuser<br>Password:<br>Last login: Wed Jul 22 18:49:42 on ttyS0<br>Arista1>en<br>Password:<br>Arista1#conf t <--- This command should be restricted<br>Arista1(config)#interface eth 10 <--- This command should be restricted<br>Arista1(config-if-Et10)#shut <--- This command should be restricted<br>Arista1(config-if-Et10)#end<br>Arista1#exit</font><font size="3" face="Times New Roman"><br><br><br><br></font><img src="cid:1__=0ABBF418DFFAD6998f9e@AMERICAS.CORP.LOCAL" width="16" height="16" alt="Inactive hide details for Aaron Wasserott ---07/16/2015 09:26:32 PM---Try changing "service = shell" to "service = exec" and se"><font size="2" color="#424282" face="Arial">Aaron Wasserott ---07/16/2015 09:26:32 PM---Try changing "service = shell" to "service = exec" and see if that works. I have NX-OS working fine</font><font size="1" color="#5F5F5F" face="Arial"><br><br>From: </font><font size="1" face="Arial">Aaron Wasserott <</font><a href="mailto:aaron.wasserott@viawest.com"><font size="1" color="#0000FF" face="Arial"><u>aaron.wasserott@viawest.com</u></font></a><font size="1" face="Arial">></font><font size="1" color="#5F5F5F" face="Arial"><br>To: </font><font size="1" face="Arial">"</font><a href="mailto:Kevin.Cruse@Instinet.com"><font size="1" color="#0000FF" face="Arial"><u>Kevin.Cruse@Instinet.com</u></font></a><font size="1" face="Arial">" <</font><a href="mailto:Kevin.Cruse@Instinet.com"><font size="1" color="#0000FF" face="Arial"><u>Kevin.Cruse@Instinet.com</u></font></a><font size="1" face="Arial">>, "</font><a href="mailto:tac_plus@shrubbery.net"><font size="1" color="#0000FF" face="Arial"><u>tac_plus@shrubbery.net</u></font></a><font size="1" face="Arial">" <</font><a href="mailto:tac_plus@shrubbery.net"><font size="1" color="#0000FF" face="Arial"><u>tac_plus@shrubbery.net</u></font></a><font size="1" face="Arial">>, </font><font size="1" color="#5F5F5F" face="Arial"><br>Date: </font><font size="1" face="Arial">07/16/2015 09:26 PM</font><font size="1" color="#5F5F5F" face="Arial"><br>Subject: </font><font size="1" face="Arial">RE: [tac_plus] Cisco Nexus Authorization problem</font><br><hr width="100%" size="2" align="left" noshade><br><font size="3" face="Times New Roman"><br><br></font><font size="2" face="Courier New"><br><br><br>Try changing "service = shell" to "service = exec" and see if that works. I have NX-OS working fine using that. Also, I have never seen the shell service used in real-world examples for network devices. But reading the manpage it appears it should work to prevent them from entering configuration mode, as long as your AAA commands are set right.<br><br>service=shell<br>for exec startup, and also for command authorizations. Requires: aaa authorization exec tacacs+<br><br>Whether authorization happens, and at which prompt level, depends on the aaa authorization settings. It's possible to only restrict exec level commands, and prevent them from entering the 'conf t' command. But if you want them in conf t mode but restrict their commands at that level, you need to enable something like this:<br><br>aaa authorization config-commands default group myTacacsGroup local<br><br>If changing the service doesn't work, include the AAA commands on your NX-OS switches.<br><br>-----Original Message-----<br>From: tac_plus [</font><a href="mailto:tac_plus-bounces@shrubbery.net"><font size="2" color="#0000FF" face="Courier New"><u>mailto:tac_plus-bounces@shrubbery.net</u></font></a><font size="2" face="Courier New">] On Behalf Of </font><a href="mailto:Kevin.Cruse@Instinet.com"><font size="2" color="#0000FF" face="Courier New"><u>Kevin.Cruse@Instinet.com</u></font></a><font size="2" face="Courier New"><br>Sent: Thursday, July 16, 2015 3:40 PM<br>To: </font><a href="mailto:tac_plus@shrubbery.net"><font size="2" color="#0000FF" face="Courier New"><u>tac_plus@shrubbery.net</u></font></a><font size="2" face="Courier New"><br>Subject: [tac_plus] Cisco Nexus Authorization problem<br><br><br><br>Hello<br><br>I have configured TACPLUS to work with cisco nexus device. I am able to successfully authenticate, however, I am able to run all commands on router. It seems the router is not restricted to the commands specified in my group config. Has anyone gotten Cisco nexus to work properly with tacplus? I need to limit certain users and cannot get this working properly. Any help is greatly appreciated!!! Thanks.<br><br>Group Config:<br><br> group = snm {<br> default service = deny<br> service = shell {<br> set shell:roles="\"network-admin\""<br> default command = deny<br> default attribute = deny<br> set priv-lvl = 15<br> cmd = configure {deny .*}<br> cmd = clear {<br> permit "counters"<br> permit "qos stat"<br> permit "mls qos int"<br> }<br> cmd = disable {permit .*}<br> cmd = enable {permit .*}<br> cmd = end {permit .*}<br> cmd = exit {permit .*}<br> cmd = logout {permit .*}<br> cmd = ping {permit .*}<br> cmd = set {<br> permit "length 0"<br> }<br> cmd = show {<br> deny "controllers vip"<br> permit .*<br> }<br> cmd = skip-page-display {permit .*}<br> cmd = terminal {<br> permit "length 0"<br> }<br> cmd = write {<br> permit "network"<br> permit "terminal"<br> permit "memory"<br> }<br> }<br> }<br><br><br> user = testuser {<br><br> member = snm<br> }<br><br><br>Session output from router:<br><br>telnet labrouter<br>Trying labrouter...<br>Connected to labrouter.<br>Escape character is '^]'.<br>User Access Verification<br>login: testuser<br>Password:<br>Cisco Nexus Operating System (NX-OS) Software TAC support: </font><a href="http://www.cisco.com/tac"><font size="2" color="#0000FF" face="Courier New"><u>http://www.cisco.com/tac</u></font></a><font size="2" face="Courier New"> Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.<br>The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.0 or the GNU Lesser General Public License (LGPL) Version 2.1. A copy of each such license is available at </font><a href="http://www.opensource.org/licenses/gpl-2.0.php"><font size="2" color="#0000FF" face="Courier New"><u>http://www.opensource.org/licenses/gpl-2.0.php</u></font></a><font size="2" face="Courier New"> and </font><a href="http://www.opensource.org/licenses/lgpl-2.1.php"><font size="2" color="#0000FF" face="Courier New"><u>http://www.opensource.org/licenses/lgpl-2.1.php</u></font></a><font size="2" face="Courier New"><br>LABROUTER# configure<br><------------------------------------------------------------ This should be denied Enter configuration commands, one per line. End with CNTL/Z.<br>LABROUTER(config)# interface ethernet 1/1 configure<br><------------------------------------------------------------ This should be denied LABROUTER(config-if)# shut<br><------------------------------------------------------------ This should be denied LABROUTER(config-if)# no shut<br><------------------------------------------------------------ This should be denied LABROUTER(config-if)# end LABROUTER#<br><br>========================================================================================================= <<<< Disclaimer >>>> This message is intended solely for use by the named addressee(s). If you receive this transmission in error, please immediately notify the sender and destroy this message in its entirety, whether in electronic or hard copy format. Any unauthorized use (and reliance thereon), copying, disclosure, retention, or distribution of this transmission or the material in this transmission is forbidden. We reserve the right to monitor and archive electronic communications. This material does not constitute an offer or solicitation with respect to the purchase or sale of any security. It should not be construed to contain any recommendation regarding any security or strategy. Any views expressed are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. This communication is provided on an “as is” basis. It contains material that is owned by Instinet Incorporated, its subsidiaries or its or their licensors, and may not, in whole or in part, be (i) copied, photocopied or duplicated in any form, by any means, or (ii) redistributed, posted, published, excerpted, or quoted without Instinet Incorporated's prior written consent. Please access the following link for important information and instructions: </font><a href="http://instinet.com/includes/index.jsp?thePage=/html/le_index.txt"><font size="2" color="#0000FF" face="Courier New"><u>http://instinet.com/includes/index.jsp?thePage=/html/le_index.txt</u></font></a><font size="2" face="Courier New"> Securities products and services are provided by locally registered brokerage subsidiaries of Instinet Incorporated: Instinet Australia Pty Limited (ACN: 131 253 686 AFSL No: 327834), regulated by the Australian Securities & Investments Commission; Instinet Canada Limited, member IIROC/CIPF; Instinet Pacific Limited, authorized and regulated by the Securities and Futures Commission of Hong Kong; Instinet Singapore Services Private Limited, regulated by the Monetary Authority of Singapore, trading member of The Singapore Exchange Securities Trading Private Limited and clearing member of The Central Depository (Pte) Limited; and Instinet, LLC, member SIPC.<br><br>=========================================================================================================<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <</font><a href="http://www.shrubbery.net/pipermail/tac_plus/attachments/20150716/5c309608/attachment.html"><font size="2" color="#0000FF" face="Courier New"><u>http://www.shrubbery.net/pipermail/tac_plus/attachments/20150716/5c309608/attachment.html</u></font></a><font size="2" face="Courier New">><br>_______________________________________________<br>tac_plus mailing list</font><font size="3" color="#0000FF" face="Times New Roman"><u><br></u></font><a href="mailto:tac_plus@shrubbery.net"><font size="2" color="#0000FF" face="Courier New"><u>tac_plus@shrubbery.net</u></font></a><font size="3" color="#0000FF" face="Times New Roman"><u><br></u></font><a href="http://www.shrubbery.net/mailman/listinfo/tac_plus"><font size="2" color="#0000FF" face="Courier New"><u>http://www.shrubbery.net/mailman/listinfo/tac_plus</u></font></a><font size="2" face="Courier New"><br>This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply and immediately delete all copies of the message.</font><font size="1" face="Georgia"><i><br><br><br>========================================================================================================= </i></font><p><font size="1" face="Georgia"><b><i><<<< Disclaimer >>>></i></b></font><font size="1" face="Georgia"><i> </i></font><p><font size="1" face="Georgia"><i>This message is intended solely for use by the named addressee(s). If you receive this transmission in error, please immediately notify the sender and destroy this message in its entirety, whether in electronic or hard copy format. Any unauthorized use (and reliance thereon), copying, disclosure, retention, or distribution of this transmission or the material in this transmission is forbidden. We reserve the right to monitor and archive electronic communications. This material does not constitute an offer or solicitation with respect to the purchase or sale of any security. It should not be construed to contain any recommendation regarding any security or strategy. Any views expressed are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. This communication is provided on an “as is” basis. It contains material that is owned by Instinet Incorporated, its subsidiaries or its or their licensors, and may not, in whole or in part, be (i) copied, photocopied or duplicated in any form, by any means, or (ii) redistributed, posted, published, excerpted, or quoted without Instinet Incorporated's prior written consent. Please access the following link for important information and instructions: </i></font><a href="%20http:/instinet.com/includes/index.jsp?thePage=/html/le_index.txt"><font size="1" color="#0000FF" face="Georgia"><i><u>http://instinet.com/includes/index.jsp?thePage=/html/le_index.txt</u></i></font></a><font size="1" face="Georgia"><i> </i></font><p><font size="1" face="Georgia"><i>Securities products and services are provided by locally registered brokerage subsidiaries of Instinet Incorporated: Instinet Australia Pty Limited (ACN: 131 253 686 AFSL No: 327834), regulated by the Australian Securities & Investments Commission; Instinet Canada Limited, member IIROC/CIPF; Instinet Pacific Limited, authorized and regulated by the Securities and Futures Commission of Hong Kong; Instinet Singapore Services Private Limited, regulated by the Monetary Authority of Singapore, trading member of The Singapore Exchange Securities Trading Private Limited and clearing member of The Central Depository (Pte) Limited; and Instinet, LLC, member SIPC. </i></font><p><font size="1" face="Georgia"><i><br><br>========================================================================================================= </i></font><p><font size="3" face="Times New Roman">This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply and immediately delete all copies of the message. </font><font size="1" face="Georgia"><i><br><br><br>========================================================================================================= </i></font><p><font size="1" face="Georgia"><b><i><<<< Disclaimer >>>></i></b></font><font size="1" face="Georgia"><i> </i></font><p><font size="1" face="Georgia"><i>This message is intended solely for use by the named addressee(s). If you receive this transmission in error, please immediately notify the sender and destroy this message in its entirety, whether in electronic or hard copy format. Any unauthorized use (and reliance thereon), copying, disclosure, retention, or distribution of this transmission or the material in this transmission is forbidden. We reserve the right to monitor and archive electronic communications. This material does not constitute an offer or solicitation with respect to the purchase or sale of any security. It should not be construed to contain any recommendation regarding any security or strategy. Any views expressed are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. This communication is provided on an “as is” basis. It contains material that is owned by Instinet Incorporated, its subsidiaries or its or their licensors, and may not, in whole or in part, be (i) copied, photocopied or duplicated in any form, by any means, or (ii) redistributed, posted, published, excerpted, or quoted without Instinet Incorporated's prior written consent. Please access the following link for important information and instructions: </i></font><a href="%20http:/instinet.com/includes/index.jsp?thePage=/html/le_index.txt"><font size="1" color="#0000FF" face="Georgia"><i><u>http://instinet.com/includes/index.jsp?thePage=/html/le_index.txt</u></i></font></a><font size="1" face="Georgia"><i> </i></font><p><font size="1" face="Georgia"><i>Securities products and services are provided by locally registered brokerage subsidiaries of Instinet Incorporated: Instinet Australia Pty Limited (ACN: 131 253 686 AFSL No: 327834), regulated by the Australian Securities & Investments Commission; Instinet Canada Limited, member IIROC/CIPF; Instinet Pacific Limited, authorized and regulated by the Securities and Futures Commission of Hong Kong; Instinet Singapore Services Private Limited, regulated by the Monetary Authority of Singapore, trading member of The Singapore Exchange Securities Trading Private Limited and clearing member of The Central Depository (Pte) Limited; and Instinet, LLC, member SIPC. </i></font><p><font size="1" face="Georgia"><i><br><br>========================================================================================================= </i></font><p><font size="3" face="Times New Roman">This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply and immediately delete all copies of the message. </font><br><font size="1" face="Georgia"><i><br><br>========================================================================================================= </i></font><p><font size="1" face="Georgia"><b><i><<<< Disclaimer >>>></i></b></font><font size="1" face="Georgia"><i> </i></font><p><font size="1" face="Georgia"><i>This message is intended solely for use by the named addressee(s). If you receive this transmission in error, please immediately notify the sender and destroy this message in its entirety, whether in electronic or hard copy format. Any unauthorized use (and reliance thereon), copying, disclosure, retention, or distribution of this transmission or the material in this transmission is forbidden. We reserve the right to monitor and archive electronic communications. This material does not constitute an offer or solicitation with respect to the purchase or sale of any security. It should not be construed to contain any recommendation regarding any security or strategy. Any views expressed are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. This communication is provided on an “as is” basis. It contains material that is owned by Instinet Incorporated, its subsidiaries or its or their licensors, and may not, in whole or in part, be (i) copied, photocopied or duplicated in any form, by any means, or (ii) redistributed, posted, published, excerpted, or quoted without Instinet Incorporated's prior written consent. Please access the following link for important information and instructions: </i></font><a href="%20http:/instinet.com/includes/index.jsp?thePage=/html/le_index.txt"><font size="1" color="#0000FF" face="Georgia"><i><u>http://instinet.com/includes/index.jsp?thePage=/html/le_index.txt</u></i></font></a><font size="1" face="Georgia"><i> </i></font><p><font size="1" face="Georgia"><i>Securities products and services are provided by locally registered brokerage subsidiaries of Instinet Incorporated: Instinet Australia Pty Limited (ACN: 131 253 686 AFSL No: 327834), regulated by the Australian Securities & Investments Commission; Instinet Canada Limited, member IIROC/CIPF; Instinet Pacific Limited, authorized and regulated by the Securities and Futures Commission of Hong Kong; Instinet Singapore Services Private Limited, regulated by the Monetary Authority of Singapore, trading member of The Singapore Exchange Securities Trading Private Limited and clearing member of The Central Depository (Pte) Limited; and Instinet, LLC, member SIPC. </i></font><p><font size="1" face="Georgia"><i><br><br>========================================================================================================= </i></font><p><font size="3" face="serif">This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply and immediately delete all copies of the message. </font><p><font face="sans-serif"><div style="font-size:12px; font-style:italic; font-family:georgia,arial,sans-serif">
<br><br>
=========================================================================================================
<div style="font-size:12px; font-style:italic; font-family:georgia,arial,sans-serif">
<p>
<B><<<< Disclaimer >>>></B>
<p>
This message is intended solely for use by the named addressee(s). If you receive this transmission in error, please immediately notify the sender and destroy this message in its entirety, whether in electronic or hard copy format. Any unauthorized use (and reliance thereon), copying, disclosure, retention, or distribution of this transmission or the material in this transmission is forbidden. We reserve the right to monitor and archive electronic communications. This material does not constitute an offer or solicitation with respect to the purchase or sale of any security. It should not be construed to contain any recommendation regarding any security or strategy. Any views expressed are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. This communication is provided on an “as is” basis. It contains material that is owned by Instinet Incorporated, its subsidiaries or its or their licensors, and may not, in whole or in part, be (i) copied, photocopied or duplicated in any form, by any means, or (ii) redistributed, posted, published, excerpted, or quoted without Instinet Incorporated's prior written consent. Please access the following link for important information and instructions: <a href=" http://instinet.com/includes/index.jsp?thePage=/html/le_index.txt"> http://instinet.com/includes/index.jsp?thePage=/html/le_index.txt</a>
<p>
Securities products and services are provided by locally registered brokerage subsidiaries of Instinet Incorporated: Instinet Australia Pty Limited (ACN: 131 253 686 AFSL No: 327834), regulated by the Australian Securities & Investments Commission; Instinet Canada Limited, member IIROC/CIPF; Instinet Pacific Limited, authorized and regulated by the Securities and Futures Commission of Hong Kong; Instinet Singapore Services Private Limited, regulated by the Monetary Authority of Singapore, trading member of The Singapore Exchange Securities Trading Private Limited and clearing member of The Central Depository (Pte) Limited; and Instinet, LLC, member SIPC.
<p>
<br><br>
=========================================================================================================
</div></font>
</body></html>