Sponsored Content
Operating Systems Linux Red Hat Problem Openvas-setup in CentOs 6.7 ! Post 302973208 by Scrutinizer on Monday 16th of May 2016 03:27:28 AM
Old 05-16-2016
Have you tested manually? Can you reach the server you are rsync'ing with through ssh?.
Is the firewall allowing this connection?
Have you tried to configure it using wget (https) instead of rsync (ssh)? Perhaps that protocol is allowed?


---
@ravindersingh:
/etc/hosts.deny is for incoming connections to services on the hosts itself.
This, however, is an outbound connection from the host to a server on the Internet.
Port 873 is for legacy insecure rsync, and again for incoming connections. Nobody uses that port anymore. Nowadays rsync is typically used with ssh only, which is the default and which usually is on port 22 (but again, for incoming connections, which is not the case here).

Last edited by Scrutinizer; 05-16-2016 at 05:01 AM..
These 2 Users Gave Thanks to Scrutinizer For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

problem of networking in centos

Hello, I am using dual boot of linux, one is ubuntu and the other is one is centos. I have three NIC's and only one of them connected with cable. The thing is that when I boot from the ubuntu, it does recognize it and I am connected to the Internet. When I boot from the centos I am not... (6 Replies)
Discussion started by: programAngel
6 Replies

2. Linux

How i can setup socks 5 in CentOS?

how i can setup socks 5 in centos? (0 Replies)
Discussion started by: hesamii
0 Replies

3. IP Networking

How i can setup socks 5 in CentOS?

how i can setup socks 5 in centos? (1 Reply)
Discussion started by: hesamii
1 Replies

4. Red Hat

DNS Server Setup Centos 6.5 Issues

I am having a bit of trouble getting my CENTOS 6.5 DNS server to work correctly in our testlab environment. Lab network is 10.8.0.0/24 in which we all access from 10.7.0.0.0/24 && 10.0.0.0/24. Here are my configs: options { listen-on port 53 { 127.0.0.1; 10.8.0.19;}; #listen-on-v6 port 53 {... (2 Replies)
Discussion started by: metallica1973
2 Replies

5. Linux

Unable to access CentOS setup Network Configuration after attempting Python update

I attempted to update Python on my CentOS 5.6 VM and have encountered some issues after then. Initially yum wouldn't work, but I have resolved that. However, now I am unable to access the Network Configuration section under setup. When I do select this option I see this at the command line: ... (2 Replies)
Discussion started by: crmpicco
2 Replies

6. Cybersecurity

Not able to login Openvas after update NVT

Hello, Today, i just updated my Openvas server for latest NVT, portsname and scapdata but after that i am not able to login to my openvas instance. Below command i fired to get this done. openvas-nvt-sync openvas-certdata-sync openvas-portnames-update openvas-scapdata-sync... (0 Replies)
Discussion started by: sunnysthakur
0 Replies

7. UNIX for Beginners Questions & Answers

Problem with cluster on centos 6.5

Hallo to everyone.From sometime i have problems with my asterisk pbx on cent os which is in corosync cluster mode with resource groups.The problem is for time the cluster just swap the active one with the other and the only messages in \var\log\messages is that bond0:link status defenitly down for... (0 Replies)
Discussion started by: evolintend
0 Replies

8. UNIX for Advanced & Expert Users

Issue setup Transparent proxy and Gateway using Squid on CentOS 7

Hello, We are migrating our gateways from CentOS 6 to CentOS 7 and for setting up a transparent proxy using squid and Firewalld i am using below configuration. #Firewalld configurations firewall-cmd --permanent --zone=public --add-forward-port=port=80:proto=tcp:toport=3128:toaddr=LAN_IP... (4 Replies)
Discussion started by: sunnysthakur
4 Replies

9. Linux

Not able to setup CentOS 7 as gateway [Using squid proxy]

Hello, Did anyone setup a CentOS7 as a gateway (with squid transparent proxy). I am trying to do so but not able to setup. I setup squid , iptables (using it instead of firewalld) and all the necessary IPtables rules but nothing work. It work previously but access.log of squid not getting... (4 Replies)
Discussion started by: sunnysthakur
4 Replies
dput.cf(5)							File Formats Manual							dput.cf(5)

NAME
       dput.cf - Debian package upload tool configuration file

DESCRIPTION
       This manpage gives a brief overview of dput's configuration file and the available options in it.  dput is a tool to upload Debian packages
       to the archive.

FORMAT
       dput.cf consists of different groups of configuration options, one for each host where you want to be able to upload  packages.	Hosts  are
       defined	using  an  identifier header with a short name for the host, enclosed in square brackets.  Note that only if multiple such headers
       are encountered in the configuration, only the group following the last header is considered. This is done to avoid confusion when overrid-
       ing  a global configuration file with a user-specific one.  There's a special identifier, [DEFAULT], which holds default parameters for all
       the hosts. The defaults can be overridden by redefining them again in each host section. The available parameters are listed below:

       fqdn   This is the fully qualified domain name that will be used (can be specified as host:port for HTTP, HTTPS and FTP).

       login  Your login on the machine named before. A single asterisk * will cause the scp and rsync uploaders to not use supply  a  login  name
	      when calling to ssh, scp, and rsync.

       incoming
	      The directory that you should upload the files to.

       method The method that you want to use for uploading the files.	Currently, dput accepts the following values for method:

	      ftp    the  package  will  be  uploaded  via  ftp, either anonymously or using a login/password. Note that ftp is unencrypted so you
		     should not use password authentication with this.

	      http and https
		     the package will be uploaded via http or https using the PUT method as specified in WebDAV. The upload method will prompt for
		     a password if necessary.

	      scp    the  package  will  be  uploaded using ssh's scp. This transfers files using a secure ssh tunnel, and needs an account on the
		     upload machine.

	      rsync  the package will be uploaded using rsync over ssh. This is similar to scp, but can save some  bandwidth  if  the  destination
		     file already exists on the upload server. It also needs a login on the remote machine as it uses ssh.

	      local  the package will be "uploaded" locally using /usr/bin/install.  This transfers files to a local incoming directory, and needs
		     appropriate permissions set on that directory.

       hash   The hash algorithm that should be used in calculating the checksum of the files before uploading them. Currently, dput  accepts  the
	      following values for hash:

	      md5    use the md5 algorithm for calculation

	      sha    use the sha algorithm for calculation

       allow_unsigned_uploads
	      This defines if you are allowed to upload files without a GnuPG signature to this host or not.

       allow_dcut
	      This defines if you are allowed to upload a dcut changes file to the queue to remove or move files.

       distributions
	      This defines a comma-separated list of distributions that this host accepts, used to guess the host to use when none is given on the
	      command line.

       allowed_distributions
	      A regular expression (of Python re module syntax) that the distribution field must match or dput will refuse the upload.

       delayed
	      Set a numeric default parameter for delayed uploads (i.e. uploads to this queue will  be	delayed  the  specified  number  of  days.
	      Defaults to the empty string, meaning no delay. This only works with upload queues that support delayed uploads.

       run_lintian
	      This  option  defines  if lintian should be run before the package will be uploaded or not. If the package is not lintian clean, the
	      upload will not happen.

       run_dinstall
	      This options defines if dinstall -n should be run after the package has been uploaded or not. This is an easy way to  test  if  your
	      package would be installed into the archive or not.

       check_version
	      This  option  defines if dput should check if the user has installed the package in his system for testing it before putting it into
	      the archive. If the user has not installed and tested it, dput will reject the upload.

       passive_ftp
	      This option defines if dput should use passive ftp or active ftp for uploading a package to one of the upload  queues.  By  default,
	      dput uses passive ftp connections. If you need to use active ftp connections, set passive_ftp to 0.

       progress_indicator
	      This integer option defines if dput should display a progress indicator for the upload. (Currently implemented in ftp only.)
	      Supported values: 0 (default) - no progress, 1 - rotating progress indicator, and 2 - kilobyte counter.

       scp_compress
	      This option defines if the scp upload to the host will be compressed, or not.  This option is only used for the 'scp' upload method,
	      and has been found to decrease upload time for slow links, and increase upload times for faster links.

       ssh_config_options
	      The arguments of this config options should be ssh config file options in the style documented in ssh_config(5). They will be passed
	      to  all  automatic  invocations of ssh and scp by dput. Note that you can define multiline (dput) configuration options by indenting
	      the second line with whitespace (i.e. similar to RFC822 header continuations).

       post_upload_command
	      This option defines a command to be run by dput after a successful upload.

       pre_upload_command
	      This option defines a command to be run by dput before a upload happens.

       default_host_main
	      This defines the default host for packages that are allowed to be uploaded to the main archive. This variable is used when  guessing
	      the host to upload to.

BUGS
       Please send bug reports to the author.

FILES
       /etc/dput.cf
	      global dput configuration file

       ~/.dput.cf
	      peruser dput configuration file

AUTHOR
       Christian Kurz. Updated by Thomas Viehmann <tv@beamnet.de>.

       Many other people have contributed to this code. See the Thanks file.

SEE ALSO
       dput(1)
       /usr/share/doc/dput

COMMENTS
       The author appreciates comments and suggestions from you, if any.

								   April 8, 2001							dput.cf(5)
All times are GMT -4. The time now is 10:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy