Safari "auto-update" installation fails

Options
samcolak
samcolak
Community Member
in Mac

Guys, although this may seem a little off-topic, the auto-update facility failed on safari - stated "Could not update extension". Whilst i really like the product, it raises the question, was there an attempt to spoof or modify the app without my knowledge by other parties than yourselves. If it was you, then why not ask my permission since, inevitably, i start asking myself have i been compromised etc.
When failures occur (like they just did), i start to review my security practices, reliance on 3rd party products like 1password and look to "new" solutions.
Hope you can understand and look forward to your input.
Best,
Samuel

Comments

  • sjk
    sjk
    1Password Alumni
    edited July 2014
    Options

    Hi Samuel ( @samcolak ),

    Could you please restart Safari and see if you're able to successfully update the 1Password extension after that?

    The specific cause of this problem has been elusive so far. @MikeT has posted some questions to help us isolate it: here.

    Any answers we can get for those are appreciated. Thanks!

  • samcolak
    samcolak
    Community Member
    edited June 2014
    Options

    Restarting Safari did not resolve the issue - i eventually removed the extension and reinstalled from the source - given the security considerations i deal with, this was the easiest option - ill keep an eye on it.

    Per the event log, i tracked the following messages in the console (system.log)

    30/06/14 07:46:30,590 2BUA8C4S2C.com.agilebits.onepassword-osx-helper[320]: 441006 [EXT:0x7fe8a2407790:] M start | [ES4] Starting JSE server on port 6263
    30/06/14 07:46:48,833 2BUA8C4S2C.com.agilebits.onepassword-osx-helper[320]: 441006 [EXT:0x7fe8a271be80:] M webSocketForURI: | [ES4] Extension connected Safari-Extension 'safari-extension://com.agilebits.onepassword4-safari-2bua8c4s2c / (null)'

    this repeats a couple of times...

    30/06/14 08:00:38,141 2BUA8C4S2C.com.agilebits.onepassword-osx-helper[320]: 441006 [EXT:0x7fe8a3af5de0:] M webSocketForURI: | [ES4] Extension connected Safari-Extension 'safari-extension://com.agilebits.onepassword4-safari-2bua8c4s2c / (null)'

    If you have a more specific request for info, give me a shout on Skype with the above username (samcolak).

    Best,
    Samuel

  • samcolak
    samcolak
    Community Member
    Options

    System info = MacBookPro Retina (15'') Late 2013, 2.6GHz i7, 16GB running OSX 10.9.3 (13D65) (Stock install from @pple)

  • daharrin
    daharrin
    Community Member
    Options

    I was encountering the same problem. Periodically, at an auto-update attempt of 1P extension 4.2.3 for Safari 6.1.4, I would receive a notice that Safari could not install the extension. Based on sjk's advice above, I restarted Safari, and was able to install manually through the Preferences… panel.

    I did not see specific notices in the console for the failed installation attempts, but I did see the "Extension connected…" message that samcolak posted, after installation was successful.

    I have a mid-2012 MBP 15" Retina (10,1), 2.6 Ghz i7, 16GB running OS X 10.8.5 (12F45).

  • sjk
    sjk
    1Password Alumni
    Options

    Hi Samuel ( @samcolak ),

    I'm sorry that the 1Password extension update still wouldn't install after restarting Safari, but am glad its removal/reinstallation worked for you without having to change permissions for the ~/Library/Safari/Extensions folder (or recreate it).

    Those log messages you posted look normal. What the next few that come after can be helpful, e.g.:

    Fri Jun 27 01:11:52 2014| 441006 [EXT:0x7f9423e00ed0:<OP4ExtensionServer: 0x7f9423c502d0>] M start | [ES4] Starting JSE server on port 6263
Fri Jun 27 01:11:54 2014| 441006 [EXT:0x7f9423c502f0:<OP4ExtensionHTTPConnection: 0x7f9423f7a8c0>] M webSocketForURI: | [ES4] Extension connected Safari-Extension 'safari-extension://com.agilebits.onepassword4-safari-2bua8c4s2c / (null)'
Fri Jun 27 01:11:54 2014| 441006 [EXT:0x7f9423c67930:<OP4ExtensionClient: 0x7f9423e3fea0>] S didOpen | [ES4 0x7f9423e3fea0] Connected 'safari-extension://com.agilebits.onepassword4-safari-2bua8c4s2c:60167'
Fri Jun 27 01:11:54 2014| 441006 [EXT:0x7f9423c7b920:<OP4ExtensionClient: 0x7f9423e3fea0>] S handleHello: | Welcoming version 4.2.2 of Safari-Extension.
Fri Jun 27 01:11:54 2014| 441006 [EXT:0x7f9423c7b920:<OP4ExtensionClient: 0x7f9423e3fea0>] S sendAction:payload: | [ES4 0x7f9423e3fea0] safari-extension://com.agilebits.onepassword4-safari-2bua8c4s2c sendAction: 'welcome'
Fri Jun 27 01:11:54 2014| 441006 [EXT:0x7f9423c502f0:<OP4ExtensionClient: 0x7f9423e3fea0>] S findExtensionProcessForPort: | [ES4 0x7f9423e3fea0] Connected safari-extension://com.agilebits.onepassword4-safari-2bua8c4s2c:60167: <NSRunningApplication: 0x7f9423db7100 (com.apple.Safari - 643)>
Fri Jun 27 01:11:54 2014| 441006 [EXT:0x7f9423c502f0:<OP4ExtensionClient: 0x7f9423e3fea0>] S verifyClient:satisfiesRequirement: | Extension client 'safari-extension://com.agilebits.onepassword4-safari-2bua8c4s2c' (<NSRunningApplication: 0x7f9423db7100 (com.apple.Safari - 643)>) passed validation

    You want to see the last of those to end with … passed validation. And ones like this during extension usage:

    Fri Jun 27 01:13:08 2014| 441006 [EXT:0x7f9423e00ed0:<OP4ExtensionClient: 0x7f9423e3fea0>] S sendAction:payload: | [ES4 0x7f9423e3fea0] safari-extension://com.agilebits.onepassword4-safari-2bua8c4s2c sendAction: 'getActiveURL'
Fri Jun 27 01:13:26 2014| 441006 [EXT:0x7f9423e00ed0:<OP4ExtensionClient: 0x7f9423e3fea0>] S sendAction:payload: | [ES4 0x7f9423e3fea0] safari-extension://com.agilebits.onepassword4-safari-2bua8c4s2c sendAction: 'fillItem'
Fri Jun 27 01:13:32 2014| 441006 [EXT:0x7f9423e00ed0:<OP4ExtensionClient: 0x7f9423e3fea0>] S sendAction:payload: | [ES4 0x7f9423e3fea0] safari-extension://com.agilebits.onepassword4-safari-2bua8c4s2c sendAction: 'getActiveURL'

    However, nothing is logged during extension installation/updating/removal that indicates success or failure. I don't recall seeing that type of logging for any extensions.

    I'm still getting more details about what, if any, security considerations might be related to this.

  • sjk
    sjk
    1Password Alumni
    Options

    I'm sorry the 1Password extension update has also been troublesome for you, @daharrin. Restarting Safari seems an effective workaround in cases where update failures are caused by injected script handling (like @MikeT mentioned in the related question post). We're still hunting for any specific cause(s).

  • littlebobbytables
    littlebobbytables
    1Password Alumni
    edited July 2014
    Options

    @samcolak‌

    If it was you, then why not ask my permission...

    I'm curious as to what you exactly mean by this particular part of your original post. The 1Password extension itself didn't initiate the update, it was Safari. You can turn this feature off if you wish, it's in Preferences... : Extensions and then select Updates in the left panel. You'll then have the option of turning automatic updates off.

This discussion has been closed.