05-14-2010
Seems to be a restriction of your Identity Management App because in a plain Unix/Linux environment it is absolutely no problem to use PKA and sudo.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
do we need root access for the remote server to ssh without a password(i.e by using id_rsa.pub method)??? (1 Reply)
Discussion started by: roshanjain2
1 Replies
2. 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
3. UNIX for Advanced & Expert Users
Hi,
I am trying to scp a file from our Unix server to the local Windows machine.I have created the key pair in Unix server using ssh-keygen command in unix.
But I am not sure where can we put the public key(generated on Unix) in Windows machine so that scp from Unix machine to Windows is... (3 Replies)
Discussion started by: dennis.jacob
3 Replies
4. Shell Programming and Scripting
I am writing a script that needs to access various servers some of which are not ssh enabled. In order to access the ssh enabled servers I am using the following command to generate the public key :
ssh-keygen -t rsa
Is there a similar command for the other servers as well.
If I try to use... (1 Reply)
Discussion started by: ravneet123
1 Replies
5. UNIX for Advanced & Expert Users
I am writing a script that needs to access various servers some of which are not ssh enabled. In order to access the ssh enabled servers I am using the following command to generate the public key :
ssh-keygen -t rsa
Is there a similar command for the other servers as well.
If I try to use... (1 Reply)
Discussion started by: ravneet123
1 Replies
6. AIX
Hi all,
I have N number of AIX hosts, where I need to login frequently and do some routine tasks (run some scripts). I need to setup ssh public/private key, so I can auto-login via a master (wrapper) script and run each script in each server.
I am trying to setup/generate ssh keys, but am... (6 Replies)
Discussion started by: haroon_a
6 Replies
7. Red Hat
Hi All;
I have an issue with password less authentication via ssh ( v2)
I have two servers Server A and Server B, following are the server details
Server A
OS - HP UX B.11.11 U 9000/800
SSH - OpenSSH_4.3p2-hpn, OpenSSL 0.9.7i 14 Oct 2005
HP-UX Secure Shell-A.04.30.000, HP-UX... (3 Replies)
Discussion started by: maverick_here
3 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
Hi,
please guide me create a public/private key using ssh-keygen, lets say I have been access to server named pngpcdb1with a userid and password ...!!! and also please explain in detail the concept of these keys and ssh as I was planning to use them in ftp related scripts..! Thanks in... (1 Reply)
Discussion started by: rahul125
1 Replies
10. UNIX for Advanced & Expert Users
My password-free ssh connection has worked in the past but has stopped working and I can't get it going again.
The files in .ssh on both source and target are set to 600:
drwx------ 2 ingres 1024 Mar 2 13:57 .
drwxr-xr-x 25 ingres 2048 Mar 29 09:38 ..
-rw------- 1 ingres ... (9 Replies)
Discussion started by: Catullus
9 Replies
LEARN ABOUT DEBIAN
app::info::handler::print
App::Info::Handler::Print(3pm) User Contributed Perl Documentation App::Info::Handler::Print(3pm)
NAME
App::Info::Handler::Print - Print App::Info event messages
SYNOPSIS
use App::Info::Category::FooApp;
use App::Info::Handler::Print;
my $stdout = App::Info::Handler::Print->new( fh => 'stdout' );
my $app = App::Info::Category::FooApp->new( on_info => $stdout );
# Or...
my $app = App::Info::Category::FooApp->new( on_error => 'stderr' );
DESCRIPTION
App::Info::Handler::Print objects handle App::Info events by printing their messages to a filehandle. This means that if you want event
messages to print to a file or to a system filehandle, you can easily do it with this class. You'll find, however, that
App::Info::Handler::Print is most effective for info and error events; unknown and prompt events are better handled by event handlers that
know how to prompt users for data. See App::Info::Handler::Prompt for an example of that functionality.
Upon loading, App::Info::Handler::Print registers itself with App::Info::Handler, setting up a couple of strings that can be passed to an
App::Info concrete subclass constructor. These strings are shortcuts that tell App::Info how to create the proper App::Info::Handler::Print
object for handling events. The registered strings are:
stdout
Prints event messages to "STDOUT".
stderr
Prints event messages to "STDERR".
See the "new()" constructor below for how to have App::Info::Handler::Print print event messages to different filehandle.
INTERFACE
Constructor
new
my $stderr_handler = App::Info::Handler::Print->new;
$stderr_handler = App::Info::Handler::Print->new( fh => 'stderr' );
my $stdout_handler = App::Info::Handler::Print->new( fh => 'stdout' );
my $fh = FileHandle->new($file);
my $fh_handler = App::Info::Handler::Print->new( fh => $fh );
Constructs a new App::Info::Handler::Print and returns it. It can take a single parameterized argument, "fh", which can be any one of the
following values:
stderr
Constructs a App::Info::Handler::Print object that prints App::Info event messages to "STDERR".
stdout
Constructs a App::Info::Handler::Print object that prints App::Info event messages to "STDOUT".
FileHandle
GLOB
Pass in a reference and App::Info::Handler::Print will assume that it's a filehandle reference that it can print to. Note that passing
in something that can't be printed to will trigger an exception when App::Info::Handler::Print tries to print to it.
If the "fh" parameter is not passed, "new()" will default to creating an App::Info::Handler::Print object that prints App::Info event
messages to "STDOUT".
handler
This method is called by App::Info to print out the message from events.
BUGS
Please send bug reports to <bug-app-info@rt.cpan.org> or file them at <http://rt.cpan.org/NoAuth/Bugs.html?Dist=App-Info>.
AUTHOR
David Wheeler <david@justatheory.com>
SEE ALSO
App::Info documents the event handling interface.
App::Info::Handler::Carp handles events by passing their messages Carp module functions.
App::Info::Handler::Prompt offers event handling more appropriate for unknown and confirm events.
App::Info::Handler describes how to implement custom App::Info event handlers.
COPYRIGHT AND LICENSE
Copyright (c) 2002-2008, David Wheeler. Some Rights Reserved.
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.10.1 2011-03-15 App::Info::Handler::Print(3pm)