5.5 and 5.6 Blog
5.5 Legal licensing and Ethical Concerns
Cost of Free
- Open source allows you to use it freely.
- Qualcomm wants royalty on their products.
Blog Post Reflection
- 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.
- In the license file, it talks about the distribution, use and reproduction of this license. It allows you to make modifications, cannot modify the license, give credit.
- 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.
- It is good to have credit to the owner but it would also prevent creativity because whenever someone has an idea but it is copyrighted, they cannot produce the good idea that they have.
- 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.
- I want to make an opensource project that allows users to use our project and hopefully improve the work that we have done.
5.6 Safe Computing
Consider using an separate junk email so that you are not giving out your information
Things known to others: Name, email, picture, school, state residence
Gray area: Birth date, place of birth, street address, phone number, driver license number
Keep secret: Credentials for access, Tw-factor Authentication onn financial accounts, social security number, tax records
Ways that they could trick you
- Malware, (makes you install a bad virus)
- Phishing, (Try to get you to respond so that you give them information)
Ways to increase your security
- Multi factor authentications- Email or text code
- Biometric- Fingerprint or facial recognition
- Symmetric- Use of a key
- Asymmetric cryptography- One public and one private key
Blog Post Reflection
- Describe a PII you have seen on a project
- We needed to input a public and private key when we first set up out fast pages at the start of the trimester
- What are your feelings about PII and your personal exposure?
- I think that I might have possible already put in my information into different applications and that I need to start changing this habit.
- Describe good and bad passwords.
- Good passwords are the ones that have combination of characters. Bad passwords are the simple ones like 1234, or the ones that have personnel information, like your birthday. You could connect your email for two factor authentication.
- Describe symmetric and asymmetric encryption.
- In symmetric- you get a key that usually changes once in a while, this code can ben used to log into your account. In asymmetric, there is a private key and public key, like the one that was used to set up the fastpages.
- Example of encryption in AWS deployment.
- We needed to encrypt our key that we used to set up our AWS deployment.
- Describe a phishing scheme you learned about the hard way.
- There are lots of email that I get that are fake like you won an ipad, I haven't clicked on these emails, but I could imagine them trying to steal the users information.