I keep getting this error: Mac verify error: invalid password? For these two commands: openssl pkcs12 -nocerts -out PushKey.pem -in moo.p12 openssl pkcs12 -nocerts -out PushKey.pem -in moo.p12 -nodes moo.p12 is issued by apple for push notifications. Restart your iOS device or computer. As many technical issues can be resolved by restarting the. Most of these postings I do either on the road using my iPhone, iPad, Netbook or from a PC. This is a journal of technical rants or some not so technical rants, though lately it has been more of a photo blog/show, and a bit more personal, it may put some people to sleep:-).

• Mac Verify Failed For Connection Idm
• Mac Verify Failed For Connection Identity
• Mac Verify Failed For Connection Id Card

*Feb 19 21:58:56.751: %CRYPTO-4-RECVD_PKT_MAC_ERR: decrypt: mac verify failed for connection id=2001 local=14.0.0.1 remote=16.15.0.254 spi=0CDE4B1E seqno=00000213

OK so playing around in my LAB, I had created a simple GRE Point to Point Tunnel between two site routers with one router in between. See picture, I chose AES 256

The tunnel is up everything seemed great until I saw the following syslog message “%CRYPTO-4-RECVD_PKT_MAC_ERR: decrypt: mac verify failed for connection id=2001 local=14.0.0.1 remote=16.15.0.254 spi=0CDE4B1E seqno=00000220”.

After doing some research there were recommendations for trying different transform sets, verifying the passphrase and disabling fast switching. (no ip route-cache) Unfortunately this has not solved the issue ……. hmmmmmmmm

I will get this ……….. traffic still flows through the tunnel and research shows that this is an issue with mac decryption and some sort of bug in the Cisco code. Not to sure about that though. Some cases have shown that the ‘no ip route-cache’ and ‘no ip route-cache cef’ actually have worked in eliminating this error. Could it be on case by case basis?

Mac Verify Failed For Connection Idm

hmmm

I will have to put WireShark to work on this and see what is going on………

“To be Continued…………”

Mac Verify Failed For Connection Identity

Dooooh...well after reading Apple's article (Two-step verification for Apple ID - Apple Support) on how two-factor authentication works...I discovered that for those applications that do not support entering verification codes you can generate an app-specific password by signing in to your Apple ID account page and in the Security section, click Edit > Generate Password. So assuming the Mac OS X Yosemite iMessage app does not support verification codes which seems odd, I generated an app-specific password and entered it into the Mac OS X Yosemite iMessage Apple ID login dialog box and It worked.

Mac Verify Failed For Connection Id Card

Jan 10, 2017 1:29 PM