Hi all
I have a script that I purchased from a company who I thought was trustworthy (long story), and later found out that there is quite a bit of encrypted code. And also, in that encrypted code, they are using fopen() to communicate with their site/server.
I am not happy about this, and actually there are lots of other people I've talked to who are unhappy too.
So I am trying to find out if there is any way to monitor outgoing activity/connections from the script. I want to know what is being sent out.
If you have any ideas... I/we would really appreciate it.
Thank you!
Is it Possible to Monitor fopen() or connection activity?
Moderator: General Moderators
That is beyond me...
I should probably mentioned this...
The script will only work on the domain entered when you buy the script. So I can't try it on any box.
Right now, my site is on shared hosting, so I can't install anything.
I'm looking for a method to monitor this using things like... php, perl, cgi... etc. Or maybe there is a program built in to the server software that I can access.
Hope there is a way!
I should probably mentioned this...
The script will only work on the domain entered when you buy the script. So I can't try it on any box.
Right now, my site is on shared hosting, so I can't install anything.
I'm looking for a method to monitor this using things like... php, perl, cgi... etc. Or maybe there is a program built in to the server software that I can access.
Hope there is a way!
-
blackbeard
- Forum Contributor
- Posts: 123
- Joined: Thu Aug 03, 2006 6:20 pm
- Chris Corbyn
- Breakbeat Nuttzer
- Posts: 13098
- Joined: Wed Mar 24, 2004 7:57 am
- Location: Melbourne, Australia
The way they probably manage the script only working from certain locations is using that connection to check against a database on their own server. Nasty coding for sure. I'd read the licensing terms before "hacking" anything in the script if you have any plans to do that.
Have you contacted the company you bought this from to see if they can shed any light?
As for sniffing packets tcpdump will help. You may actually be able to compile and install it in your own home directory on the server.
Have you contacted the company you bought this from to see if they can shed any light?
As for sniffing packets tcpdump will help. You may actually be able to compile and install it in your own home directory on the server.
d11wtq wrote:The way they probably manage the script only working from certain locations is using that connection to check against a database on their own server. Nasty coding for sure. I'd read the licensing terms before "hacking" anything in the script if you have any plans to do that.
Have you contacted the company you bought this from to see if they can shed any light?
As for sniffing packets tcpdump will help. You may actually be able to compile and install it in your own home directory on the server.
I really don't care what they think. There are a bunch of us who are fed up with them. We all complained about the way they handle licensing, and they don't care. They hardly respond to anyone anymore... even for support.
The way the licensing works... is everytime we login to admin, it connects to their server to check licensing, and if their server goes down or they go out of business... we're all locked out.
That tcpdump, I will look into that. If it works... that would be very cool!
Thank you