3 ms·
Any other actual router jockeys out there, aside from the folks just talking about it? I used to do BGP support at a regional ISP but I got out of that game al
by VLM 14y ago
Any other actual router jockeys out there, aside from the folks just talking about it? I used to do BGP support at a regional ISP but I got out of that game almost a decade ago. Dead end job, dead end company, dead end industry, low pay, and 24x7 on call. Of course it doesn't have to be that bad.
Anyway, the doctrine pushed at the time by cisco was embedding a password into a router was only for home or VERY small business users. Anyone with more than, say, 4 routers or so should be using some form of network authentication.
We had network auth in the very early 00s although all our routers had an emergency console password configured in (had to use it once, looked like 80 characters of line noise, maybe it was). That was in a sealed envelop in a lockbox. Because he had to update every router manually if that envelope opened, our one security guy got pretty annoyed if anyone ripped the envelope open.
Anyway the point that might be missed is in a carrot and stick method, this might be a very extreme application of the stick to get people to use network AAA systems instead of configuring their console and enable passwords in each router.
I guess modern cisco routers/IOS can do LDAP and KERBEROS its not all RADIUS from 1993, although old stuff does work.
I will say that in the dark days before we went network AAA it was an absolute nightmare when someone on the team quit and someone had to go manually thru every router on the network and change the passwords and distribute the new one to us all.
This will negatively impact people with 1990s architecture, but to the extent that they're already in a living hell anyway it won't be much worse.
Unfortunately I've worked at a few places with non-internet connected routers (or so they thought, anyway) where documentation was so poor you basically had to break in each time you needed access. Physical access to do hard recovery via a reboot was a PITA. Making it "easier to break in" would be seen as a feature not a bug in those locations.
- spydum 14y agoI can say with certainty there still remain tons of network infrastructures in the enterprise space who fail to comprehend the value of AAA. They still send router passwords around in plain text files. It really pains me to see how slowly enterprise customers adapt to operational trends (why change?, things have worked so far! facepalm)
- trout 14y agoThis is true - RADIUS and TACACS are the most secure way to access routers. I've found that nearly all routers in nearly all environments still have a local authentication. If you were to remove all network connections (or just the right one) you no longer have access to the authentication server and you would be totally locked out of the box since it doesn't cache any of the authentication. The running configuration of the router IS what you have to secure, and it needs to be stored under lock and key (SFTP, authenticated file share, etc). If you're sending it to non-shared parties you should remove the authentication from the configuration either manually or with 'show run brief'.
- EvanKelly 14y agoMost Cisco gear I've worked on (not ISP level) is extremely susceptible to local "attacks". I've never seen "disable-password-recovery" turned on in a config, and I've gone in and changed the CONFREG values dozens of times in order to grab an old config which no one knew the password too. I always assumed that Cisco kind of passed off physical security to the owners of the equipment, which actually made some sense to me, as long as the users were aware that the device wasn't physically secure.