Sponsored Content
Full Discussion: openSSL command help
Top Forums Shell Programming and Scripting openSSL command help Post 302656185 by shade917 on Thursday 14th of June 2012 10:35:57 AM
Old 06-14-2012
The output of the code would be something like this:

Code:
blah blah
blah blah

Certificate chain
 0 s:/C=US/ST=New Jersey/L=Passaic/O=Super Secret Company/OU=Webserver/CN=blah blah blah
blah blah
blah blah
....

The bold is the part i need
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

openssl help

I ungraded my openssl on sun solaris 8 from openssl 0.9.6c to openssl 0.9.6g the ungrade went fine but when I tried to ssh in to server, I received the following error message "ld.so.1: ./sshd: fatal: relocation error: file /usr/local/ssl/lib/libcrypto.so.0.9.6: symbol main: referenced symbol... (2 Replies)
Discussion started by: hassan2
2 Replies

2. UNIX for Advanced & Expert Users

Using openssl

All, I am new to openssl and I have not been able to figure out exactly how to use it. What I need to do is to create a shell script which FTPS's (SFTP is not allowed on my project) a file to a mainframe. The mainframe will not initiate a session with my server. Question. Are the packages... (7 Replies)
Discussion started by: MichaelInDC
7 Replies

3. Solaris

Openssl 0.9.8r

Hi Peeps, Having trouble compiling openssl 0.9.8r on Solaris 10 x86. The make test fails when running the shatests (segmentation faults). There is a PROBLEM file that references a file called values.c. Anyone know whereabouts in the source tree you put this file as the file doesn't tell you... (2 Replies)
Discussion started by: callmebob
2 Replies

4. Solaris

Version of OpenSSL being used

Hello I'm relatively new to technologies like Apache & ssl but have some years experience with Unix. My question concerns the version of OpenSSL which is genuinely being used on our server & how is that set. The server is running Solaris 10. I'll show output from various commands: ... (1 Reply)
Discussion started by: CHoggarth
1 Replies

5. Red Hat

Openssl vulnerabilities

Hi there, The following openssl package are installed on the machine (openssl-1.0.0-27.el6_4.2.x86_64). It isn't the last version but I need to known if this content Vulnerabilities... How to check that on RedHat? Could you please tell me how to find this information?? Thankx (3 Replies)
Discussion started by: hiero_nymus
3 Replies

6. Cybersecurity

OpenSSL

I just started playing around with Unix's OpenSSL utility. I can't seem to get the hang of it, and the man page isn't helping much. I wanted to experiment with file encryption, so I created a dummy text file with one line of text and tried to encrypt it using DES. I used the following command: ... (2 Replies)
Discussion started by: Ultrix
2 Replies

7. Shell Programming and Scripting

Shell differences for openssl command output

The following works in bash (/bin/bash): echo "U2FsdGVkX198UexvhHEtfC7iLbT3awAfla77fvSjZQJ0LC4GmDMeLOghPWXpyy6e" | openssl aes-128-cbc -a -d -salt -pass file:<( echo -n "toy" ) Fri Sep 15 15:20:01 PDT 2017 But fails when run in sh (/bin/sh): echo... (1 Reply)
Discussion started by: SkySmart
1 Replies

8. UNIX for Beginners Questions & Answers

How to check ssl certificate expiry date using openssl command?

hi how to check ssl certificate expiry date using openssl command try below code it is not working, any help echo q | openssl s_client -connect akamai.com:443 | openssl x509 -noout -enddate socket: Bad file descriptor connect:errno=9 unable to load certificate... (0 Replies)
Discussion started by: raghur77
0 Replies
radiusd.conf(5) 					   FreeRADIUS configuration file					   radiusd.conf(5)

NAME
radiusd.conf - configuration file for the FreeRADIUS server DESCRIPTION
The radiusd.conf file resides in the radius database directory, by default /etc/raddb. It defines the global configuration for the FreeRA- DIUS RADIUS server. CONTENTS
There are a large number of configuration parameters for the server. Most are documented in the file itself as comments. This page docu- ments only the format of the file. Please read the radiusd.conf file itself for more information. The configuration file parser is independent of the server configuration. This means that you can put almost anything into the configura- tion file. So long as it is properly formatted, the server will start. When the server parses the configuration file, it looks only for those configurations it understands. Extra configuration items are ignored. This "feature" can be (ab)used in certain interesting ways. FILE FORMAT
The file format is line-based, like many other Unix configuration files. Each entry in the file must be placed on a line by itself, although continuations are supported. The file consists of configuration items (variable = value pairs), sections, and comments. Variables Variables can be set via: name = value Single and double-quoted strings are permitted: string1 = "hello world" string2 = 'hello mom' Sections A section begins with a section name, followed on the same line by an open bracket '{'. Section may contain other sections, com- ments, or variables. Sections may be nested to any depth, limited only by available memory. A section ends with a close bracket '}', on a line by itself. section { ... } Sections can sometimes have a second name following the first one. The situations where this is legal depend on the context. See the examples and comments in the radiusd.conf file for more information. section foo { ... } Comments Any line beginning with a (#) is deemed to be a comment, and is ignored. Comments can appear after a variable or section defini- tions. # comment foo = bar # set variable 'foo' to value 'bar' section { # start of section ... } # end of section Continuations Long lines can be broken up via continuations, using '' as the last character of the line. For example, the following entry: foo = "blah blah blah" will set the value of the variable "foo" to "blah blah blah". Any CR or LF is not turned into a space, but all other whitespace is preserved in the final value. REFERENCES
The value of a variable can reference another variable. These references are evaluated when the configuration file is loaded, which means that there is no run-time cost associated with them. This feature is most useful for turning long, repeated pieces of text into short ones. Variables are referenced by ${variable_name}, as in the following examples. foo = bar # set variable 'foo' to value 'bar' who = ${foo} # sets variable 'who' to value of variable 'foo' my = "${foo} a" # sets variable 'my' to "bar a" If the variable exists in a section or subsection, it can be referenced as ${section.subsection.variable}. Forward references are not allowed. Relative references are allowed, by pre-pending the name with one or more period. blogs = ${.foo} Will set variable blogs to the value of variable foo, from the current section. blogs = ${..foo} Will set variable blogs to the value of variable foo, from the section which contains the current section. blogs = ${modules.detail.filename} Will set variable blogs to the value of variable filename, of the detail module, which is in the modules section of the configuration file. Properties of anonymous parent sections may also be referenced, currently name and instance are supported. modules { example foo { file = ${.:name} } } Will set variable file to the name of the containing section (example). modules { example foo { file = ${.:instance} } } Will set variable file to the instance name of the containing section (foo). modules { example foo { file = ${..:name} } } Will set variable file to the name of the parent of the containing section (modules). FILES
/etc/raddb/radiusd.conf SEE ALSO
radiusd(8) unlang(5) AUTHOR
Alan DeKok <aland@freeradius.org> 28 Jun 2013 radiusd.conf(5)
All times are GMT -4. The time now is 02:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy