is open source more secure ? Post: 302331526

Sponsored Content

Special Forums Cybersecurity is open source more secure ? Post 302331526 by Neo on Monday 6th of July 2009 12:38:25 PM

07-06-2009

Administrator

I would also like to add that, at least for me personally and speaking in sweeping generalities which I don't like to do; I feel less secure with "closed code" than "open code".

For me, I can easily trust what I can see. I can search open code more easily (and look for problems) than I can search a binary or encrypted code like encrypted PHP (which I cannot search at all).

Recently, I refused to install encrypted PHP on a web site for that exact reason. I do not trust code I cannot see and see no reason to install encrypted PHP code when I can find open alternatives.

As I mentioned before, I don't normally like to respond to generalizations without context, so I am simply providing my personal opinion, and that is that I (my personal opinion) feel more secure when I can examine the code, grep it, search it, add debug statements, etc.

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

6 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

open source for the forum

This is a slick looking forum. Any chance on making the code for the forum open source?

2. IP Networking

Open Source NMS

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.

3. UNIX for Dummies Questions & Answers

open source antivirus

Hello What is the best open source anti virus? Thanks

4. UNIX for Dummies Questions & Answers

what is the best open source antispam?

Hello what is the best open source antispam? Thanks http://www.linuxforums.org/forum/images/smilies/icon_smile.gif

5. Shell Programming and Scripting

Open Source

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

6. Fedora

Is UNIX an open source OS ?

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...

LEARN ABOUT DEBIAN

fssync-debug_volop

FSSYNC-DEBUG_VOLOP(8)					       AFS Command Reference					     FSSYNC-DEBUG_VOLOP(8)

NAME

       fssync-debug_volop - Display pending volume operation info (FSYNC_VOL_QUERY_VOP opcode)

SYNOPSIS

       fssync-debug volop -volumeid <volume ID>
	   [-partition <exact partition name>]
	   [-reason <sync protocol reason code>]
	   [-programtype <program type code>]
	   [-help]

       fssync-debug vo -v <volume ID>
	   [-pa <exact partition name>]
	   [-r <sync protocol reason code>]
	   [-pr <program type code>]

       fssync-debug vop -v <volume ID>
	   [-pa <exact partition name>]
	   [-r <sync protocol reason code>]
	   [-pr <program type code>]
	   [-h]
	   [-h]

DESCRIPTION

       The fssync-debug volop command displays information about the pending volume operation for a given volume, if any.

OPTIONS

       -volumeid <volume ID>
	   Specifies the numeric volume ID. Volume names are not permitted.

       -partition <exact partition name>
	   Specifies the exact partition name (e.g. /vicepa). Abbreviations are not permitted.

       -reason <sync protocol reason code>
	   Specifies numeric sync protocol reason code.  Available codes are listed in OpenAFS source file src/vol/fssync_inline.h. For
	   SYNC_REASON_NONE, use -reason 0.

       -programtype <program type code>
	   Specifies program type code. Permitted values are fileServer, volumeUtility, salvager, salvageServer, volumeServer and volumeSalvager.

PRIVILEGE REQUIRED

       The issuer must have write access to the file server.  Usually, this means that the issuer must be the local superuser "root" on the file
       server machine.

SEE ALSO

       fssync-debug_attach(8), fssync-debug_detach(8), fssync-debug_mode(8), fssync-debug_online(8), fssync-debug_offline(8),
       fssync-debug_error(8)

COPYRIGHT

       Copyright 2010 Sine Nomine Associates

       This documentation is covered by the IBM Public License Version 1.0.  This man page was written by Andrew Deason and Davor Ocelic for
       OpenAFS.

OpenAFS 							    2012-03-26						     FSSYNC-DEBUG_VOLOP(8)