We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Data being uploaded to menu.asposeptyltd.com

Aspose.Total Product Family
#1

We have identified a large amount of data being uploaded to menu.asposeptyltd.com.


We do not believe that we initiated this transfer.

Please advise ASAP what could have caused this.

Thank you,
J
#2

We have identified a large amount of data uploaded to menu.asposeptyltd.com.
We do not believe we initiated this transfer.
Please contact me ASAP regarding this issue and what could be the cause.
Thank you,

Joe MarkAnthony, Pratt & Whitney
IT Senior Discipline Specialist, Enterprise Architecture
Fellow, Technical Applications and Strategy
860-565-5454 (w), 860-709-2666 (m)

This message was posted using Support2Forum.

#3

Hi Joe,


Thank you for contacting support. Please elaborate a bit more about the issue here in this forum thread. We’ll investigate and reply you appropriately.

#4

I received the following message from our security team:

“A computer (XXXX) has been identified as sending data (29 MB) out [menu.asposeptyltd.com](http://menu.asposeptyltd.com/):
on Jan 2, 2017.
(The data may have been sent when you uploaded a file, engaged in
video-conferencing, or participated in another Internet based activity.)”

The only thing I can think of is around that time I was using our Aspose.Total libary (we have been customers for some time) on the computer in question but I had an old license file in place, but had just imported the latest libraries. I got lots of error messages. I replaced the old license file with our new license file, and the errors went away. However, I soon go the message above. This is why perhaps some log data was sent as part of a license verification?

This is a critical issue - we cannot have any data sent to your website. Please look into your logs to see what was sent, and what was the cause of the initiation. It may not have been caused by the library, but I do not recall otherwise doing anything on your website (especially “[menu.asposeptyltd.com](http://menu.asposeptyltd.com/)”).

Again, I must stress the importance of this and need to understand what can cause 29MB of data sent to your site.

Thanks - Jeo

#5

Hi Jeo,


Thank you for the details. Please note, the latest version of Aspose APIs monitors the regular usage and keep track of the API licenses. The clients can also apply a usage based license for each Aspose library as narrated here. Please let us know in case of any confusion or questions.

#6

Hi Joe,

Thanks for the heads up and sharing your concern which is valid. Our customer happiness developer, Imran Rafique is not aware of it so please excuse him. Let me address your concern to clear the confusion.

However, I soon go the message above. This is why perhaps some log data was sent as part of a license verification?


This
is a critical issue - we cannot have any data sent to your website.
Please look into your logs to see what was sent, and what was the cause
of the initiation. It may not have been caused by the library, but I
do not recall otherwise doing anything on your website (especially
“menu.asposeptyltd.com”).
Again, I must stress the importance of this and need to understand what can cause 29MB of data sent to your site.

First of all, this was not any log data that was being sent for license verification. So, please rest assured that you didn’t sent any of your data to our website. Then what was it?

You also noticed that data was being sent to menu.asposeptyltd.com which is one of our newly developed app to try centralizing header and footer on all of our website modules including CMS, Blog, Forums etc. Whenever website is visited first time, menu related resources (JS/CSS/Images) are cached in client’s browser to improve loading speed of web pages for better user experience of customers.

There was a bug in our menu.asposeptyltd.com app due to which client’s local cache was being updated after every 5 seconds assuming that header/footer content is updated at menu.asposeptyltd.com. We have applied the fix. Please check again and hopefully you won’t see this issue any more. If you still notice any issue, please feel free to let us know and we will fix it.

Have a good time.

#7

Thanks for the information. I will relay to our security team. The concern is that we were somehow sending local data, but based on your note that is not the case.

If you learn anything further you think would be useful, please provide.

Thanks - Joe
#8

Hi Joe,


Sure, we’ll let you know if there is any useful information available in this regard.