stuartcryan

Ladies and gents,

I can happily say today marks the release of a LOT of time and effort... 1.4.2 of the workflow is OUT

Version 1.4.2 MAJOR update - Please Read

-----------------------------------------------------------

Ladies and gents, I am happy to present v 1.4.2 of the workflow. Before I continue, this has represented a SIGNIFICANT amount of work for me so if you like it and use it, please say thank you by donating towards my Diet Coke and cake fund.   Any amount will do, whatever you feel the value is for you/your business/your time.  

 

Please note you *MUST* update your LastPass CLI version to 0.7.1 or higher as this update relies on new functionality that I worked with the LastPass team on integrating into the official CLI.

 

I would also like to say thank you to Michael B. who was extremely patient and worked with me back and forth to help quash an evil bug that stopped some vault items from displaying at all.

 

If you haven't used LastPass before... you are crazy and you should it is the single greatest password manager package out there   so check it out at http://stu.link/LaStPaSs (Disclaimer, if you sign up through that link I get a free month otherwise you can go direct to http://www.lastpass.com).

-----------------------------------------------------------

 

Version 1.4.2

1. NOTE: This version *requires* the LastPass CLI v 0.7.1 or higher due to this new feature --> Login process completely changed over to use AppleScript (cleaner and nicer). This was thanks to work between myself and Bob from LastPass who maintains the official LastPass CLI to add a feature allowing an external login prompt to be used.
2. Login password prompt now uses an AppleScript password prompt.
3. Fix to allow you to search for words in any order.
4. Vault item's which now require re-authentication will pop up the AppleScript login prompt.
5. Has now been tested with a Vault with over 30,000 items for performance tweaks. (I have since been told by LastPass support their soft limit is significantly lower than this at ~2500 items explains why I was having some issues in testing).
6. More resilient escaping of text in the XML to ensure that special characters should not cause any issues.
7. Fixed missing quotes in some areas that could cause issues with spaces.
8. Squashed a little regex bug and wiped up the goo.
9. Fixed issues with spaces in certain paths we referenced
10. Fixed how the initial login process is run after a reboot. This required the changes made to how we manage the login process and it has subsequently been cleaned up significantly.
11. Other minor general tweaks.

Any issues please log an issue over at GitHub.

