07-04-2009
pro's and con's either way...
open source mean anyone can find and patch the bugs, but also anyone can find and exploit bugs.
I feel that often open source is more secure simple because patches usually come out faster if a bug is found. (but this is not always the case.)
at the end of the day security is more about you and your habits then what OS you are using.
don't open ports you don't need.
don't run services you don't need.
keep passwords strong.
do patching often.
6 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
This is a slick looking forum. Any chance on making the code for the forum open source? (1 Reply)
Discussion started by: ecupirate1998
1 Replies
2. IP Networking
Hello there,
I wanted to know the members' opinion about the best open source network management software which uses a web browser to show its interface and results.
I am interested in the software for both windows and Linux OSs.
Thanks. (4 Replies)
Discussion started by: Jawwad
4 Replies
3. UNIX for Dummies Questions & Answers
Hello
What is the best open source anti virus?
Thanks (4 Replies)
Discussion started by: mohammadmahdi
4 Replies
4. UNIX for Dummies Questions & Answers
Hello
what is the best open source antispam?
Thanks http://www.linuxforums.org/forum/images/smilies/icon_smile.gif (1 Reply)
Discussion started by: mohammadmahdi
1 Replies
5. Shell Programming and Scripting
Hi Friends
I'm new to this UNIX - I'm working on the porting project from Solaris To Linux i just want to map some commands from solaris to Linux so can any one please tell me how to get the source code of the commands like "ls", "cu", "du"
Regards
sabee (1 Reply)
Discussion started by: sabee.prakash
1 Replies
6. Fedora
Hi everyone,
I know the following questions are noobish questions but I am asking them because I am confused about the basics of history behind UNIX and LINUX.
Ok onto business, my questions are-:
Was/Is UNIX ever an open source operating system ?
If UNIX was... (21 Replies)
Discussion started by: sreyan32
21 Replies
LEARN ABOUT CENTOS
git-quiltimport
GIT-QUILTIMPORT(1) Git Manual GIT-QUILTIMPORT(1)
NAME
git-quiltimport - Applies a quilt patchset onto the current branch
SYNOPSIS
git quiltimport [--dry-run | -n] [--author <author>] [--patches <dir>]
DESCRIPTION
Applies a quilt patchset onto the current Git branch, preserving the patch boundaries, patch order, and patch descriptions present in the
quilt patchset.
For each patch the code attempts to extract the author from the patch description. If that fails it falls back to the author specified with
--author. If the --author flag was not given the patch description is displayed and the user is asked to interactively enter the author of
the patch.
If a subject is not found in the patch description the patch name is preserved as the 1 line subject in the Git description.
OPTIONS
-n, --dry-run
Walk through the patches in the series and warn if we cannot find all of the necessary information to commit a patch. At the time of
this writing only missing author information is warned about.
--author Author Name <Author Email>
The author name and email address to use when no author information can be found in the patch description.
--patches <dir>
The directory to find the quilt patches and the quilt series file.
The default for the patch directory is patches or the value of the $QUILT_PATCHES environment variable.
GIT
Part of the git(1) suite
Git 1.8.3.1 06/10/2014 GIT-QUILTIMPORT(1)