AutoPkgr 1.4.2

Fresh off the release of macOS Sierra, we've got a new version of AutoPkgr that includes some important fixes for 10.12 compatibility. We've also added amazingly easy one-click integration with the great new VirusTotalAnalyzer processor from Hannes Juutilainen, which checks downloaded files against the VirusTotal database.

Important note: this version of AutoPkgr no longer supports OS X Mountain Lion (10.8).

If you have any questions, find us on Slack or Google Groups. If you find a reproducible bug, we'd love it if you'd open an issue on GitHub. Thanks!

 

Added

• One-click integration with @hjuutilainen's VirusTotalAnalyzer processor. (#503)

Changed

• Updated versions of MMMarkdown and MailCore2 used in AutoPkgr.
• Clarified wording on the selective notifications picker (thanks to @poundbangbash for the wordsmithing).
• Prepared for localization, starting with French. (#537, big thanks to Guillaume Gete)
• Left-aligned results of recipe searches.
• Updated hard-coded default list of AutoPkg repos used when GitHub is not accessible.

Fixed

• Fixed issues with storing notification credentials in the AutoPkgr keychain in macOS Sierra. (#554, #555)
• Fixed the AutoPkgr Slack bot icon URL. (#527)
• Fixed a bug that would prevent notifications from being sent if the notification trigger actions were never customized. (#533)
• Fixed a bug that caused the width of the AutoPkgr window to snap back to defaults when clicking on the Notifications tab. (#499)
• Some typos found and corrected.

Removed

• Removed 10.8 support. AutoPkgr now requires Mac OS X 10.9 or higher.

AutoPkgr 1.4.1

Version 1.4.1 of AutoPkgr is now available, and it has a larger-than-your-average-point-release number of improvements and changes. Take a look:

Added

• AutoPkgr now allows you to customize the template used to generate notifications when new actions have occurred. Check it out at the bottom of the Notifications tab. (#184)
  

Fixed

• Fixed a long-standing issue that caused an incorrect prompt for the AutoPkgr keychain password! (#469)
• Addressed several issues that may have prevented notifications from working reliably in version 1.4. (#508, #515)
• Fixed a crash caused by the SMTP server setting being blank. (#502)
• AutoPkgr launches a bit faster now. (#500)
• AutoPkgr now reports InstallFromDMG processor results in addition to Installer processor results.
• Fixed an issue that would cause the email notification subject to be blank.

Changed

• Adjusted default formatting of email and Slack notifications. (#507)
• Added logging for SMTP operations.
• Prevented password field from wrapping to a "new line." (#481)
• Increased width of active recipe list picker.
• Updated versions of MMMarkdown and MailCore2 used in AutoPkgr.

Security

• A note on keychain security in AutoPkgr 1.4.1:

  The fix for issue #469 requires AutoPkgr to be less aggressive when locking the AutoPkgr keychain (a separate keychain stored in ~/Library/Keychains that stores your SMTP credentials for email notifications). It's possible for somebody with access to your AutoPkgr Mac to obtain your SMTP password using the security command while the AutoPkgr keychain is unlocked.

  Here's why AutoPkgr exceeds our security requirements, even with less aggressive keychain locking:

  • AutoPkgr's locking behavior is still more restrictive than your login keychain's behavior.
  • Physical access or VNC to your AutoPkgr Mac is necessary to use the security command to obtain the SMTP password.
  • AutoPkgr goes to great lengths to keep the actual AutoPkgr keychain password both unknown and unnecessary to know, which prevents password exposure via the Keychain Access app.

  Taking common sense security steps should mitigate any risks introduced by this change. Here are three to consider:

  • Use an SMTP account dedicated to AutoPkgr for email notifications.
  • Run AutoPkgr on a dedicated Mac or VM, rather than using one shared by other services.
  • Unless necessary, don't leave the Mac logged in. AutoPkgr works great at the login window (which is why it has its own keychain in the first place), and a Mac at the login window is magnitudes safer than one with an active user session.

 

As always, please submit any issues you find on GitHub, or find us on Slack or Google Groups if you have questions. Have a great week!

AutoPkgr 1.4.1 release candidate 4

v1.4.1-rc4

Increment build number to match 1.4 release.

AutoPkgr 1.4

There's a little something for everybody in this major AutoPkgr release! We especially think you'll love the ability to mute certain types of notifications, the new simplified JSSImporter interface (with CDP support), and the much-requested ability to add/remove repos and recipes in bulk using multi-selection.

As always, get in touch with us if you have questions! Questions are welcome in our Google Group, and if you find a reproducible problem, please submit an issue on GitHub. The #autopkg channel on the MacAdmins Slack team is also an excellent place to get real-time support for AutoPkg and AutoPkgr.

We hope you love it! 👍

Added

• You can now select which events trigger a notification. For example, you can receive only Munki import notifications, and ignore download notifications. In other words, no more daily emails about VLC downloading! (#184)
• Ability to select multiple repos and then update, add, or remove the selected repos. (#434)
• Ability to select multiple recipes and then run, enable, or disable the selected recipes. (#434)
• Built-in integration with FileWave version 10 and higher, via the new FileWaveImporter processor. (#339, with thanks to @johncclayton.)
• Integration with new LANrevImporter processor. (#488) See the LANrevImporter wiki for information on migrating from AbsoluteManageExport.
• Ability to switch between multiple recipe lists. (#263)
• Ability to specify pre/post processors. (#346, #384)
• MakeCatalogs.munki will be included when .munki recipes are run from the contextual menu. (#485)

Fixed

• Fixed a bug that caused progress spinners to incorrectly display on multiple recipes if they share the same name. (#447)
• Fixed a bug that caused AutoPkgr to freeze when adding a custom repo with a trailing space in the URL. (#486)
• Fixed a minor counting error in log output. (#446)
• Fixed crash that occurred if Git was not reinstalled after an OS X upgrade. (#458)
• Fixed a bug that resulted in unreliable "Run This Only Recipe Only" selection. (#456)
• XPC connections to helper tool are now explicitly closed on process completion.

Changed

• Totally redesigned and simplified the JSSImporter settings sheet.
• JSSImporter configuration UI now supports cloud distribution points (CDP) and local distribution points. (#463, #309)
• MakeCatalogs.munki recipe is now added by name rather than by identifier. An override with the same name will now be used, if one exists. (Hat tip to @grahampugh.)
• General improvements to integration performance. No longer makes duplicate GitHub API calls when "releases" don't exist.
• Updated "AutoPkgr" link in footer of notification emails to point to AutoPkgr information page instead of GitHub repo.
• Moved Recipe/Override chooser out of contextual menu and into AutoPkg preference panel.
• Widened images in readme.md so they'll look awesome with GitHub.com's new repo layout.
• Updated bundled version of Sparkle auto-update framework.
• The "Add Repo" button and associated text field now work with any supported URL, not just HTTPS.
• When you right-click and run a single Munki recipe, AutoPkgr will now run MakeCatalogs.munki too.
• Made width of tab views more consistent.

AutoPkgr 1.3.2

AutoPkgr 1.3.2 is now available, and fixes a couple bugs that were reported by the community.

Added

• You can now specify the name of the AutoPkgr bot when configuring Slack integration. (#437)

Changed

• Now includes localized hostname in all notifications, not just email.

Fixed

• Fixed an unpleasant freeze that occurred after installing JSSImporter. (#443)
• AutoPkgr now more gracefully handles mid-run interactive prompts from AutoPkg, which is usually a result of missing parent recipes. (#441)
• Fixed a bug that resulted in errors when a repo path contained spaces. (#435)
• Fixed a tiny typo in the default Munki repo path.
• Resolved an issue in the CocoaPods configuration.

If you have any trouble with AutoPkgr, first check the Troubleshooting section of the README file. We've tried to describe a few common solutions to problems there.

Still have questions after reading the manual? Reach out to us on the MacAdmins Slack channel, or on the AutoPkgr discussion group. Or if you believe you've discovered a reproducible bug, please submit an issue on GitHub.

We've started collecting AutoPkgr-related success stories on the Linde Group website, and we'd love for you to share your story if you feel so inclined!

Have a great day.

AutoPkgr 1.3.1

AutoPkgr 1.3.1 is a minor update that focuses on fixing a couple bugs and adding some small features.

Added

• Now supports GitHub two-factor authentication for generation of API tokens. (#393)
• Made Slack and HipChat output more verbose, including errors. (#417)

Changed

• Changed the way a valid user is determined when adding a schedule. Users not physically logged into the system can now enable the schedule assuming they have a valid home directory, and a com.github.autopkg.plist preference file. (#416)

Fixed

• Adjusted a few things that should improve AutoPkgr's behavior when running on Mac OS X 10.8.
• Fixed a bug that would cause proxy settings to be displayed incorrectly. (#399)
• Fixed a bug where schedule changes would not reload in-memory launchd schedule.
• Incorporates a new version of AHLaunchCtl, which improves the reliability of the schedule settings.
• Fixed a bug that would prevent JSSImporter-related defaults from getting set.
• Fixed a bug that would result in repos appearing twice in the repo table. (#406)
• Fixed a bug causing search results to be incorrectly formatted. (#410)
• Improved handling of git operations when using proxies.
• Resolved issue where Slack/HipChat settings were not saving properly in OS X El Capitan. (Note: AutoPkgr does not officially support El Capitan yet.)

Removed

• AutoPkgr no longer attempts to automatically correct or change JSS URLs entered through the "Configure JSSImporter" options. As long as the URL you enter is valid, you shouldn't notice this.

Do you love AutoPkgr? We want to hear from you! Take a minute and tell us how AutoPkgr has made your life easier.

As always, if you discover a reproducible bug, the best thing to do is submit an issue on GitHub. This is how bug fixes like the ones in 1.3.1 happen!

Happy packaging.

AutoPkgr 1.3

We're proud to announce AutoPkgr 1.3, with a ton of new features and improvements.

Along with integration with Absolute Manage and MacPatch, there are new scheduling options (running at a specific time every day) and notification options (notifying a Slack or HipChat channel). We've also polished and refined the interface, and reworked the back-end to more easily support future integration with other AutoPkg processors.

See a full list of the changes below:

Added

• Integration with Absolute Manage (via the AbsoluteManageExport processor). (#217)
• Integration with MacPatch (via the MacPatchImporter processor). (#347)
• Now you can send notifications directly to a Slack (#358) or HipChat (#359) channel.
• More flexible options for scheduling AutoPkg to run. New daily and weekly options! (#361)
• By popular request, you can now right-click on a recipe and choose Run This Recipe. (#107)
• You can also right-click on a recipe in the list and choose Get Info to see various details about the recipe. (#342, #357, #370)
• Right-click on a repo to access the GitHub commits page or update a single repo. (#357)
• The repo and recipe lists are now sortable! (#356)
• The repos list now displays the number of stars each repo has on GitHub (and you can sort by them too). (#356, #357)
• Proxy configuration is now much easier than typing Terminal commands. Just go to the Folders & Integration tab, then click on Configure AutoPkg to access the proxy settings.
• In the same location as the proxy settings, you can now create the GitHub API token used with autopkg search feature using AutoPkgr. This allows a greater number of search queries per hour.
• The install tab now displays status of additional integrated tools and processors, like AbsoluteManageExport and MacPatchImporter.
• Easier uninstallation of components like JSSImporter and AbsoluteManagerExport. (#332)
• Better validation of the standard output AutoPkgr receives from AutoPkg.
• Ability to change the Git binary used by AutoPkg.
• The repos list now has a status indicator showing if there are new commits to an installed repo. (#357)
• The recipe list now has a status indicator showing if a recipe is missing a parent recipe. (#357, #370)
• We're now using OS X Notification Center for a few useful messages, like when new software has been packaged by AutoPkg. (#79)
• Added the ability to configure how often notifications are sent for new version of AutoPkg, JSSImporter, Git, and other components. (#379)
• Added a "Check for AutoPkgr Updates" item in the AutoPkgr menu extra. (#275, #312)

Changed

• New JSSImporter users will now get the "official" jss-recipes repo when configuring JSSImporter.
  Note: Existing JSSImporter users will not (yet) be affected, but will eventually need to transition to the new repo. Instructions will be available soon. In the meantime, read through the jss-recipes readme!
• Reworked Folders & Integration tab interface to support a theorically unlimited number of integration tools, including Munki, Casper, Absolute Manage, and MacPatch. The sky is the limit.
• Updated readme to make it clear that you should only update repos before every AutoPkg run if you trust recipe authors.
• Removed unused menus and menu items.
• Significantly rewrote the readme with new and updated information.
• Behind-the-scenes code cleanup, typo fixes, refactors, and reorganization. Always tidying up!

Fixed

• Fixed a bug that could prevent email configuration changes from "sticking."
• Squished a bug that could cause the JSS_VERIFY_SSL key to be incorrectly set.
• Stomped on a bug that resulted in a "(null)" error in certain circumstances. (#352)
• Swatted a bug that required pressing Tab or Enter in order to save the email password before sending a test email. Now the password is saved upon clicking the Send Test Email button as well. (#352)
• When a JSSImporter update was available, the text on the Install tab would often overflow its container. We've enlarged the container, so hopefully that won't happen now. (#314)
• AutoPkgr now remembers the last window position and table sort status upon subsequent launches. (#375)
• Squashed a bug that resulted in "Version (null)" in OS X notifications. (#376)
• Eradicated a bug that could cause AutoPkgr to falsely believe there are multiple instances of AutoPkg running.

We don't just love community feedback; we require it! AutoPkgr wouldn't be as cool as it is without the input from Mac admins who use it. Get in touch with us and let us know what you think.

To get help with AutoPkgr, you can find us on our Google Group or submit an issue on GitHub. You can also sometimes get help and ideas on the MacAdmins Slack channel. Also, we've greatly expanded the Troubleshooting section of our readme, so please do check that out.

Hope you love it!

AutoPkgr 1.2.3

Hello friends! We've got a new version of AutoPkgr for you. This has a few small fixes and changes, including more friendly display of the "Last AutoPkg Run" status in the menu and a long-awaited fix to a problem reported by a few Chrome users.

Changed

• Now you can check the SSL box even if you're not using SMTP authentication. (#335)
• Relative date/time now shown in AutoPkgr menu status (e.g. "Today at 8:00 AM"). (#340)

Fixed

• Fixed a particularly devious bug that would cause AutoPkgr to get stuck running recipes while certain apps (usually Google Chrome) were active. (#230)
• AutoPkgr menu status should now be up to date upon first click, not just upon status change. (#340)
• Fixed a bug that caused progress indicators to show inaccurate counts when the StopProcessingIf processor is present in a recipe. (#333)
• Reduced the odds of error messages overflowing the on-screen alert dialog boxes.
• AutoPkgr now asks for XML when talking to your JSS, but should successfully revert to JSON if your JSS stubbornly refuses. (#287)
• Fixed a minor bug that could result in excess CPU usage.
• Various minor cosmetic changes.

Security

• Updated to the most recent version of the AFNetworking components.

We're constantly improving AutoPkgr based on community feedback. If you have ideas for future features, if you want to report a bug, or if you just have questions about using AutoPkgr, the best way to get in touch with us is to submit an issue on GitHub. If you don't have or want a GitHub account, you can also reach us at the autopkgr-discuss Google group. Thank you!

AutoPkgr 1.2.2

Welcome to AutoPkgr 1.2.2! This is a minor update focused on supporting upcoming changes in how AutoPkg reports its actions.

Added

• Compatibility with upcoming changes to AutoPkg reporting format.
• Updated documentation to include information about creating/editing overrides.
• Items in Help menu now link to useful URLs. (#12)

Changed

• AutoPkgr now prevents you from proceeding beyond the Install tab if you don't have AutoPkg and Git installed. (#325)

If you have any issues with AutoPkgr, please submit an issue on GitHub. We always welcome your feedback.

Thank you!

AutoPkgr 1.2.1

Following up on our big 1.2 release, we've released 1.2.1 with a few bug fixes and enhancements:

Added

• Created changelog.
• AutoPkgr now displays the version number of Git and AutoPkg in the Install tab. (#244)
• Now you'll receive an email when new versions of Git, AutoPkg, or AutoPkgr are available. (#137)

Security

• Now using three-way encryption to store SMTP password more securely. (#271)
• Improved security of the helper tool AutoPkgr uses to run in the background.
• AutoPkgr now tries to obfuscate sharepoint usernames and passwords in email notifications. (#227)

Fixed

• Background run not updating date in status menu. (#286)
• Resolved an issue that prevented "Launch at Login" button from working in 10.8 and 10.9. (#272)
• Prevented displaying progress detail messages unnecessarily.
• Properly processes %20 in URLs when parsing versions. (#270)
• Fixed the "Check for repo updates before each recipe run" checkbox wording.
• Fixed a bug that prevented status messages over 50 characters from being displayed in the menu.
• Fixed a bug that prevented autopkg run status from appearing in the menu.
• Made configuration options for "Run AutoPkg Now" consistent with menu items.
• Fixed a situation that prevented launchd from reading current defaults values. (#296)
• Now showing AutoPkgr icon in both the Dock and the menu bar by default.
• Small improvements to keychain migration method.

Changed

• Uninstall is now handled by the main app, not the helper tool.

As always, if you find any bugs or encounter problems, we welcome you to open a new issue on GitHub. Thank you!