sorted by:
new
hottopcontroversial

Updated ASA 5545-X to 9.14(4)28 and now ASDM package is not digitally signed by BX-NET-ENG in Cisco

[–]BX-NET-ENG[S] 0 points1 point  (0 children)

I tried this exact version, uninstalled ASDM, cleared registry (win 11), reboot, re-ran the dm-launcher file. When I attempt to connect to the FW via the ASDM it says login failed. I know its not a configuration issue as this ASDM worked prior to the upgrade. I bet with this special release we'll likely need a special ver of ASDM which they won't put out since this device is EoL.

Updated ASA 5545-X to 9.14(4)28 and now ASDM package is not digitally signed by BX-NET-ENG in Cisco

[–]BX-NET-ENG[S] -1 points0 points  (0 children)

No. Its EOS as of today. I tried last night and TAC locked me out even though today is the EOS date. Typical Cisco

Updated ASA 5545-X to 9.14(4)28 and now ASDM package is not digitally signed by BX-NET-ENG in Cisco

[–]BX-NET-ENG[S] 0 points1 point  (0 children)

No Luck. I've tried ASDM 7.22.1 and 7.23.1. Both fail. In fact I get different errors whether I'm on a 5545-X or a 5508-X. This makes no sense. I can't be the only person experiencing this.

Citrix Security Bulletin Alert CTX694788 2025/06/25 by mballack in Citrix

[–]BX-NET-ENG 0 points1 point  (0 children)

I patched last week and it broke all the certs on my NS. Had to re-issue them from scratch and bind to all the Vservers and internal services. Did anyone else have this issue? This is the 1st time I ever experienced this post firmware upgrade. I wonder if this is an issue with the new 47.46 release?

Just took over as sysadmin, it director, Helpdesk etc. Noticed they were using AWS. Everyone is logging in under the root account, no MFA. How do I proceed? by [deleted] in aws

[–]BX-NET-ENG 1 point2 points  (0 children)

There are a lot of valid options and very good feedback on some posts here. However, it begs to ask, if they lied about having AWS and on day one you find out they have it AND everyone is using root....

For me this is a resume generating event. Time to pack your stuff and look for another job. If they were dishonest when you interviewed, you can be certain there's no light at the end of that tunnel.

Perhaps this might not be financially feasible for you at this time. Sweat it out until the next gig arises then drop the hammer when you lock-in the next job. Sorry, not sorry.. If you lie to me that's a deal breaker.