Sponsored Content
Top Forums UNIX for Dummies Questions & Answers UNIX Filename length restrictions? Post 23654 by xmeh on Wednesday 26th of June 2002 04:13:40 PM
Old 06-26-2002
UNIX Filename length restrictions?

Can anyone help me out with information on the filename length restrictions in UNIX? Thanks!
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

is LS a fixed length? I want to use cut -c#-# to isolate filename.

-rw-r--r-- 1 fxpbftp fusion 368 Jun 10 08:34 FX_1.11840235236594E12.111234236809956 If I have a long list of files that look like this (they al begni with FX_1.#######.####) Sometimes, there may be less numbers or more in the filename, that varies. I wish to isolate just the... (8 Replies)
Discussion started by: yongho
8 Replies

2. UNIX for Dummies Questions & Answers

Length of a Unix filepath max length

Hi Guys, Could anyone shed some light on the length of a Unix filepath max length pls ? thanks ! Wilson (3 Replies)
Discussion started by: wilsontan
3 Replies

3. Shell Programming and Scripting

Join two fixed length Files in Unix

Hi, Can we join two fixed length files in Unix using JOIN command? Is there any other command to accomplish the same? Thanks, G.Harikrishnan (6 Replies)
Discussion started by: gharikrishnan
6 Replies

4. Shell Programming and Scripting

User restrictions

Hi, I am setting up a new Suse server and I'm very happy with it :). So far Apache2, SVN, PHP5 and MySQL are up and running. Now I want to create and delete users (for coders for our projects) but they aren't allowed to do anything so there must be some restrictions. I want access restriction so... (0 Replies)
Discussion started by: kever
0 Replies

5. UNIX for Dummies Questions & Answers

User restrictions

Hi, I am setting up a new Suse server and I'm very happy with it . So far Apache2, SVN, PHP5 and MySQL are up and running. Now I want to create and delete users (for coders for our projects) but they aren't allowed to do anything so there must be some restrictions. I want access restriction so... (1 Reply)
Discussion started by: kever
1 Replies

6. Red Hat

Account restrictions

Lets say for example I want to restrict a users access, for example if they FTP in I want to lock them down to a certain directory. What is the best way of doing this? I'm planning to implement LDAP accounts, so I'd need this to be done automatically. Just not sure how I would go about this task. (3 Replies)
Discussion started by: Printf
3 Replies

7. Solaris

While copying files from windows to Solaris5.8 with filezilla length of the filename changed

Hello I am copying a tar from windows7 to Solaris with filezilla i could see, some characters in the name of the file get deleted. I could see only substring of the filename eg: original filename :abcdefghijklmnopqrstu.h i can see like abcdefghijklm solution to this problem is highly... (2 Replies)
Discussion started by: Revathi R
2 Replies
DGST(1) 							      OpenSSL								   DGST(1)

NAME
dgst, md5, md4, md2, sha1, sha, mdc2, ripemd160 - message digests SYNOPSIS
openssl dgst [-md5|-md4|-md2|-sha1|-sha|-mdc2|-ripemd160|-dss1] [-c] [-d] [-hex] [-binary] [-out filename] [-sign filename] [-keyform arg] [-passin arg] [-verify filename] [-prverify filename] [-signature filename] [-hmac key] [file...] [md5|md4|md2|sha1|sha|mdc2|ripemd160] [-c] [-d] [file...] DESCRIPTION
The digest functions output the message digest of a supplied file or files in hexadecimal form. They can also be used for digital signing and verification. OPTIONS
-c print out the digest in two digit groups separated by colons, only relevant if hex format output is used. -d print out BIO debugging information. -hex digest is to be output as a hex dump. This is the default case for a "normal" digest as opposed to a digital signature. -binary output the digest or signature in binary form. -out filename filename to output to, or standard output by default. -sign filename digitally sign the digest using the private key in "filename". -keyform arg Specifies the key format to sign digest with. Only PEM and ENGINE formats are supported by the dgst command. -engine id Use engine id for operations (including private key storage). This engine is not used as source for digest algorithms, unless it is also specified in the configuration file. -sigopt nm:v Pass options to the signature algorithm during sign or verify operations. Names and values of these options are algorithm-specific. -passin arg the private key password source. For more information about the format of arg see the PASS PHRASE ARGUMENTS section in openssl(1). -verify filename verify the signature using the the public key in "filename". The output is either "Verification OK" or "Verification Failure". -prverify filename verify the signature using the the private key in "filename". -signature filename the actual signature to verify. -hmac key create a hashed MAC using "key". -mac alg create MAC (keyed Message Authentication Code). The most popular MAC algorithm is HMAC (hash-based MAC), but there are other MAC algorithms which are not based on hash, for instance gost-mac algorithm, supported by ccgost engine. MAC keys and other options should be set via -macopt parameter. -macopt nm:v Passes options to MAC algorithm, specified by -mac key. Following options are supported by both by HMAC and gost-mac: key:string Specifies MAC key as alphnumeric string (use if key contain printable characters only). String length must conform to any restrictions of the MAC algorithm for example exactly 32 chars for gost-mac. hexkey:string Specifies MAC key in hexadecimal form (two hex digits per byte). Key length must conform to any restrictions of the MAC algorithm for example exactly 32 chars for gost-mac. -rand file(s) a file or files containing random data used to seed the random number generator, or an EGD socket (see RAND_egd(3)). Multiple files can be specified separated by a OS-dependent character. The separator is ; for MS-Windows, , for OpenVMS, and : for all others. file... file or files to digest. If no files are specified then standard input is used. NOTES
The digest of choice for all new applications is SHA1. Other digests are however still widely used. If you wish to sign or verify data using the DSA algorithm then the dss1 digest must be used. A source of random numbers is required for certain signing algorithms, in particular DSA. The signing and verify options should only be used if a single file is being signed or verified. 1.0.1e 2013-02-11 DGST(1)
All times are GMT -4. The time now is 10:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy