11-04-2019
10 More Discussions You Might Find Interesting
1. AIX
hello
I want to connect from server1 to server2 (Aix 5.3) with ssh, without password prompt.
So i define a ssh-key
On server1:
ssh-keygen -b 1024 -f identity -P '' -t dsa
scp identity.pub toto@server2:/tmp/identity-.pub
On server 2:
cat identity-.pub >> .ssh/authorized_keys
chmod 400... (2 Replies)
Discussion started by: pascalbout
2 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
I have got a Solaris machine and I have several user account setup up with the .ssh and authorized_keys file in their home directories.
I have check all the permission and ownership and they are all indentical and belongs to the user ID and group respectively. However one of the... (3 Replies)
Discussion started by: stancwong
3 Replies
3. Cybersecurity
Hi,
When logging in using SSH access (to a remotely
hosted account), I received a prompt to accept
a server's key fingerprint. Wrote that string
of code down for comparision.
Already emailed my host for their listing of the
string of code for the server's key fingerprint
(for comparison,... (1 Reply)
Discussion started by: Texan
1 Replies
4. UNIX for Advanced & Expert Users
When should one have to generate a public key on a Server when the public key is already created and used by other clients?
Thanks,
Rahul. (6 Replies)
Discussion started by: rahulrathod
6 Replies
5. UNIX for Advanced & Expert Users
Hi all,
I have a sshkey which I use to connect from my unix box to a linux box without any issue......
however I downloaded this same key to my laptop and tried to connect to the same linux box but it failed.....
As my laptop is running MS Vista I guessing I going have to convert it ...... (1 Reply)
Discussion started by: Zak
1 Replies
6. Cybersecurity
Hello here is what I've seen
inside some public pgp keys.
gAIAAAAAAAkBAAAAAAoAAAAFAAoArwFI/gkAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA... (1 Reply)
Discussion started by: morten44
1 Replies
7. Shell Programming and Scripting
Hi,
I want to use ssh to add a register key on remote ssh server. Since there are space characters in my register key string, it always failed. If there is no space characters in the string, it worked fine. The following is what I have tried. It seems that "ssh" command doesn't care about double... (9 Replies)
Discussion started by: leaftree
9 Replies
8. Solaris
Hi, I've used the following way to set ssh public key authentication and it is working fine on Solaris 10, RedHat Linux and SuSE Linux servers without any problem. But I got error 'Server refused our key' on Solaris 8 system. Solaris 8 uses SSH2 too. Why? Please help. Thanks.
... (1 Reply)
Discussion started by: aixlover
1 Replies
9. UNIX for Dummies Questions & Answers
Hello,
i was talking to an expert in my work and i requested him to import my ssh public-key in the ~/.ssh/authorized_keys on a remote host.
but he told me that he only import OS groupkey(not OS user key). so he asked me to give him the output of (id -a)
user1@hostname$ id -a... (3 Replies)
Discussion started by: amr.emam
3 Replies
10. AIX
Hello
I have AIX server as a source server and destination is Linux server. I have configured the ssh key as below....
generated rsa key on aix with userA and copied the public key to
on linux server in userB/.ssh/authorized_keys
but when i try ssh userB@linux server its again asks me for... (4 Replies)
Discussion started by: powerAIX
4 Replies
SFILL(1) General Commands Manual SFILL(1)
NAME
sfill - secure free disk and inode space wiper (secure_deletion toolkit)
SYNOPSIS
sfill [-f] [-i] [-I] [-l] [-l] [-v] [-z] directory/mountpoint
DESCRIPTION
sfill is designed to delete data which lies on available diskspace on mediums in a secure manner which can not be recovered by thiefs, law
enforcement or other threats. The wipe algorythm is based on the paper "Secure Deletion of Data from Magnetic and Solid-State Memory" pre-
sented at the 6th Usenix Security Symposium by Peter Gutmann, one of the leading civilian cryptographers.
The secure data deletion process of sfill goes like this:
* 1 pass with 0xff
* 5 random passes. /dev/urandom is used for a secure RNG if available.
* 27 passes with special values defined by Peter Gutmann.
* 5 random passes. /dev/urandom is used for a secure RNG if available.
afterwards as many temporary files as possible are generated to wipe the free inode space. After no more temporary files can be created,
they are removed and sfill is finnished.
COMMANDLINE OPTIONS
-f fast (and insecure mode): no /dev/urandom, no synchronize mode.
-i wipe only free inode space, not free disk space
-I wipe only free disk space, not free inode space
-l lessens the security. Only two passes are written: one mode with 0xff and a final mode with random values.
-l -l for a second time lessons the security even more: only one random pass is written.
-v verbose mode
-z wipes the last write with zeros instead of random data
directory/mountpoint this is the location of the file created in your filesystem. It should lie on the partition you want to write.
LIMITATIONS
FILESYSTEM INTELLIGENCE
Most filesystems (ext2, ffs, etc.) have several features included to enhance performance, which will result in that sfill might not
receive all available free space. Sad but true. Nothing can be done about that ...
NFS Beware of NFS. You can't ensure you really completely wiped your data from the remote disks. (especially because of caching)
Raid Raid Systems use stripped disks and have got large caches. It's hard to wipe them.
swap Some of your data might have a copy in your swapspace. sswap is available for this task.
BUGS
No bugs. There was never a bug in the secure_deletion package (in contrast to my other tools, whew, good luck ;-) Send me any that you
find. Patches are nice too :)
AUTHOR
van Hauser / THC <vh@thc.org>
DISTRIBUTION
The newest version of the secure_deletion package can be obtained from http://www.thc.org
sfill and the secure_deletion package is (C) 1997-2003 by van Hauser / THC (vh@thc.org)
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by
the Free Software Foundation; Version 2.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER-
CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
SEE ALSO
srm (1), sswap (1), sdmem (1)
SFILL(1)