Open Source SW

6301885770_8c3b6aa962_z.jpg

1

It´s time to talk a little about Open Source Software.

If you can remember, we published a post about Software Licenses. This are to ensure software are going to be well distributed/implemented/modified by all of the user that sees it.

Recently I want to comment I assist to a litlle course of Software optimization for Machine learning, this means having all the posible resources of the machine (Yes Hardware level) really beaing used for your algorithm, code or software in general.

Only as a little intro, we used AVX3 and AVX2 to compare time execution and time optimization in code. All of these in Linux using gcc.

I am telling this little history because the topic of today is Open Source Software.

Acording to https://opensource.com/

Open source software is software with source code that anyone can inspect, modify, and enhance.

“Source code” is the part of software that most computer users don’t ever see; it’s the code computer programmers can manipulate to change how a piece of software—a “program” or “application”—works. Programmers who have access to a computer program’s source code can improve that program by adding features to it or fixing parts that don’t always work correctly.

Yes, If you remember i.e. GNU GPL this source code can be implemented, changed and distributed free. This means if you want to modify a part of the source code of a GNU GPL and sell it to another you can´t.

Something to keep on mind:

Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone.

Or, less formally, “Given enough eyeballs, all bugs are shallow.” I dub this: “Linus’s Law”.

from: https://blogs.microsoft.com/microsoftsecure/2006/06/07/linuss-law-aka-many-eyes-make-all-bugs-shallow/

Some of the benefits of using an Open Source software are:

Control: This means,

Continue reading "Open Source SW"

About Security certificates

https://www.jpao.es/wp-content/uploads/2015/10/seguridad.jpg
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

http://www.technipages.com/wp-content/uploads/2015/07/IE-problem-with-website-security-certificate.png
Continue reading "About Security certificates"

About basic software Licenses

How should we choose whether or not to apply one or many SW License to our work?

Below a few description of the basic ones:

Originally posted at: https://opensource.org/licenses/MIT

The MIT License (MIT)

Copyright (c) <year> <copyright holders>

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal 
in the Software without restriction, including without limitation the rights 
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 
copies of the Software, and to permit persons to whom the Software is furnished
to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in 
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 
SOFTWARE.

Originally posted at: http://www.apache.org/licenses/LICENSE-2.0

Apache License

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Originally posted at: https://www.gnu.org/licenses/gpl-3.

license
Continue reading "About basic software Licenses"