That's the way it worked for me Michael.
They just port scan the IP, and look up what usually runs on that port. I had some stuff running on odd-ball ports on the router in front of the server. Their port scan detected the ports, and refused to pass the PCI Compliance until I shut it down.
Thanks
Here is the report from doing
netstat -tupan|grep LISTEN
[root@cabin4 admin]# netstat -tupan|grep LISTEN
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN
10524/nginx: master
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN
24649/dovecot
tcp
Michael and Chuck,
No they did not have access to the server. Just their port scan.
I blocked that port with iptables so... the scan should pass
I was dealing with these clown a few years back and their scans showed I
had ports open that are only on windoz machines.
They are no
Hi Tim,
> I have a client that is telling me that their pci scan is failing
> because "lighttpd service running on port 42443"
>
> Is this service even running on BX?
No, "lighthttpd" is not included on a stock BlueOnyx nor do any add-on
PKGs from the shop provided it.
Do this to check:
Hi Tim,
> Here is the report from doing
>
> netstat -tupan|grep LISTEN
>
> Nothing for port 42443
>
> Correct?
Correct.
> Could nginx be effecting their PCI scans?
No. When you acticate Nginx, Apache releases port 443 and Nginx binds to
port 443. Port 42443 isn't involved in that.
I wonder
I have a client that is telling me that their pci scan is failing
because "lighttpd service running on port 42443"
Is this service even running on BX?
Thanks
--Tim
___
Blueonyx mailing list
Blueonyx@mail.blueonyx.it
Hi Chuck,
> They just port scan the IP, and look up what usually runs on that port.
> I had some stuff running on odd-ball ports on the router in front of the
> server. Their port scan detected the ports, and refused to pass the PCI
> Compliance until I shut it down.
That's how a PCI
There are two elements to package descriptions. Firstly, at the newlinq server
level. Those are auto generated during the package build process. Internally,
once you actually install a module at a site level - there is more detail
available. In earlier versions of the build process, i
Hi all,
Greg wrote:
> Could you as a user edit this? Not really. Its in CODB, but that will
> get refreshed every time you poll for new apps. But once a module is
> installed, descriptions do exist in /home/webapps/*/product_info … but
> that data is complete...
If it's there, I could pull it
