v1.0

Release Notes for rbbedit v1.0

We are excited to announce the release of rbbedit v1.0! This major version bump signifies the stability and maturity
of the project, along with the introduction of two significant enhancements.

🚀 New Features

1. Automation Permissions Fix for macOS

   • Addressed the issue of missing Automation permissions when running bbedit from an SSH session.
   • Introduced a new command-line argument -P that allows users to request Automation permissions.
   • When the -P argument is passed, rbbedit uses an osascript to display a dialog in BBEdit, prompting the user
     to grant the necessary permissions for sshd-keygen-wrapper to control BBEdit.
   • Provides a seamless solution for users encountering the Automation permissions error, ensuring a smooth experience
     when using rbbedit from an SSH session.

2. Restricted SSH Access with bbedit-restricted

   • Added a new feature to enhance security by restricting SSH access to limited commands when using rbbedit.
   • Introduced the bbedit-restricted script, which allows only specific osascript, bbedit, and bbresults
     commands to be executed via SSH.
   • Implemented a new command-line argument -R that copies the bbedit-restricted script to the BBEdit workstation
     and provides instructions for updating the authorized_keys file.
   • By using the bbedit-restricted script and updating the authorized_keys file, users can ensure that SSH access
     is limited to the necessary commands required by rbbedit, providing an additional layer of security.

🎉 Version v1.0 Milestone

This release marks a significant milestone for the rbbedit project. With the bump to version v1.0, we acknowledge the
stability, reliability, and maturity of the codebase. rbbedit has undergone extensive testing and refinement to ensure
a solid foundation for remote file editing using BBEdit.

We express our gratitude to the community for their valuable feedback, bug reports, and contributions that have helped
shape rbbedit into a robust and feature-rich tool.

📝 Updated Documentation

The README file has been updated to reflect the new features and enhancements introduced in this release. It includes
detailed instructions on how to use the -P argument to request Automation permissions and the -R argument to set up
restricted SSH access using the bbedit-restricted script.

We highly recommend reviewing the updated README to familiarize yourself with these new features and ensure a smooth
transition to rbbedit v1.0.

🙏 Feedback and Support

We value your feedback and are committed to providing ongoing support for rbbedit. If you encounter any issues, have
suggestions for improvements, or want to contribute to the project, please don't hesitate to reach out. You can open an
issue on the GitHub repository for further assistance.

Thank you for your continued support and trust in rbbedit. We are excited to deliver these enhancements and look
forward to your feedback and experiences with version v1.0.

Happy remote editing with BBEdit!

The rbbedit Team

Full Changelog: v0.8.0...v1.0

A decade has passed

This release contains a few improvements, but also shows current activity for the project which is still useful and relevant in this decade. (Congrats to BBSW for getting to BBEdit v15 - 33 years of fantastic effort.)

• README updates
• support for keybase.io directory signing
• command option to set path to bbedit
• Only show who is associated with current session
• Added support for server-host username & hostname in SFTP connections

Squash complaints about certificate mismatch

Doing self-update was failing due to certificate mismatch when downloading from Github.

Add 'ftp' as a copy method

copy_method="ftp"
-m ftp

The 'ftp' copy method is almost identical to the 'sftp' method. The difference is that the home directory will be stripped from the filename, under the assumption that the FTP server is chrooting connections. So a relative path for the filename is used, if the first part of the path matches $HOME. You can disable the relative path behaviour by setting ftp_absolute=1 in your ~/.rbbedit file.

Installer and self-updating script

Self Updating

Use curl -L https://raw.githubusercontent.com/cngarrison/rbbedit/master/install.sh | sh to automatically install rbbedit.

Use the -+ option to update rbbedit using the latest version from GitHub. The update is done by downloading the install.sh script and running it.

Copy SSH public key between workstation and server

For easiest use of rbbedit, it's best to have the public SSH key on both the BBEdit workstation and the server host. Passing the -k command option with either get or send will transfer the SSH public key between hosts.

The send option will transfer the server host SSH public key to the BBEdit workstation. The get option will transfer the BBEdit workstation SSH public key to the current user account on the server host. Both options will attempt to use ssh-copy-id to tranfer the public key. If the get option fails with ssh-copy-id, then it will fallback to a simple cat $bbedit_key_identity >> ~/.ssh/authorized_keys method.

If the SSH identity file containing the public key cannot be found, you can specify which file to use with the -i option. Default values can also be specified in ~/.rbbedit with either local_key_identity or bbedit_key_identity options. In addition, you can specify defaults for the path to the ssh-copy-id executable on each host using the bbedit_ssh_copy_id_command or local_ssh_copy_id_command options.

[The -y option is not required in current version of rbbedit.] You must specify -y understood on the command line to show your understanding of the implications of copying SSH public keys. You can also set yes_agree="understood" in the ~/.rbbedit file.

The contents of ~/.ssh/authorized_keys on both BBEdit workstation and server host should be checked after running either the get or send key copy option.