OK so human error is a thing... it happens, and totally my bad. After releasing this a couple of guys have pointed out to me that the binary itself did not actually update :( so all of you that tried to download this yesterday would have got the same old boring workflow.

HOWEVER

That is now fixed and we have v1.4.3 which also adds another feature/fix which I had a stroke of genius on yesterday (after the original release). 1.4.3 also includes a feature/fix to drastically speed up the performance of the LastPass CLI's copy to clipboard function. Therefore passwords should now copy with lightening speed

Looking forward to everyone's thoughts.

Ladies and gents,

I can happily say today marks the release of a LOT of time and effort... 1.4.2 of the workflow is OUT

Version 1.4.2 MAJOR update - Please Read

-----------------------------------------------------------

Ladies and gents, I am happy to present v 1.4.2 of the workflow. Before I continue, this has represented a SIGNIFICANT amount of work for me so if you like it and use it, please say thank you by donating towards my Diet Coke and cake fund.   Any amount will do, whatever you feel the value is for you/your business/your time.  

Please note you *MUST* update your LastPass CLI version to 0.7.1 or higher as this update relies on new functionality that I worked with the LastPass team on integrating into the official CLI.

I would also like to say thank you to Michael B. who was extremely patient and worked with me back and forth to help quash an evil bug that stopped some vault items from displaying at all.

If you haven't used LastPass before... you are crazy and you should it is the single greatest password manager package out there   so check it out at http://stu.link/LaStPaSs (Disclaimer, if you sign up through that link I get a free month otherwise you can go direct to http://www.lastpass.com).

-----------------------------------------------------------

Version 1.4.2

1. NOTE: This version *requires* the LastPass CLI v 0.7.1 or higher due to this new feature --> Login process completely changed over to use AppleScript (cleaner and nicer). This was thanks to work between myself and Bob from LastPass who maintains the official LastPass CLI to add a feature allowing an external login prompt to be used.
2. Login password prompt now uses an AppleScript password prompt.
3. Fix to allow you to search for words in any order.
4. Vault item's which now require re-authentication will pop up the AppleScript login prompt.
5. Has now been tested with a Vault with over 30,000 items for performance tweaks. (I have since been told by LastPass support their soft limit is significantly lower than this at ~2500 items explains why I was having some issues in testing).
6. More resilient escaping of text in the XML to ensure that special characters should not cause any issues.
7. Fixed missing quotes in some areas that could cause issues with spaces.
8. Squashed a little regex bug and wiped up the goo.
9. Fixed issues with spaces in certain paths we referenced
10. Fixed how the initial login process is run after a reboot. This required the changes made to how we manage the login process and it has subsequently been cleaned up significantly.
11. Other minor general tweaks.

Any issues please log an issue over at GitHub.

Hopefully the last beta update before release:

I give to you 1.4.2 which (with the new login issue) resolves a long standing bug which made the login process after a reboot somewhat less than user intuitive.

https://dl.dropboxusercontent.com/u/9093155/LastPass%20CLI_1.4.2_beta.alfredworkflow

If I don't get any major show stopper feedback in the next 24 hours this will be marked as the next stable release.

Great!

So useful!

So glad you like it it is easily the quickest workflow I have written yet but probably the one that gets the most use as well

Stuart

Hi All,

Another beta update, this update aims to further improve stability and deal with special characters in item names. Also working towards fixing a bug where some items would not display (but hard to narrow down as it requires the sharing of vault data for me to diagnose).

Feedback welcome:

https://dl.dropboxusercontent.com/u/9093155/LastPass%20CLI_1.4_beta.alfredworkflow

Hi Xilopaint and JHinden, I will have a look at that issue for the next update. Will keep you posted.

I don't understand.

 

If you're not running your script from within Alfred, the Alfred environmental variables Vítor mentions above that are "exactly what [you] needed" won't be available…

They are if I pass them through to bash. So basically I use a system command (perl) to run a command with Bash, but using the Alfred variables I am able to pass the data through that I need to that system command.

For anyone else that is interested... version 1.3 beta https://dl.dropboxusercontent.com/u/9093155/LastPass%20CLI_1.3_beta.alfredworkflow

If you do download... please subscribe to this post so you know when to download the final.
 

Changes in this version:

1. Change login process to use AppleScript, far cleaner and should support passwords that require RE authentication

2. Improvements to reliability, especially surrounding searching for items with multiple words

3. Fix to allow you to search for words in any order

4. Other minor general tweaks

5. Has now been tested with a Vault with over 30,000 items for performance tweaks.

OOH forgot to mention you MUST use lastpass CLI 0.7.1 or higher, the script changes are not backwards compatible as we rely on a new feature that I worked with the LastPass team on.

I solved my problem when I realized Alfred couldn't open any terminal windows whatsoever.

 

I had "Custom" set as the chosen terminal, this was copied over from Alfred's preferences on the other computer.  

 

However in the new computer I only have the OSX Terminal installed.

 

So after changing the preference to use "Terminal", the workflow runs great =D. 

 

 

 

Also, the lack of notifications in 1. in the above post was explained when it happened today; I have a Do Not Disturb mode scheduled for certain times of the day, and all my Alfred notifications get caught by this.

Howdy my good man,

sorry for the delay, it seems I missed out on these email notifications when my mailbox overflowed and stopped accepting emails #oops

Glad you got it solved.

I can't seem to get this to work for me. While it will load many passwords, it doesn't load them all. I don't know if the directory hierarchy is the cause, permissions, or just terrible organization (it's well known, our team is working on it).

 

Currently we have the hierarchy set as such:

 

Client Named Folder

 

_Administrative account

 

SOME-SERVER-01

 

_Services, Portals, Website Logins

 

www.somewebsitelogin.com

 

Some.random.password.that.shouldnt.be.here

 

Note, our structure is totally mucked up and that's only representative of what we would like to be ideal and not the whole structure overall, which again, we're working on. Though I don't how much that would affect the visibility of passwords. The only other thing I can think of is permissions, but whenever I'm using the CLI interface, I can see all the secure notes, sites, etc. without issue.

 

I'd love to use this more, but it only seems like I can pull about 50% of the passwords out before nothing else syncs.

 

Thank you for any suggestions.

 

Michael

Hi Michael,

I am currently liaising with LastPass support to see what options I have for basically generating a large dummy vault so that I can do some performance testing.

I will keep you posted.

Very interested. Work in an MSP with many clients and passwords that we share within our company internally, so we have very large vaults that we work with continuously, throughout the day. I've been trying to get a decent workflow for LP to work correctly, but I've been having trouble. I'd love to help out in any way I can.

Awesome and thank you.

I will message you to get your contact details you are exactly the kind of person I would like to test (especially want to try to get it working with huge vaults).

Hi All,

I have been working on a major update to the LastPass for Alfred workflow, and am looking for a handful of people that are regular users of the workflow (i.e. multiple times daily) to beta test the new flow for me.

This is the workflow for those of you interested:

http://www.alfredforum.com/topic/5630-lastpass-workflow-for-alfred-update-v12-released-august-21-2015/

Current change list as follows:

1. Login process completely changed over to use AppleScript

2. Login password prompt now uses an AppleScript password prompt

Still working on (prior to beta release):

1. Enabling access to passwords that require re-authentication

2. General speed optimisations

3. Toying round with the idea of auto presenting the search prompt after login... have not yet decided on this (open to ideas).

If you are interested please just post a comment here and I will get into contact with you when ready.

Many thanks

Stuart

 

When Alfred runs your workflow, it always does to from the workflow's own directory.

 

That is to say, from any running workflow, the user's workflow directory is ../.

 

This is true, except for when you run something in Bash I have found, hence I need to be more explicit.

What you’re looking for are Workflow Script Environment Variables. Also check how to access them with AppleScript (and other languages).

WOOHOO exactly what I needed thank you.

Howdy all, have a bit of a conundrum.

In one of the workflows I am developing, I have a script which needs to set an environment variable for OSX such as:

set osascript to "/Users/stuartryan/Dropbox/AlfredSync/Alfred.alfredpreferences/workflows/user.workflow.EE2025D2-9836-4EF1-995D-B91C6A8D3377/passwordInput.osascript"

However, in order to do this I need to be able to tell what the workflow directory is on each system. Is there any automated mechanism/variable to do this? (Using osascript).

Alternatively the only other workaround I can think of is to check if a data directory exists for the workflow, and if not create it and "cat" a file there. Ideally I would copy the file over but I need to know where to copy it from first.

Thank you all... this one is doing my head in so trying to find what the best supported solution is.

Howdy all,

Vitor has done some awesome work and closed out a couple of tasks, I apologise for the delay in merging them but I have been unwell.

All back to normal now and new version of the scripts have been released, so I suggest you get your hands on the latest version from:

• iTerm 2 Branch (tested up to 2.1.1) - view the v2.1 script on Github - updated December 14, 2015
• iTerm 2.9 Branch (tested up to 2.9.20150626) - view the v2.9 script on Github - Updated December 14, 2015

The actual problem is a bug with iterm (described below in more detail), so I don't really think you can fix it from outside. But FWIW, here's how I setup the "quake window" feature.

...

That's the entire story I use the ~ (tilda) button to show/hide it.

 

The thing is, it's a little buggy (I opened a bug in iterm), when I toggle it off with the hotkey, it's impossible to use cmd+tab to get back to the window. A similar problem happens here, where if it's hidden with the hotkey, it probably cannot be detected so it opens a new iterm window.

 

Note that when it happened to me, I only had the "hotkey window" open, no other iterm windows.

Boo that is a shame, something I won't be able to fix for the time being. Hopefully they can resolve that soon in the iTerm binary.

If there are any changes as a result after the fix I can look at making those in the AppleScript.

Installed and works, thanks for the effort!

I've noticed an issue with searches containing more than one word?

 

edit: forgive me for linking the images like this, they look huge when linked thru the forum editor...

successful-search (password was copied) - http://i.imgur.com/h3v9ruC.png

not-found (expected) - http://i.imgur.com/2YvdOUg.png

lastpass-cli-not-installed (weird) http://i.imgur.com/LIFZKI3.png

As I've done the first two searches, the result of the third search is impossible.

Apologies if this has been reported before or is noted somewhere...

 

Also, a trivial typo I must report for the sake of perfection (by default)... - http://i.imgur.com/73L4nsj.png 

 

Howdy my good man, so sorry I missed this.

I have logged two bugs for you:

1. Weird search issue --> https://github.com/stuartcryan/lastpass-alfred-workflow/issues/12

2. Shameful SHAMEFUL typo LOL --> https://github.com/stuartcryan/lastpass-alfred-workflow/issues/13

Thank you for reporting them, I have a week off as of this evening so hopefully will be able to get to them.

H

i am not a technical person and don't know anything about capture:tiny, homebrew etc. But I have installed everything and i am on the stage of logging in pinentry

 /usr/local/bin/lpass login [--trust] [--plaintext-key [--force, -f]] USERNAME

 

i am hesitant to ask, and you can laugh or beat me to death but I have gathered strength to ask this :

 

is there a risk of my master password getting compromised this way? There is a lot going on in CLI and i don't know what all code my MasterPassword would go through and which host/domain these scripts might connect from background. I appreciate this fantastic workflow and don't doubt you at all. its just that i want to know the background work these scripts would do. 

Apologies if i offended you or anybody.

 

Regards,

Jay

Hi Jay,

