About Security certificates

Original image from: https://www.jpao.es/wp-content/uploads/2015/10/seguridad.jpg

Have you ever wondered why or who makes the little padlock in the url bar before the url of a web page?

Let´s be a little objective, related with one of my pasts post I touched the topic of doing software engineering with an ACM code of ethics for Sofware Engineering. Allright then, one of the principal areas disscussed then were about the rights of the end user and the professional.

Today we are going to talk about the security certificate, what are they and if you can trust one.

Thanks in advance to United States Computer Emergency Readiness team at: https://www.us-cert.gov/ncas/tips/ST05-010


What are web site certificates?

If an organization wants to have a secure web site that uses encryption, it needs to obtain a site, or host, certificate. There are two elements that indicate that a site uses encryption (seeProtecting Your Privacy for more information):

  • a closed padlock, which, depending on your browser, may be located in the status bar at the bottom of your browser window or at the top of the browser window between the address and search fields
  • a URL that begins with “https:” rather than “http:”

By making sure a web site encrypts your information and has a valid certificate, you can help protect yourself against attackers who create malicious sites to gather your information. You want to make sure you know where your information is going before you submit anything (see Avoiding Social Engineering and Phishing Attacks for more information).

If a web site has a valid certificate, it means that a certificate authority has taken steps to verify that the web address actually belongs to that organization. When you type a URL or follow a link to a secure web site, your browser

Continue reading "About Security certificates"

How to do Software ethically and don´t die trying.


Image from: https://howtobeastoic.wordpress.com/2015/09/17/ancient-vs-modern-ethics-a-comparison/

Every day, a lot of lines of code are written in the world with or without thinking of how, when and whom are going to use them.

Here we explain a little how a code of Ethics for Software Engineering works and is stablished, due to the need of ethics application in all professional activities.

Software engineers shall commit themselves to making the analysis, specification, design, development, testing and maintenance of software a beneficial and respected profession. In accordance with their commitment to the health, safety and welfare of the public, software engineers shall adhere to the following Eight Principles:

1. PUBLIC – Software engineers shall act consistently with the public interest.

2. CLIENT AND EMPLOYER – Software engineers shall act in a manner that is in the best interests of their client and employer consistent with the public interest.

3. PRODUCT – Software engineers shall ensure that their products and related modifications meet the highest professional standards possible.

4. JUDGMENT – Software engineers shall maintain integrity and independence in their professional judgment.

5. MANAGEMENT – Software engineering managers and leaders shall subscribe to and promote an ethical approach to the management of software development and maintenance.

6. PROFESSION – Software engineers shall advance the integrity and reputation of the profession consistent with the public interest.

7. COLLEAGUES – Software engineers shall be fair to and supportive of their colleagues.

8. SELF – Software engineers shall participate in lifelong learning regarding the practice of their profession and shall promote an ethical approach to the practice of the profession.

Seems easy right? Let´s check what these principles means to do:


The engineer shall accept for their work even if the work produces any good or bad situations. Test is an important thing in software related with

Continue reading "How to do Software ethically and don´t die trying."