Sponsored Content
Top Forums Shell Programming and Scripting To find the publisher of file Post 302414285 by bakunin on Monday 19th of April 2010 06:12:48 PM
Old 04-19-2010
Quote:
Originally Posted by ssachins
Is there any way to find out who (from which server) is publishing the file?
Use "ls -l <filename>" to find out which user/group the file belongs to. Then try the following:

Have a look in the crontab of this user and the root user, maybe the file is not "pushed" to the server, but "pulled". ("su" to the user and issue "crontab -l").

If you are using ssh/scp to connect between servers have a look in the users "authorized_keys" file (usually located in "~/.ssh", depending on ssh-configuration) and investigate the user/host combinations mentioned there. Check the crontabs of these users on the remote hosts too.

Set up "tcpdump" (read the manpage carefully, it can produce awful lots of output) to trace the incoming connection sending the file to its originating host, then investigate on this remote host. Start with the time around the timestamp of the file, probably its being sent every day at the same time.

I hope this helps.

bakunin
 

We Also Found This Discussion For You

1. Solaris

Solaris 11 - custom publisher IPS

Hi all, we are starting to build some basic infrastructure for using solaris 11. I have built an IPS of solaris packages from the DVD images. what I want to do next is create a repository of custom packages. so in that case I want a publisher of "my-company-name" and not solaris. can... (1 Reply)
Discussion started by: robsonde
1 Replies
ssh-keysign(1M) 														   ssh-keysign(1M)

NAME
ssh-keysign - ssh helper program for host-based authentication SYNOPSIS
ssh-keysign ssh-keysign is used by ssh(1) to access the local host keys and generate the digital signature required during host-based authentication with SSH protocol version 2. This signature is of data that includes, among other items, the name of the client host and the name of the client user. ssh-keysign is disabled by default and can be enabled only in the global client configuration file /etc/ssh/ssh_config by setting Host- basedAuthentication to yes. ssh-keysign is not intended to be invoked by the user, but from ssh. See ssh(1) and sshd(1M) for more information about host-based authen- tication. /etc/ssh/ssh_config Controls whether ssh-keysign is enabled. /etc/ssh/ssh_host_dsa_key /etc/ssh/ssh_host_rsa_key These files contain the private parts of the host keys used to generate the digital signature. They should be owned by root, readable only by root, and not accessible to others. Because they are readable only by root, ssh-keysign must be set-uid root if host-based authentication is used. ssh-keysign will not sign host-based authentication data under the following conditions: o If the HostbasedAuthentication client configuration parameter is not set to yes in /etc/ssh/ssh_config. This setting cannot be overri- den in users' ~/.ssh/ssh_config files. o If the client hostname and username in /etc/ssh/ssh_config do not match the canonical hostname of the client where ssh-keysign is invoked and the name of the user invoking ssh-keysign. In spite of ssh-keysign's restrictions on the contents of the host-based authentication data, there remains the ability of users to use it as an avenue for obtaining the client's private host keys. For this reason host-based authentication is turned off by default. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsshu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ ssh(1), sshd(1M), ssh_config(4), attributes(5) AUTHORS
Markus Friedl, markus@openbsd.org HISTORY
ssh-keysign first appeared in Ox 3.2. 9 Jun 2004 ssh-keysign(1M)
All times are GMT -4. The time now is 12:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy