5 ms·
When I worked at a company that made some networking equipment SNMP was a constant problem, security, bugs that crash the device and so on. It became clear to
by duxup 1y ago
When I worked at a company that made some networking equipment SNMP was a constant problem, security, bugs that crash the device and so on.
It became clear to me over time that the pattern at that company was to direct the less great engineering resources to SNMP...
- hylaride 1y agoSNMP is one of those good ideas in theory, bad ideas in practice. Anyways, Cisco hasn’t done great engineering pretty much since the dotcom bust. They’re now essentially a giant PE firm that grows through acquisitions and then milks them dry. It’s a classic case of the accountants took over.
- FuriouslyAdrift 1y agoCisco's old model (which worked very well for them) was to develop an outside startup and see if they gain traction while keeping at least some financial/control stake to democratize the risk and spend and then spin-in if it is succesful (or sell off).
- Our_Benefactors 1y agoI interviewed with Cisco once. They wanted me to do a take home interview. Implement an api, make a web app, host the GitHub repo somewhere, host the web app so it was publicly available for them to test, make sure I included full documentation and test suite. A fully tested and deployed full stack application, from scratch, as a “take home test”. I said “no, I don't work for free”. That was by far the most egregious example I’ve encountered of “we are trying to get unpaid labor from our interview process.”
- FuriouslyAdrift 1y agoYeah, that's ridiculous. It's not just FAANGs that pull this crap.
- lawlessone 1y agoFAANGS often start it and then everyone else thinks it's going to make their company great if they do it too.
- chuckadams 1y agoI think it's reasonable if one's applying as a full-stack developer, the app is something like a simple TODO list that isn't anything they'd actually use, and there isn't a high expectation of polish. Few hours of work at most, not days, and definitely not a first-interview thing. Expecting you to host it yourself is definitely unreasonable: they can build and run it themselves if they care that much, but eyeballing the source ought to be good enough in most cases.
- jacquesm 1y agoIt's only ok if they pay you for your time.
- deleted 1y ago[deleted]
- stuff4ben 1y agoAh good ole MPLS (Mario, Prem, Luca, and I can't remember who was S)...
- lima 1y agoSoni
- themafia 1y agoSounds like something an equity or financial firm should do. I'm not sure why a networking company decided to make that their core competency.
- MangoToupe 1y agoSelfishly, I'm happy and grateful they bought out chez scheme, opened it up, and funded development. Do I understand why? No, and I'm not going to question it! EDIT: it seems like it was an acquihire of Dybvig and the team working on chez for something under NDA.
- rubymancer 1y agoCisco employee here, this is spot on. I was at a startup they acquired ~4 years ago, by now it's just about milked completely dry. Even though our product is close to industry-leading, they laid off our product manager, then another one, the QA team, and half of the devs. Unsurprisingly the product is falling apart. It's not a company that attempts to produce value, as with so many others the product is the stock price. The MBAs are showing some kind of savings on a spreadsheet somewhere though, so I suppose all the sacrifices are worth it.
- downrightmike 1y agoThat's what MBAs did to Intel too
- neuroelectron 1y agoAmerican tech sector is being destroyed so it can be replaced by _____ and their surveillance state. It's death by a thousand cuts, labor supply, education, taxes, regulation, finance, dependencies, versioning, operating systems, etc. all are being made obfuscated, complex and frustrating to slow advancement and ultimately unstable and impossible to maintain. Most of our tech stack already has surveillance built in and that is already being co-opted and we're well on our way of having it outsourced to a foreign state.
- iwontberude 1y agoand couldn't even get the stock to be worth anything
- FuriouslyAdrift 1y agoSNMP v3 at least has some security in mind, but a lot of devices are just v1 or v2c which are basically unsecured. Allowing ANY write access via SNMP is a bad idea in my opinion, unless you segment it out into it's own secured management or out-of-band network. Even then... I'd be worried. Network infrastructure security has a lot of unsolved gotchas and not a lot of industry desire to fix. Most of what everyone interacts with is in an abstracted or virtualized layer on top of the old plumbing.
- elevation 1y agoSNMP v2c is still common in the embedded world because it's protected with a simple password so it just works out of the box. SNMPv3 requires key management and an established PKI, and there's no equivalent of Let's Encrypt for isolated use cases in small orgs.
- ay 1y agoSNMPv3 absolutely doesn’t require PKI nor key management, it works fine with shared keys. You can take a look at an implementation of that, which I had built for entertainment: https://github.com/ayourtch/oside/blob/main/examples/snmpwalk.rs https://github.com/ayourtch/oside/blob/main/examples/snmpwal...
- mkipper 1y agoI never looked into the guts of how this was implemented, but I worked on a product which had an SNMPv3 agent that was only restricted by a username and password. I could flash a PC with a fresh Ubuntu image, apt install Net-SNMP and start sending SNMPv3 requests without every futzing with any keys. If I remember right, handling SNMPv3 traps required some messy key stuff so the agent still sent SNMPv2 traps, but there was no requirement for keys for GET/SET.
- deleted 1y ago[deleted]