Changes

Jump to: navigation, search

SPO600 Communication Tools

583 bytes added, 09:10, 6 September 2023
Other Communication Tools
# Enter this command: <code>ssh-keygen -t ed25519</code>
#* Answer the questions asked by ssh-keygen. Use default values for most questions. The use of a passphrase is '''strongly''' recommended. Avoid changing the filename from the default (unless there is a really good reason), because the location, name, and permission of keys is critical.'''DO NOT FORGET YOUR PASSPHRASE!'''
#* ssh-keygen will produce two files; the name will be the same but the location will vary according to the operating system in use:
#** <code>~/.ssh/id_ed25519</code> - your private key- do not let anyone else have this file#** <code>~/.ssh/id_ed25519.pub</code> - your public key- this file can be freely shared with anyone#* The permissions on these files matter! Take this in to account if you move these files or copy them between systems:#** <code>~/.ssh</code> directory must have permission 0700 (rwx------)#** <code>~/.ssh/id_ed25519</code> must have permission 0600 (rw-------)#** <code>~/.ssh/id_ed25519.pub</code> should have permission 0644 (rw-r--r--)
{{Admon/tip|Key Type and Length|ssh-keygen can generate multiple types of keys, including rsa, dsa, ecdsa, and ed25519. Any of these types serves the same purpose, and rsa/dsa can be generated with varying key lengths. The longer the key, the more difficult it is to break the key by guessing it (trying successive values until the right key is found) - each bit added to the key doubles the number of possible key values. Key lengths of 1024-4096 bits are considered reasonably secure; as computers become faster, key lengths should be increased. Better yet, use the ed25519 eliptic curve option, which is considered the most secure format supported by the current OpenSSH implementation (8.4 as of the time of writing).}}
=== Make a Copy of Your Submitting your Blog URLs and SSH Public Key =Keys ==# Copy Once you have the blog feed and public key file to <code>''UserID''ready, enter them on the [https://forms.office.pub<com/r/code> -- for exampleMxe4wcBJ41 Blog and SSH Information Form]. == Updating your SSH Key == If you need to update your SSH key, if you want can do so by logging in to have the user ID ''superhacker3000'', name your file <code>superhacker3000SPO600 account(s).pub</code>
== Submitting If you do not have access to your Blog URLs and account, please send an email to your professor, with the subject line "SPO600 SSH Key". Attach a '''copy''' of your updated SSH Public Keys =='''public''' key named <code>''yourUserId''.pub</code>
Once you have the blog feed and Warning: Sending a new SSH public key ready, enter them on the [https://forms.office.com/Pages/ResponsePage.aspx?id=Svc06-dYi0qeWUM-TEEnVxA8PnpzsPpIhWTKX2RkUF1UN1E2U1RCNVZLMzBHQTQ0SDVLSlNZMjlRUC4u SPO600 Blog and SSH Information Form]to your professor will invalidate your previous key.
<!-- == IRC ==
When communicating with your professor by email, please use your Seneca-provided e-mail address as the "From:" address (<code>''yourname''@myseneca.ca</code>). Because your professor receives a '''huge''' amount of email, it's critical to include your course code in the subject line of each of your messages.
<!--
=== Slack ===
Slack is an online discussion system. Sign up to use the [https://seneca-open-source.slack.com Seneca Open Source Slack] workspace (sign-up with your @myseneca.ca email; this same Slack workspace is used in the [[OSD600]]/[[DPS909]] course, so you may already have an account if you're also taking that course).
<!--
== Etherpad ==

Navigation menu