Sponsored Content
Special Forums Cybersecurity PCI DSS Compliance : Insecure Communication Has Been Detected Post 302724493 by Yoda on Wednesday 31st of October 2012 04:52:39 PM
Old 10-31-2012
AFAIU there are some services running on your host which does not support TLS or SSL. You can run nmap on your host and discover services running on your network and identify the insecure ones.
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

More command insecure

The more command allows a user to invoke shell. If it is run using the sudo command this will give a user a possibility to run whatever he wants with root's privilegies. Does anybody know about a command with the same abilities that more but without escape to shell? (2 Replies)
Discussion started by: odashe
2 Replies

2. AIX

Can I use Any DSS Tape in My Drive ?

Can I use Any DDS Tape in My Drive ? drive model : IBM-C568303030!D Part number : 19P0798 Can I use DDS1,DDS2,DDS3,DDS5 ? OR Only tape DDS4 can work on this Tape Drive what type DDS compatibilities with this drive ? How do I know? (2 Replies)
Discussion started by: AIX122
2 Replies

3. Red Hat

Looking for PCI Compliance tool for Redhat Lix.

Hi i am in new to Linux world . I have been assigned to a project to find out a tool that will fulfill the PCI compliance for Linux servers for Audit process. anyone have any recommendation on that. Do Rad hat have any native application or plug-ins which we can use for that. (1 Reply)
Discussion started by: sahasuman
1 Replies

4. Linux

Sata sil_3132 on pci express is not getting detected in Linux on powerpc

Hi, I am using Aitech sata device sil3132, on powerpc mpc8641. The device is pci express msi compatible. I had enabled msi in device tree for powerpc but still its giving me Cannot translate IRQ index 0 and so on messages. fsl-msi f7f41600.msi: fsl_msi_setup_hwirq: Cannot translate IRQ index 0... (0 Replies)
Discussion started by: shubha_1
0 Replies

5. HP-UX

Password compliance setting

I need to set password compliance for some servers in my company. However, the requirements are that we need to set different password policies for 3 different user groups within the company. These are : System Users: i.e root, etc Batch/Application Users: oracle, bscs, etc Standard User:... (0 Replies)
Discussion started by: anaigini45
0 Replies

6. OS X (Apple)

POSIX compliance...

Thanks to all you guys about posix compliance I have learnt an enormous amount over the last few days. I have written a program that is an Egg Timer with simple animation. I now realise how sophisticated 'bash' is compared to full posix compliance. The code below has passed all of the tests from... (11 Replies)
Discussion started by: wisecracker
11 Replies
RUP(1)							    BSD General Commands Manual 						    RUP(1)

NAME
rup -- remote status display SYNOPSIS
rup [-dshlt] [host ...] DESCRIPTION
rup displays a summary of the current system status of a particular host or all hosts on the local network. The output shows the current time of day, how long the system has been up, and the load averages. The load average numbers give the number of jobs in the run queue aver- aged over 1, 5 and 15 minutes. The following options are available: -d For each host, report what its local time is. This is useful for checking time syncronization on a network. -s Print time data in seconds (seconds of uptime or seconds since the epoch), for scripts. -h Sort the display alphabetically by host name. -l Sort the display by load average. -t Sort the display by up time. The rpc.rstatd(8) daemon must be running on the remote host for this command to work. rup uses an RPC protocol defined in /usr/include/rpcsvc/rstat.x. EXAMPLE
example% rup otherhost otherhost up 6 days, 16:45, load average: 0.20, 0.23, 0.18 example% DIAGNOSTICS
rup: RPC: Program not registered The rpc.rstatd(8) daemon has not been started on the remote host. rup: RPC: Timed out A communication error occurred. Either the network is excessively congested, or the rpc.rstatd(8) daemon has terminated on the remote host. rup: RPC: Port mapper failure - RPC: Timed out The remote host is not running the portmapper (see portmap(8) ), and cannot accomodate any RPC-based services. The host may be down. SEE ALSO
ruptime(1), portmap(8), rpc.rstatd(8) HISTORY
The rup command appeared in SunOS. Linux NetKit (0.17) August 15, 1999 Linux NetKit (0.17)
All times are GMT -4. The time now is 02:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy