home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!sun-barr!sh.wide!wnoc-tyo-news!cs.titech!kddlab!jcpltyo!ohayon
- From: ohayon@jcpltyo.JCPL.CO.JP (Tsiel Ohayon)
- Newsgroups: comp.databases.sybase
- Subject: Re: Hiding a password while dumping
- Message-ID: <93@jcpltyo.JCPL.CO.JP>
- Date: 9 Nov 92 03:43:48 GMT
- References: <1688@anagld.analytics.com>
- Organization: James Capel Pacific Limited, Tokyo Japan
- Lines: 27
-
- In article <1688@anagld.analytics.com> rcsmith@anagld.analytics.com (Ray Smith) writes:
-
- [RS] FORWARDED MESSAGE
-
- [RS] I'm trying to write a shell script executed through cron to perform a
- [RS] Sybase dump. The problem is as follows:
- [RS] The Sybase dump command is a Transact/Sql command. Therefore, it must be
- [RS] invoked using the isql command.
- [RS] The isql command normally prompts the user for their Sybase userid and
- [RS] passwd. However, this can be overridden by entering the -U and -P flags
- [RS] when invoking isql.
- [RS] The problem: The -P flag take the user's unencrypted passwd as argument.
- [RS] This means that while the backup is running, any user can see/learn the
- [RS] passwd because it is displayed clearly in the output of the ps command.
- [RS] The question: Does anyone have any ideas how I can prevent the passwd from
- [RS] being displayed? I'd like to run the backup as a batch process using cron
- [RS] (the data can fit on one tape), but don't want to compromise the passwd.
-
- I used a C program to do that. If you are interested, I can show how to do
- it.
-
- Cheers.
- --
- ----8<--------------------------------------------------------------->8------
- Tsiel:ohayon@jcpl.co.jp | If you do not recieve this E-mail, please let me
- Employer may not have same | know as soon as possible, if possible.
- opinions, if any ! | Two percent of zero is almost nothing.
-