5.5

1. When you create a GitHub repository it requests a license type. Review the license types in relationship to this Tech Talk and make some notes in your personal blog.

• There are closed and open source licenses. Closed means not open to public and open are.
• In closed you have to credit the original authors.
• GPL is open and it deosn't allow closed versions of itself to be made
• Both are great but have different uses
• Can be helpful for sharing software. In Github we often reuse code such as themes so the license gives credit to it. Makes it free of charge for the user
• There are many differetn types

2. In your blog, summarize the discussions and personal analysis on Software Licenses/Options, Digital Rights, and other Legal and Ethical thoughts from this College Board topic.

• Copyright can be dangerous. Many people use it for their own gain at expense of others. It takes other people work and doesn't give them credit meaning they lose money.
• License helps keep copyright away by claiming a product.
• We can use liscenses on Github to claim our own work.
• It is not easy to detest if someone stole your liscense however.

3. Make a license for your personal (blog) and Team repositories for the CPT project. Be sure to have a license for both Team GitHub repositories (frontend/backend). Document license(s) you picked and why. FYI, frontend, since it is built on GitHub pages may come with a license and restrictions. Document in blog how team made license choice and process of update.

• https://github.com/JakeWarren2414/dolphins2/blob/gh-pages/LICENSE
• We chose a GNU General Public License because of its accesibility and easiness to use
• https://github.com/JakeWarren2414/FirstFastpages/blob/master/LICENSE
• I am using the Apache license because of the easines to edit. I am not using trademark use so I don't need that. I am using private use and modicfication se so this license is perfect. There is a reason it is default.

5.6

1. Describe PII you have seen on project in CompSci Principles.

• I have seen people use usenames, emails, date of birth, and more in their projects. My project includes, username, BMI, calorie intake, sport, and workout routine.

2. What are your feelings about PII and your personal exposure?

• I feel like we should be more careful about PII. If we reveal too much information soemone could take our identity, attack us, or use that information for bad puroses. Of course things like name, country, and credit reports aren't too bad. However, once we give away more personal information such as drivers license number, SS number, and names of reletives it can be dangerous.

3. Describe good and bad passwords? What is another step that is used to assist in authentication.

• A good password would be a name of a pet followed by some number that is personal to you and only you know such as Sammy2414. A bad password would be one that is easily guessed such as 12345678, or one that has accesible information about you such as your instagram username.

4. Try to describe Symmetric and Asymmetric encryption.

• Symmetric encrption is where you only use one key like a password to detec some sort of information. Aysmmeric is where you use two, one public and one private like a username and password.

5. Provide an example of encryption we used in AWS deployment.

• We use the link of our website, the key of our website, and when we make a github page we have to enter a key.

6. Describe a phishing scheme you have learned about the hard way. Describe some other phishing techniques.

• A phishing scheme I have learned is people pretending to be some official such as a member of a credit card company to achieve sensetive information. I have also seen people send a link that when clicked gives information. Finally I have also seen people make websites that require inforation to sign up and it takes that information.