12-11-2006
Given they're implementing the same algorithms(DES, etc) how different can they be? Seems like open-source-paranoia to me, the outdated notion that actively updated open source is wide-open to hackers while slower-updated closed source is invulnerable.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
First off, I apologize for making my first post here a question that has probably been asked over a billion times... however with the ever changing nature of technology, it almost seems like yesterday's answers are no longer applicable.
Basically I am looking to start up a business and am trying... (15 Replies)
Discussion started by: Verbose Bob
15 Replies
2. Solaris
Hi,
I would like to login from a Sun server running ssh:
Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f
to
ssh: SSH Secure Shell 3.0.1 on sparc-sun-solaris2.6
How can I achieve this?
Thanks a million in advance (1 Reply)
Discussion started by: newbewie
1 Replies
3. UNIX for Dummies Questions & Answers
I am using OpenSSH on my sun servers.
There is another suite of sun servers attempting to SSH into my machines.
I am running ssh -vv:
OpenSSH_4.4p1, OpenSSL 0.9.8d 28 Sep 2006
the other guy is running the sun version of ssh (i don't know what/if any differences there are between... (7 Replies)
Discussion started by: EWTGPAC
7 Replies
4. UNIX for Dummies Questions & Answers
I have a FreeBSD server on my home network. It is hooked to the router with an Ethernet cable. Both the server and the router are in the basement. The other computers in the house are upstairs, wireless. So the server's local IP address is set outside the wireless pool, and suppose it's... (1 Reply)
Discussion started by: gabi
1 Replies
5. Solaris
I set the RETRIES and DISABLETIME in /etc/default/login on 2 systems:
- 1 Solaris 9 system running Sun SSH
- 1 Solaris 9 system running Openssh 5.2 P1
I expected that after n failed logins, the login process will hang for n seconds.
It does when the attempted login is done at the console... (8 Replies)
Discussion started by: jabentay
8 Replies
6. Solaris
hi All,
We tried to establish a connection from OpenSSH3.8.1 running on Windows Box to SunSSH-1.1 running on Solaris 10. Please see the debug statements.
C:\Documents and Settings\sadmin\.ssh>ssh sadmin@10.4.3.8 -v -v -v
OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004
debug1: Reading... (2 Replies)
Discussion started by: venusunil
2 Replies
7. UNIX for Advanced & Expert Users
Hi all,
I have a Solaris 10 server with SUN_SSH_1.1 installed.
I want to restrict a user via SFTP to only be able to access one directory. I've written a little script in .profile which works perfectly for an ssh login but it appears sftp doesn't read the .profile file so it doesn't work.
... (2 Replies)
Discussion started by: Donkey25
2 Replies
8. Solaris
which should i prefer to install in my system openssh or ssh package provided by SUN by default. can i have two packages installed at the same time? (2 Replies)
Discussion started by: chidori
2 Replies
9. Red Hat
There was a security analysis run on one server which has RHEL 5.8 installed and it is showing security vulnerabilities with respect to ssh in OpenSSH with reference no CVE-2007-4752. The vulnerability solution in the security report is showing solution as below:
1) Download and apply the... (3 Replies)
Discussion started by: RHCE
3 Replies
LEARN ABOUT CENTOS
io::atomicfile
IO::AtomicFile(3) User Contributed Perl Documentation IO::AtomicFile(3)
NAME
IO::AtomicFile - write a file which is updated atomically
SYNOPSIS
use IO::AtomicFile;
### Write a temp file, and have it install itself when closed:
my $FH = IO::AtomicFile->open("bar.dat", "w");
print $FH "Hello!
";
$FH->close || die "couldn't install atomic file: $!";
### Write a temp file, but delete it before it gets installed:
my $FH = IO::AtomicFile->open("bar.dat", "w");
print $FH "Hello!
";
$FH->delete;
### Write a temp file, but neither install it nor delete it:
my $FH = IO::AtomicFile->open("bar.dat", "w");
print $FH "Hello!
";
$FH->detach;
DESCRIPTION
This module is intended for people who need to update files reliably in the face of unexpected program termination.
For example, you generally don't want to be halfway in the middle of writing /etc/passwd and have your program terminate! Even the act of
writing a single scalar to a filehandle is not atomic.
But this module gives you true atomic updates, via rename(). When you open a file /foo/bar.dat via this module, you are actually opening a
temporary file /foo/bar.dat..TMP, and writing your output there. The act of closing this file (either explicitly via close(), or
implicitly via the destruction of the object) will cause rename() to be called... therefore, from the point of view of the outside world,
the file's contents are updated in a single time quantum.
To ensure that problems do not go undetected, the "close" method done by the destructor will raise a fatal exception if the rename() fails.
The explicit close() just returns undef.
You can also decide at any point to trash the file you've been building.
AUTHOR
Primary Maintainer
David F. Skoll (dfs@roaringpenguin.com).
Original Author
Eryq (eryq@zeegee.com). President, ZeeGee Software Inc (http://www.zeegee.com).
REVISION
$Revision: 1.2 $
perl v5.16.3 2005-02-10 IO::AtomicFile(3)