<commit_before>Migrate ssh keys to new computer
================================

I need to use a set of ssh keys on a new machine. **In general, it is best to
generate new keys instead of copying old keys**, but this is a *temporary
solution*.

So, given that disclaimer, I copied the **~/.ssh** folder from the old machine
into a *temp folder* on the new machine.  This avoids copying over anything in
the new machine's **~/.ssh** folder.  Copy all *keyname*, *keyname.pub* files
to **~/.ssh**.  Also, copy the **~/.ssh/config** (if you have one).  Finally,
the new computer needs to add the keys. Do this with command for each key:

.. code-block:: bash

    $ ssh-add keyname

You will be prompted for the password for the key (if any).  Now, try the keys
out.  You should be able to ssh to all of the machines covered by the added
key(s).

Potential Problems
------------------

There can be a variety problems with the above process.  The above worked for
me without modification.  However, I think that file ownership and permissions
can be problematic.  One solution for `ssh permission problems`_ is available
just in case.
<commit_msg>add .. more:: to migrate post<commit_after>Migrate ssh keys to new computer
================================

I need to use a set of ssh keys on a new machine. **In general, it is best to
generate new keys instead of copying old keys**, but this is a *temporary
solution*.

.. more::

So, given that disclaimer, I copied the **~/.ssh** folder from the old machine
into a *temp folder* on the new machine.  This avoids copying over anything in
the new machine's **~/.ssh** folder.  Copy all *keyname*, *keyname.pub* files
to **~/.ssh**.  Also, copy the **~/.ssh/config** (if you have one).  Finally,
the new computer needs to add the keys. Do this with command for each key:

.. code-block:: bash

    $ ssh-add keyname

You will be prompted for the password for the key (if any).  Now, try the keys
out.  You should be able to ssh to all of the machines covered by the added
key(s).

Potential Problems
------------------

There can be a variety problems with the above process.  The above worked for
me without modification.  However, I think that file ownership and permissions
can be problematic.  One solution for `ssh permission problems`_ is available
just in case.

{'fraction_non_alphanumeric': 0.11998273629693569, 'fraction_numerical': 0.0, 'mean_word_length': 3.5185185185185186, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2882296', 'n_tokens_mistral': 655, 'n_tokens_neox': 615, 'n_words': 365}