Virtual Machines

admin — Tue, 10 Dec 2024 15:13:12 +0000

FASRC does not provide a general virtual machine service as part of its core services. It has in the past attempted to fill this gap when no other options were available, but 1) there was no funding for hardware or support for this and the ad-hoc infrastructure used is old and retired/being retired 2) other options, within and without Harvard, now exist.

If you require a VM for web hosting or other needs or for hosting or sharing data sets, please see the following options.

Harvard-based options:

Harvard Dataverse: hosting for data sets https://dataverse.harvard.edu
Harvard NERC: Self-service VM provisioning and other services https://nerc.mghpcc.org
Harvard Web Publishing group: Web publishing and consulting https://hwp.harvard.edu
Research Support options https://researchsupport.harvard.edu/dissemination-preservation
More data sharing and publishing options https://researchsupport.harvard.edu/data-sharing-and-publishing
Digital Scholarship Support Group: Web consulting services https://dssg.fas.harvard.edu/initiatives/research
HUIT’s Cloud services: Help with using AWS and other cloud resources https://cloud.huit.harvard.edu/services

Self-service, pay as you go, managed by you:

Amazon Web Services (AWS): https://aws.amazon.com
Google Cloud Platform (GCP): https://cloud.google.com
Digital Ocean: https://www.digitalocean.com

Please note that PIs and other data owners are responsible for following Harvard Information Security Policy and all other applicable Harvard policies and requirements. This includes knowing your data and following the requirements for Data Security Level for servers and Research Data Management Security and Ownership Policies

MacOS Sequoia SSH ‘corrupted’ bug

admin — Thu, 10 Oct 2024 17:47:02 +0000

October 2024: This doc addresses a current issue on the new MacOS Sequoia. This should be fixed in a future update and should not be considered current information for MacOS versions beyond 15.0.1

DISCLAIMER: The following information is meant as a courtesy to help cluster users who are experiencing this issue and it is impacting their work. You should decide if you wish to make these changes at your own risk or wait for Apple to push out a fix.

If you manage your own Mac (HUIT has not yet pushed out Sequoia to Harvard Macs) and receive an error message like:

Bad packet length [some large number].

ssh_dispatch_run_fatal: Connection to [an IP address] port 22: Connection corrupted

You can manually add SSH to your Mac’s firewall rules. Again, proceed at your own risk or wait for an Apple update.

If you are using the built-in Mac SSH, open Terminal and run:
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /usr/bin/sshYou will need to supply your local use password (the one you log in with) when running sudo.
If you have installed SSH via homebrew, open Terminal and run:
sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /opt/homebrew/bin/sshYou will need to supply your local use password (the one you log in with) when running sudo.

Informational – FASRC DOCS

Virtual Machines

MacOS Sequoia SSH ‘corrupted’ bug