Obfuscating sensitive information in EXPORT commands
Hi.
Been a while since I posted last time, and I hope you all are doing well.
I'm automating a Data Integration process end to end using Shell programming over Linux 2.6x platform, and I'm accessible to Korn and Bash shells with provision to use Perl 5.1 also.
What we do as a common practice to make all global values available to all the scripts is to enlist all EXPORT commands for these in a single flat file(name of the file is global_variable.cfg) and invoke this file at the start of each script.
The structure of this file looks something like below:
Since this flat file is accessible to all users configured to the system, how can I obfuscate only the sensitive details like database passwords of this file from any unintended user may not be able to track them even if he accesses the file? Also, how can I hide/obfuscate the database passwords from the sql prompts whilst the SQL queries are getting executed?
Any help is highly appreciated.
Please revert for further clarifications.
Does anyone know of any tool(s) to obfuscate shell scripts for intellectual property protection purposes?
My searches turned up one such tool for Perl but not for shell scripts. Thanks. (2 Replies)
Hello users,
I have a question ?
I was just wondering whether the hostname on unix systems are case sensitive.
For example in the system which I work.
ping TestHost and ping testhost gives me the same output i.e I get the reply from the remote host
Is this applicable for all... (3 Replies)
I am attempting to write a shell script that runs a program which generates data and then runs another program to plot the data. The problem is that I need the plotting to take place in a different terminal window that stays open after the plotting has finished. I have experimented 'xterm -e '... (1 Reply)
I would like to set the root password for mysql databases installed on various machines connected within a network. These machines receive their mysql installation via a script that pulls the installation files from the server and starts installing. During installation I would also like to set the... (0 Replies)
Is there a way for me to take a parameter then store it in a variable and use its value as non case sensitive?
Ex.
Lets say i have a parameter which contains "Hey".
Then im gonna store it to GR using GR=$1.
CL=/install/$GR.g
How can i make GR non case sensitive so that the... (1 Reply)
Hi
I'm trying to understand variable scopes in solaris10.
It is said that to display env variables we use 3 commands :
- env
- set
- export
What is the difference between them ?
thx for help.
---------- Post updated at 11:00 AM ---------- Previous update was at 10:50 AM ----------
... (2 Replies)
Hi all,
I am writing this post in order to share my experience with the SUN nxge ethernet interfaces and try to see if some of you managed to solve similar issues than the ones we experienced here with T5520 running Solaris 10.
First, we noticed that it was somehow difficult to have those... (5 Replies)
Hi All,
select app from the menu:
ABC
DEF
GHI
JKL
ALL # ALL will select all the apps in the menu
echo "Enter your option"
read option;
if
then
<execute the below command>
elif # option is the 1 selection from menu...not ALL
<execute the below command>
else (14 Replies)
Discussion started by: Devaraj A
14 Replies
9. Post Here to Contact Site Administrators and Moderators
Hi
Kindly remove the following from the post . These are confidential info posted by mistake
https://www.unix.com/shell-programming-and-scripting/201037-perl-while-loop-each.html
please remove the comments section which is first 16 lines in the perl script .
Also please remove the ... (1 Reply)
I need to know what are the commands in Solaris to retrieve the below information about the hardware platform.
1. Chipset information (information about various hardware controller cards on the mother boards, system BIOS versions, PCI firmware version etc..)
2. Serial number of the work... (2 Replies)
Discussion started by: rajujayanthy
2 Replies
LEARN ABOUT POSIX
export
EXPORT(1P) POSIX Programmer's Manual EXPORT(1P)PROLOG
This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the correspond-
ing Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux.
NAME
export -- set the export attribute for variables
SYNOPSIS
export name[=word]...
export -p
DESCRIPTION
The shell shall give the export attribute to the variables corresponding to the specified names, which shall cause them to be in the envi-
ronment of subsequently executed commands. If the name of a variable is followed by =word, then the value of that variable shall be set to
word.
The export special built-in shall support the Base Definitions volume of POSIX.1-2008, Section 12.2, Utility Syntax Guidelines.
When -p is specified, export shall write to the standard output the names and values of all exported variables, in the following format:
"export %s=%s
", <name>, <value>
if name is set, and:
"export %s
", <name>
if name is unset.
The shell shall format the output, including the proper use of quoting, so that it is suitable for reinput to the shell as commands that
achieve the same exporting results, except:
1. Read-only variables with values cannot be reset.
2. Variables that were unset at the time they were output need not be reset to the unset state if a value is assigned to the variable
between the time the state was saved and the time at which the saved output is reinput to the shell.
When no arguments are given, the results are unspecified. If a variable assignment precedes the command name of export but that variable is
not also listed as an operand of export, then that variable shall be set in the current shell execution environment after the completion of
the export command, but it is unspecified whether that variable is marked for export.
OPTIONS
See the DESCRIPTION.
OPERANDS
See the DESCRIPTION.
STDIN
Not used.
INPUT FILES
None.
ENVIRONMENT VARIABLES
None.
ASYNCHRONOUS EVENTS
Default.
STDOUT
See the DESCRIPTION.
STDERR S
The standard error shall be used only for diagnostic messages.
OUTPUT FILES
None.
EXTENDED DESCRIPTION
None.
EXIT STATUS
Zero.
CONSEQUENCES OF ERRORS
Default.
The following sections are informative.
APPLICATION USAGE
None.
EXAMPLES
Export PWD and HOME variables:
export PWD HOME
Set and export the PATH variable:
export PATH=/local/bin:$PATH
Save and restore all exported variables:
export -p > temp-file
unset a lot of variables
... processing
. temp-file
RATIONALE
Some historical shells use the no-argument case as the functional equivalent of what is required here with -p. This feature was left
unspecified because it is not historical practice in all shells, and some scripts may rely on the now-unspecified results on their imple-
mentations. Attempts to specify the -p output as the default case were unsuccessful in achieving consensus. The -p option was added to
allow portable access to the values that can be saved and then later restored using; for example, a dot script.
FUTURE DIRECTIONS
None.
SEE ALSO
Section 2.14, Special Built-In Utilities
The Base Definitions volume of POSIX.1-2008, Section 12.2, Utility Syntax Guidelines
COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2013 Edition, Standard for Information Technol-
ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, Copyright (C) 2013 by the Institute of
Electrical and Electronics Engineers, Inc and The Open Group. (This is POSIX.1-2008 with the 2013 Technical Corrigendum 1 applied.) In the
event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Stan-
dard is the referee document. The original Standard can be obtained online at http://www.unix.org/online.html .
Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source
files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .
IEEE /The Open Group 2013 EXPORT(1P)