1Password 6.5 will break connection

[rafcontreras]

I've been beta testing 1P 6.5 and on sudolikeaboss Coprocess from iTerm it requests and update on the browser extension.

I have raised this issue on the agilebits forums and they've asked me to create a bug report so they can provide you with additional documentation to keep this working.

Cheers

[rickfillion]

1Password 6.5 will require what we call Simple Mutual Authentication, which is a means of allowing a pairing between 1Password mini and the apps that talk to it. This will break the current version of sudolikeaboss.

Give it a shot with the current betas of 1Password 6.5 and if you have any questions, let us know and we can try to point you in the right direction.

[charliwest]

+1 for getting this fixed, damn my clicking the beta updates :)

[rudyrichter]

adding myself as a watcher in the event i'm able to assist with any question answering

[brettrann]

adding myself as a watcher too. happy to test. Thanks for offering this awesome tool proactive support Rick!

[ravenac95]

@rickfillion Thanks so much for reaching out! Jeffrey from Agilebits also reached out to me. I sent him a response about getting some docs on the protocol. Let me know if there's anything else I may need.

[bwithem]

Thanks @ravenac95 I hope you know how much time you save us on a daily basis! <3

[ssgelm]

@ravenac95 Let me know if there's anything I can do to help - I'd love to be able to use this again too! 😀

[nzkller]

Hello Guys,

The new update has been pushed and now im on 1Password Version 6.5 (650034) and my sudolikeaboss is broken.

Do you have any news about this? I think I've become sudolikeaboss dependant for my daily work.

Let me know if I can help.

Best regards,

Nzk

[ravenac95]

@ssgelm @nzkller I've been moving apartments recently which has taken up most my time. I just finished with all that and should have time to address these concerns. I'm starting development tonight. I will send out some beta builds once I get them! Would you guys be willing to test?

[knilob]

I would totally be willing to help test.

[JamesValero]

Me too! Use it everyday

[ssgelm]

I'd be very happy to test!

[ssloss]

I don't know how many testers you need, but I'd be very happy to test too.

[warrengottlieb]

Also happy to test!

[nzkller]

@ravenac95 Count me in happy to test and help 👍

[rcreasey]

+1 for testing.

[charliwest]

Willing to test here as well

[cchalasani]

I can help too

[kguay]

Happy to test!

[mhe-de]

+1 add me to the list

[Gee19]

I am also willing to test or help out!

[rudyrichter]

@ravenac95, if you run into any scenarios where you need any assistance debugging the interaction with 1Password mini let me know and i can take a look. I spent many weeks working on that code.

[targeter]

Let me know if I can help with testing

[kdorff]

I'm happy to test. I will be sad until sudolikeaboss is restored to it's former glory.

[ravenac95]

Hey guys. Just an update. I've been working on this a bit this week. Some of the documentation I was given wasn't quite correct but I was able to figure it out. I think I am unblocked now so it's simply following the updates for new 1password protocol. I will post a build up here once I have it! Hoping I can have an experimental build up this weekend.

[rudyrichter]

@ravenac95 I'm curious what wasn't right in the documentation, did you sent feedback to Jeff to let him know so we can update it accordingly?

[ravenac95]

@rudyrichter I will totally send feedback to Jeff :)! I haven't had a moment to write the email.

[rudyrichter]

@ravenac95 thanks, I'll look forward to reading it. maybe i know the why of why it differs!

[ssgelm]

Very exciting! I've got tons of free time in the coming days so let me know if you need help with the code at all - happy to help.

[sibartlett]

Is there any chance of myself also obtaining the documentation too? So I can update 1password integration for hyperterm? @rudyrichter @rickfillion?

[roodkcab]

I've finished reversing chrome 1p plugin, and upload to my forked repo, if anybody like to have a test just clone from my repo, and compile the code using
CC=clang go build -ldflags -s

I've tested this code both under 6.6.4 and 6.7.1

!!!!!!!!!!!!! CAUTION !!!!!!!!!!!!!
u must put the password in PASSWORD category, it mustn't has a username field
if u put your password in LOGIN category, i.e. it has a username together with url
1password will send a openUrl action to sudolikeaboss, instead of a collectDocuments
good luck

[rudyrichter]

@roodkcab,

just a heads up, 6.8 implements Native Messaging and rejects chrome clients over WebSockets.

[roodkcab]

@rudyrichter interesting, I'll have a look

[roodkcab]

@rudyrichter are u sure about this? I upgraded to 6.8 beta4 and everything is ok, chrome plugin version is still 4.6.6 using websocket to communicate with 1password, I've tested my code, no problem there.

[rudyrichter]

@roodkcab you have verify code signature turned off in advanced settings.

[roodkcab]

@rudyrichter thanks, I'll have a look

[ssgelm]

@rudyrichter Any chance I could get a copy of the integration doc? I'm trying to update 0.3.0-beta1 to work with 1pass 6.8 and I'm not having luck with any non-chrome origin URL. Alternatively any suggestions you have would be awesome!

[ssgelm]

As an aside re-running sudolikeaboss register under 6.8 does make it work again (with verify code signature turned off) but I'd love to fix this in a more correct way.

[TyBrown]

Confirmed the following combination works:

• 1Password Version 6.8.BETA-12 (680012)
• sudolikeaboss Version 0.3.0-beta1
• Verify browser code signature: disabled

[ideologysec]

Where did the 0.3.0-beta1 version come from? is that the 6.5compat branch?

[TyBrown]

@Aktariel Please see @ravenac95 's comment here: #29 (comment)

That's where the sudolikeaboss version 0.3.0-beta1 version that I have installed came from.

[rudyrichter]

@ssgelm, i'm not sure what document the security folks would have sent over to @ravenac95, but I suspect it only pertained to the implementation of the SMA (Secure Mutual Authentication) handshaking protocol.

There are a couple things stacking up that will be coming in the next couple months: WebSockets is going away as a means of communicating with 1Password (along with it the verify code signature checkbox). Native Messaging (Chrome and Firefox are pushing this one) will be the way to talk to 1Password. The underlying protocol for communication with 1P will stay the same (SMA + Action Protocol), but the transport for that communication will be Native Messaging https://developer.chrome.com/extensions/nativeMessaging. The downside I see for sudolikeaboss is that that whole pathway requires that the binary be code signed with a signature that we also recognize as valid.

We'd certainly be interested in talking with @ravenac95 or anyone else that's interested in working on these changes.

[brycekahle]

@rudyrichter Since @ravenac95 is clearly very busy (#40), I've started updating a fork (https://github.com/brycekahle/sudolikeaboss) that contains several fixes/improvements from the community. I would be interested in talking to you about Native Messaging and any other important updates that need to happen. My email is on my GitHub profile.

[charliwest]

@brycekahle would like to give this a try, is the process the same to install via go for your fork? Cheers

[GitHubGreg]

Thanks @brycekahle for taking this up. Much appreciated.

[brycekahle]

@charliwest I haven't had a chance to test my changes yet. Once I do, I will make a homebrew tap + release download. I'm hoping to get to that later today.

[jchannon]

I'm on 6.8.1 will fixes there address that version?

…

On 30 August 2017 at 16:39, Bryce Kahle ***@***.***> wrote: @charliwest <https://github.com/charliwest> I haven't had a chance to test my changes yet. Once I do, I will make a homebrew tap + release download. I'm hoping to get to that later today. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#29 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGapmpzVGYNbd05JFrsRjqChHGq3ojJks5sdYIvgaJpZM4KlUwl> .

[brycekahle]

I'm on 6.8.1 will fixes there address that version?

@jchannon If that version requires Native Messaging, then no. I'm hopefully going to be contacted by AgileBits with details on what is necessary to add NM support.

I saw this thread in the 1Password forums that seemed to indicate NM might be required for 6.8.1. I have 6.8 installed, and websockets still work (but have some odd quirks like 1Password needing to be unlocked first).

[brycekahle]

@charliwest I just released 0.3.0. The easiest way to install is via homebrew brew install brycekahle/sudolikeaboss/sudolikeaboss.

[charliwest]

@brycekahle just got it installed, thanks for the quick work. I had 6.8.1 and it failed with the same error about restarting my browser. Just downgraded to 6.8 and working fine again. So you are probably correct about NM.

[amaltson]

It looks like 6.8.1 is broken and I installed it from the App Store 😞, is there any hope for me?

[brycekahle]

@amaltson You can follow these instructions and then download 6.8 here.

[ChristoRibeiro]

any update to make it work with 1Password 6.8.1?

[myrandor]

There's no more need for this now, especially with the latest restriction cause by OSX... With latest version iTerm2, there's an encrypted password manager accessible using CMD-OPT-F.

It has to be copied from 1Password but it's not a big hassle...

[2bithacker]

I disagree, I think there's still a lot of use cases that sudolikeaboss + 1Password address that the iTerm2 password manage does not handle, such as OTP.

[brycekahle]

@ChristoRibeiro Unfortunately, it won't be possible because AgileBits refuses to allow tools like sudolikeaboss. See this issue and the forum post linked from there.

[ChristoRibeiro]

@brycekahle thanks for your feedback. So the only fix is to downgrade to 6.8 until AgileBits decide to make sudolikeaboss official?

[brycekahle]

until AgileBits decide to make sudolikeaboss official

They have stated that this will not happen. 😢