5.5 Legal and Ethical Concerns

Cost of Free

  • Use of GPL software can void rights to charge for software and patents
  • Open Source says any derivative work is free an code should be shared
  • Qualcomm wants all derivative work to require a royalty payment payment
    • Anyone who uses the idea/patent pays royalty

License Communities, License Types

  • Adding and selecting a license GitHub instructions. An author, a licensor, needs to determine a license. This may result in asking…
    • Do I want to waive default copyright in reuse?
    • Do I want to allow derivative works or not?
    • Do I want to require all derivative code to be shared?

Open source - Free, but you cannot sell it - Community - Creative Commons CC0 Public Domain Dedication (waives copyright) - Open Source MIT (allows for using code freely, and making and distributing closed source versions)(GitHub proj could be priv)

Close source - have to pay - Capitalism


5.5 Blog Post Reflection

  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. Open source MIT

  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. Open sourced licenses are more focused on community, while closed sources are focuses on making sales.

  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.

  • We have chosen the MIT Open Source


5.6 Safe Computing

Terms and Conditions - Digital Rights distribution - EX: Apps, Music,

Multi-factor authentication often requires you to enter a code that has been texted or emailed to you. Other types of authentication are biometrics (finger print or facial recognition).

Malware is often sent in attachments to things in email. Often they request you to click on an attachment and it starts the process of adding a virus to your computer.

Phishing is where unknown sources try to entice you into a response, like click here and receive $500. Often such systems impersonate someone like Amazon asking for login information. Be careful to look closely at source of email (ie amzn.com vs amazon.com).

  • A Virus or Malware compromise security, they are opposite of increasing security.

  • Phishing is a way to get a Virus on your machine, or a way to get you to input PII.

  • After a Virus or being compromised by Phishing it is advised to review all of you PII vulnerabilities.

2FA - Two-factor Authentication


Blog Post Reflection:

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

One example of PII I have seen in a CompSci Project was asking for the name, email and age. The name and email were visible to everyone.

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

I think that one has to be really careful with the PII one shares online. I try not to share my last name on social media or my exact age as it is something that can be potentially dangerous.

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

Good passwords are unpredictable, bad passwords have known PII in them, such as names.

  1. Try to describe Symmetric and Asymmetric encryption.

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

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