08-30-2008
A good practical test of randomness is: does it compress well? If not, it's random. (Not necessarily truly random, of course; a compressed file doesn't compress well, because the redundancy has been reduced by the compression algorithm, but if you know the input and the compression algorithm, it can be reconstructed at will.)
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
When should one have to generate a public key on a Server when the public key is already created and used by other clients?
Thanks,
Rahul. (6 Replies)
Discussion started by: rahulrathod
6 Replies
2. Linux
Dear All,
I need to decrypt with private key most of the time and this works for RSA. At times I need to decrypt with public key (data is encrypted with private key). This does not seem to work via VB.Net. Is there support for such an activity in Java on Linux or Windows ? Please advise.
... (3 Replies)
Discussion started by: Sushma Y
3 Replies
3. UNIX for Dummies Questions & Answers
Hi all
Ive setup a VSFTPD server and im forcing SSL encryption. I have made a key and it works perfectly.
I have a client who wants to connect but is using software that needs the key to be added before he can connect.
Does he need me to send the key i created and that the VSFTPD.conf... (0 Replies)
Discussion started by: mokachoka
0 Replies
4. Cybersecurity
Hey all, I have a request from a third party that will be setting my firm up for an account so we can sftp files to their server in a Production environment. I know where the public keys are located on our Red Hat Linux envronment. I was going to ftp the keys from the Linux environment over to my... (2 Replies)
Discussion started by: dfb500
2 Replies
5. Solaris
Hi, I've used the following way to set ssh public key authentication and it is working fine on Solaris 10, RedHat Linux and SuSE Linux servers without any problem. But I got error 'Server refused our key' on Solaris 8 system. Solaris 8 uses SSH2 too. Why? Please help. Thanks.
... (1 Reply)
Discussion started by: aixlover
1 Replies
6. Shell Programming and Scripting
I generated a public key that we are using for ssh and sftp but I noticed that I am still being asked for a password when I run my script. is there something I need to put in my script?
Our linux guy said he placed keys on both servers. (2 Replies)
Discussion started by: MJCreations
2 Replies
7. AIX
Hi Guys,
I am trying to import the public of vendor to my system. I am getting below error while importing public key. can anyone please help me with this??
laranakejt4:/u/raja/.pgp $ pgp --import secure.asc
0x1545A56A52:import key (4007:key failed signature check)
secure.asc:import key... (0 Replies)
Discussion started by: Vinoth Kumar G
0 Replies
8. UNIX for Dummies Questions & Answers
Hi Guys,
I am trying to import the public of vendor to my system. I am getting below error while importing public key. can anyone please help me with this??
laranakejt4:/u/raja/.pgp $ pgp --import secure.asc
0x1545A56A52:import key (4007:key failed signature check)
secure.asc:import key... (2 Replies)
Discussion started by: Vinoth Kumar G
2 Replies
9. UNIX for Advanced & Expert Users
Hi,
we have private and public key, encrypt file using public and want to decrypt using private key. can you please advise below commands are correct or other remedy if unix have?
encrypt -a arcfour -k publickey.asc -i TESTFILE.csv -o TESTFILE00.csv
decrypt -a arcfour -k privatekey.asc... (2 Replies)
Discussion started by: rizwan.shaukat
2 Replies
10. Shell Programming and Scripting
Hi All,
While using ssh command and not able to decrypt the files . if run manually and it working fine . that means connect to server and running the pgp command.
ssh devtesting@198.120.190.34 'cd /home/test/load; pgp --decrypt --passphrase "pstestingThe" --input *'
Cloud please help... (10 Replies)
Discussion started by: bmk123
10 Replies
LEARN ABOUT OPENDARWIN
uncompress
COMPRESS(1) BSD General Commands Manual COMPRESS(1)
NAME
compress, uncompress, -- compress and expand data
SYNOPSIS
compress [-cfv] [-b bits] [file ...]
uncompress [-cfv] [file ...]
DESCRIPTION
The compress utility reduces the size of the named files using adaptive Lempel-Ziv coding. Each file is renamed to the same name plus the
extension ``.Z''. As many of the modification time, access time, file flags, file mode, user ID, and group ID as allowed by permissions are
retained in the new file. If compression would not reduce the size of a file, the file is ignored.
The uncompress utility restores the compressed files to their original form, renaming the files by deleting the ``.Z'' extension.
If renaming the files would cause files to be overwritten and the standard input device is a terminal, the user is prompted (on the standard
error output) for confirmation. If prompting is not possible or confirmation is not received, the files are not overwritten.
If no files are specified or a file argument is a single dash ('-'), the standard input is compressed or uncompressed to the standard output.
If either the input and output files are not regular files, the checks for reduction in size and file overwriting are not performed, the
input file is not removed, and the attributes of the input file are not retained.
The options are as follows:
-b Specify the bits code limit (see below).
-c Compressed or uncompressed output is written to the standard output. No files are modified.
-f Force compression of file, even if it is not actually reduced in size. Additionally, files are overwritten without prompting for
confirmation.
-v Print the percentage reduction of each file.
The compress utility uses a modified Lempel-Ziv algorithm. Common substrings in the file are first replaced by 9-bit codes 257 and up. When
code 512 is reached, the algorithm switches to 10-bit codes and continues to use more bits until the limit specified by the -b flag is
reached (the default is 16). Bits must be between 9 and 16.
After the bits limit is reached, compress periodically checks the compression ratio. If it is increasing, compress continues to use the
existing code dictionary. However, if the compression ratio decreases, compress discards the table of substrings and rebuilds it from
scratch. This allows the algorithm to adapt to the next "block" of the file.
The -b flag is omitted for uncompress since the bits parameter specified during compression is encoded within the output, along with a magic
number to ensure that neither decompression of random data nor recompression of compressed data is attempted.
The amount of compression obtained depends on the size of the input, the number of bits per code, and the distribution of common substrings.
Typically, text such as source code or English is reduced by 50-60%. Compression is generally much better than that achieved by Huffman cod-
ing (as used in the historical command pack), or adaptive Huffman coding (as used in the historical command compact), and takes less time to
compute.
DIAGNOSTICS
The compress and uncompress utilities exit 0 on success, and >0 if an error occurs.
The compress utility exits 2 if attempting to compress the file would not reduce its size and the -f option was not specified.
SEE ALSO
gunzip(1), gzexe(1), gzip(1), zcat(1), zmore(1), znew(1)
Welch, Terry A., "A Technique for High Performance Data Compression", IEEE Computer, 17:6, pp. 8-19, June, 1984.
STANDARDS
The compress and uncompress utilities conform to IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
The compress command appeared in 4.3BSD.
BSD
May 17, 2002 BSD