The workflow itself does not do any storage of passwords in any way shape or form.

Really it comes down to the CLI that has been written by the lastpass team and how much you trust them/it. Essentially all this workflow does is leverage the content within the CLI that Lastpass provides.

Therefore I would say you would need to make an assessment as to how much you trust that LastPass has put together a safe CLI. Having said that if you trust them enough to use their other browser plugins, I foresee no issue why their CLI should be any different.

And no worries at all, no offence taken, it is good to be diligent in these matters.

Excellent, and thank you. One comment so far (15 minutes of playing with it) is your maps are google.maps.au, so I went and relocalized for my country. 

Suggestion - can I add in another common location - for me, it's gym. Some mornings i head to work, some mornings I stop first at gym. I guess I can just plug in gym postal code, but a feature to add other favorites (or search address book) would be cool. 

 

Thanks again.

OOOH noted, I have logged two issues on github.

1. Don't assume .com.au need to look at some sort of localisation --> https://github.com/stuartcryan/advanced-google-maps-alfred-workflow/issues/1

2. Add additional locations dynamically --> https://github.com/stuartcryan/advanced-google-maps-alfred-workflow/issues/2

I will try to get to these in my next round of updates .

@stuartcryan -

 

I'm on the bleeding edge of iTerm I think (Build 2.9.20150812-nightly)

 

As for the new feature - would it be like a boolean you configure at the top of the script? Or actually a different script? I want to understand what "all or nothing" means, I don't mind if it's not configurable in a UI, but would love a way to be able to quickly change it in the custom script code.

 

Also, this is funny, but I'm actually experiencing different results whether I'm cmd+tabbing away from that hotkey window or if I'm hiding it with the hotkey itself (I get a new tab in a new window vs. new tab in the hotkey profile window). This actually is related to the iTerm bug I posted, haha

 

Thanks.

Howdy my good man,

Any chance you could do a screen recording of the issue (and upload to youtube as private? or alternatively I can set up an SFTP location for you).

Just want to get a better idea of how it all works as I haven't used the quake feature before.

Hi All,

As per a request submitted on Github, I have updated to add support for FirefoxDeveloperEdition and Webkit Nightly Builds to the workflow.

New version is 1.2 and is available here --> https://github.com/stuartcryan/defaultbrowser-alfred-workflow/blob/master/set-default-browser-alfred-workflow.alfredworkflow

#enjoy

@stuartcryan -

All righty, I have logged two issues on github for you:

1. https://github.com/stuartcryan/custom-iterm-applescripts-for-alfred/issues/7- Feature request

2. https://github.com/stuartcryan/custom-iterm-applescripts-for-alfred/issues/6- Investigate bug relating to iTerm behaviour

@stuartcryan -

 

I'm on the bleeding edge of iTerm I think (Build 2.9.20150812-nightly)

 

As for the new feature - would it be like a boolean you configure at the top of the script? Or actually a different script? I want to understand what "all or nothing" means, I don't mind if it's not configurable in a UI, but would love a way to be able to quickly change it in the custom script code.

 

Also, this is funny, but I'm actually experiencing different results whether I'm cmd+tabbing away from that hotkey window or if I'm hiding it with the hotkey itself (I get a new tab in a new window vs. new tab in the hotkey profile window). This actually is related to the iTerm bug I posted, haha

 

Thanks.

Good to know on the version I will have a squiz and see what I can come up with.

I was actually thinking along the lines of a boolean in the script itself (rather than a separate script). So I think that would suit exactly what you are looking for.

And that is strangeeeee I might have a play and see if I need to ask for some extra applescript additions in iTerm to help get around it even in the long term.

I'm using iTerm's "quake window" feature (I have a specific half-screen sized window,that drops when I hit the `~` (tilda) button). This opens a new tab in that profile, but doesn't activate the actual window.

 

It may be related to this bug I previously opened for iTerm, which is sort-of related to activating the "hotkey profile".

 

I would also be interesting to be able to choose whether the script ( opens a new tab / reuses one tab *it opened* / opens a window / reuses one window it opened ). Don't know if that's feasible, but I would definitely choose a reused tab/window instead of a new one every time.

 

Thanks!

Hi Maddog,

Can I please ask, what version of iTerm are you running? I will have to have a look as that may require some additional logic (I will have to play with the feature as I have not used it before).

Also with regards to the new feature, that is possible but it would be on an all or nothing basis, i.e. it can't really be set at run time. So are you looking for a set one off to change how the script as a whole runs or are you looking for something you can change each time it runs depending on what behaviour you would like at that time (just wanting to clarify, as the latter is not really possible).