07-13-2012
This is the reason you need to use a third-party brute-forcing utility like expect to kludge plaintext passwords into things: It's a subtle message, writ in mile-high flashing neon, that doing so is an extremely bad idea. As you've independently discovered.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Does anybody know how to change the password on multiple servers with a script. I have 300 Sun boxes and the password expiry is set to 30 days. Im in a process to build a script using expect. Need a help from an expert who has already done it.
Regards,
Vinod (1 Reply)
Discussion started by: chellam
1 Replies
2. Shell Programming and Scripting
Hi,
I am writing a UNIX .ksh script and need to send the login password of the login id that is executing the script to a command that I am executing in the script. I don't want that password to be seen by anyone except whoever is executing the script.
Does anyone know how I can accomplish... (6 Replies)
Discussion started by: samd
6 Replies
3. Shell Programming and Scripting
Could someone please help me...I have an expect script. There's a need for a log in during the script and a password is required...right now the password is just a variable in the expect script...what would be the best way to put that in an encrypted flat file and have the expect script pull the... (2 Replies)
Discussion started by: cubs0729
2 Replies
4. UNIX for Advanced & Expert Users
Hello folks
I have a conf file ,say 'pass.conf' ,which is storing ascii password : PASS1111.
I need to encrypt this password once and store it in a file.
I ,then need to write a script which would read this encrypted password and decrypts it.The o/p o this script shud be this decrypted... (8 Replies)
Discussion started by: ak835
8 Replies
5. Shell Programming and Scripting
Dear folks,
The title of my thread says mostly all of what I want to do. Basically I want to auto-ssh to a remote host, and run a program on it (VLC is just an example). I wrote a script which calls xterm and then runs expect on it. The code is as follow
#!/bin/bash
export PASS="xxxxxxx"... (22 Replies)
Discussion started by: dukevn
22 Replies
6. Shell Programming and Scripting
Hi
I have following problem Im writing a script (in bash ) , where need to be written login & passwd for databas client .
Its need to in following form login passwd@dbhostname .
The problem is so anybody can read it so the passwd & login are visible and thats not very safety .
Can... (8 Replies)
Discussion started by: kvok
8 Replies
7. Shell Programming and Scripting
All,
I am trying to use expect to send SFTP password because I am unable to share a key with the vendor.
They gave me a password that uses some symbols in it like $ and !
When i try to use the send command in expect it thinks the $ is a variable.
Is there anyway to have it send the... (2 Replies)
Discussion started by: markdjones82
2 Replies
8. Shell Programming and Scripting
Dear All,
I have a requirement where I have to SFTP or SCP a file in a batch script. Unfortunately, the destination server setup is such that it doesn't allow for shell command line login. So, I am not able to set up SSH keys. My source server is having issues with Expect. So, unable to use... (5 Replies)
Discussion started by: ss112233
5 Replies
9. Shell Programming and Scripting
I have a script that does an SSH into a remote node. It should expect the prompt and send the password.
#!/usr/bin/expect
set user ;
set pass ;
spawn ssh $user@E-Internal
expect {
-re "RSA key fingerprint" {send "yes\r"}
timeout... (1 Reply)
Discussion started by: Junaid Subhani
1 Replies
10. Shell Programming and Scripting
I am writing a shell script for sql loader (just copy part of the code) :
For security reason, I have to put the below loginName and password into another separate file instead of in the same file of this script.
Anyone can give me a hand. Thanks.
Shell Script :... (12 Replies)
Discussion started by: Jaewong
12 Replies
LEARN ABOUT FREEBSD
badsect
BADSECT(8) BSD System Manager's Manual BADSECT(8)
NAME
badsect -- create files to contain bad sectors
SYNOPSIS
badsect bbdir sector ...
DESCRIPTION
The badsect utility makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which pro-
vides a forwarding table for bad sectors to the driver. If a driver supports the bad blocking standard it is much preferable to use that
method to isolate bad blocks, since the bad block forwarding makes the pack appear perfect, and such packs can then be copied with dd(1).
The technique used by this program is also less general than bad block forwarding, as badsect cannot make amends for bad blocks in the i-list
of file systems or in swap areas.
On some disks, adding a sector which is suddenly bad to the bad sector table currently requires the running of the standard DEC formatter.
Thus to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard badsect may be used to good
effect.
The badsect utility is used on a quiet file system in the following way: First mount the file system, and change to its root directory. Make
a directory BAD there. Run badsect giving as argument the BAD directory followed by all the bad sectors you wish to add. (The sector num-
bers must be relative to the beginning of the file system, but this is not hard as the system reports relative sector numbers in its console
error messages.) Then change back to the root directory, unmount the file system and run fsck(8) on the file system. The bad sectors should
show up in two files or in the bad sector files and the free list. Have fsck(8) remove files containing the offending bad sectors, but do
not have it remove the BAD/nnnnn files. This will leave the bad sectors in only the BAD files.
The badsect utility works by giving the specified sector numbers in a mknod(2) system call, creating an illegal file whose first block
address is the block containing bad sector and whose name is the bad sector number. When it is discovered by fsck(8) it will ask ``HOLD BAD
BLOCK ?''. A positive response will cause fsck(8) to convert the inode to a regular file containing the bad block.
DIAGNOSTICS
The badsect utility refuses to attach a block that resides in a critical area or is out of range of the file system. A warning is issued if
the block is already in use.
SEE ALSO
fsck(8)
HISTORY
The badsect utility appeared in 4.1BSD.
BUGS
If more than one sector which comprise a file system fragment are bad, you should specify only one of them to badsect, as the blocks in the
bad sector files actually cover all the sectors in a file system fragment.
BSD
June 5, 1993 BSD