07-06-2009
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.
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 DEBIAN
rskeygen
rskeygen(1) General Commands Manual rskeygen(1)
NAME
rskeygen - generate private key pairs for TI graphing calculators
SYNOPSIS
rskeygen [ --secure ] [ --ti ] [ --length nbytes ]
DESCRIPTION
rskeygen generates application and OS signing keys for the Texas Instruments TI-73, TI-83 Plus, TI-84 Plus, TI-89, and TI-92 Plus graphing
calculators. These keys consist of two prime numbers p and q as well as their product n. Current calculator models impose a limit of 512
bits (64 bytes) on the size of n, so p and q are generally about 256 bits each. As of this writing this means factoring n is beyond the
reach of most people, though this will undoubtedly change in the future.
The keys generated by rskeygen are not very useful at the moment, because in order for an application or OS to be accepted by the calcula-
tor, the key used to sign it must itself be signed using the calculator's own (possibly unique) private key, which is only known to TI.
Nevertheless, rskeygen is provided in the hope that it can be useful, both for testing and for devising new signature schemes based on
TI's.
OPTIONS
--secure
Attempt to generate a ``secure'' key using the system's entropy pool, /dev/random (see random(4).) The actual security is thus
dependent on your system's implementation of /dev/random.
Without --secure, the keys are generated based on the current time and process ID, which is not secure in the slightest.
--ti Generate keys which are palatable to TI's official app signing programs. This forces p to be congruent to 3 and q to 7 modulo 8.
This option is not necessary when using rabbitsign(1), nor is it necessary for the calculator to validate signatures properly.
--length nbytes
Specify the length in bytes of the modulus n; p and q are each calculated to be approximately half this length. This should not be
greater than 64 for current calculators, and must be less than 256 in any event due to a limitation of the key file format.
SEE ALSO
rabbitsign(1), packxxk(1)
AUTHOR
Benjamin Moody <floppusmaximus@users.sf.net>
RabbitSign 2.0 July 2009 rskeygen(1)