09-18-2015
Thanks for the quick response.
But the configuration file(which has all EXPORT commands) not only has DB passwords, but also passwords which are required to perform file SCP's.
For DB's, passwords can be saved in Oracle wallet, but what about the other passwords?
Please help.
Thanks.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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)
Discussion started by: tabourje
2 Replies
2. UNIX for Dummies Questions & Answers
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)
Discussion started by: ajphaj
3 Replies
3. UNIX for Dummies Questions & Answers
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)
Discussion started by: chris2051
1 Replies
4. UNIX and Linux Applications
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)
Discussion started by: figaro
0 Replies
5. UNIX for Dummies Questions & Answers
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)
Discussion started by: khestoi
1 Replies
6. Solaris
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)
Discussion started by: presul
2 Replies
7. Solaris
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)
Discussion started by: fpraile
5 Replies
8. Shell Programming and Scripting
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)
Discussion started by: ptappeta
1 Replies
10. Solaris
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 DEBIAN
tightvncpasswd
vncpasswd(1) TightVNC vncpasswd(1)
NAME
vncpasswd - set passwords for VNC server
SYNOPSIS
vncpasswd [file]
vncpasswd -t
vncpasswd -f
DESCRIPTION
The vncpasswd utility should be used to create and change passwords for the TightVNC server authentication. Xvnc uses such passwords when
started with the -rfbauth command-line option (or when started from the vncserver script).
vncpasswd allows to enter either one or two passwords. The first password is the primary one, the second password can be used for view-only
authentication. Xvnc will restrict mouse and keyboard input from clients who authenticated with the view-only password. The vncpasswd util-
ity asks interactively if it should set the second password.
The password file name defaults to $HOME/.vnc/passwd unless the -t command-line option was used (see the OPTIONS section below). The
$HOME/.vnc/ directory will be created if it does not exist.
Each password has to be longer than five characters (unless the -f command-line option was used, see its description below). Only the
first eight characters are significant. If the primary password is too short, the program will abort. If the view-only password is too
short, then only the primary password will be saved.
Unless a file name was provided in the command-line explicitly, this utility may perform certain sanity checks to prevent writing a pass-
word file into some hazardous place.
If at least one password was saved successfully, vncpasswd will exit with status code 0. Otherwise the returned status code will be set to
1.
OPTIONS
-t Write passwords into /tmp/$USER-vnc/passwd, creating the /tmp/$USER-vnc/ directory if it does not exist, and checking the permis-
sions on that directory (the mode must be 700). This option can help to improve security when your home partition may be shared via
network (e.g. when using NFS).
-f Filter mode. Read plain-text passwords from stdin, write encrypted versions to stdout. One or two passwords (full-control and view-
only) can be supplied in the input stream, newline terminates a password. Note that in the filter mode, short or even empty pass-
words will be silently accepted.
SEE ALSO
vncserver(1), Xvnc(1), vncviewer(1), vncconnect(1)
AUTHORS
Original VNC was developed in AT&T Laboratories Cambridge. TightVNC additions were implemented by Constantin Kaplinsky. Many other people
participated in development, testing and support.
Man page authors:
Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>,
Tim Waugh <twaugh@redhat.com>,
Constantin Kaplinsky <const@tightvnc.com>
August 2006 vncpasswd(1)