Jump to content
UBot Underground

meter

Fellow UBotter
  • Content Count

    954
  • Joined

  • Last visited

  • Days Won

    27

Posts posted by meter

  1. cool i've added

     

    -last access date

    -last access ip

    -last access version

    -first access date(the first time user activated license and hence ran software)

    -number of times ran

     

    so should be a easy fix for me to adjust when you update.

     

    could i suggest that you also add first access date and number of times ran. The reason for this is any extra info is pretty useful for any paypal disputes. As you can show when they first ran the software, how many times ran and the last time ran and of course IP

     

    I have the code if you want its slightly modified from aymens update so you may have some of the code already.

     

    Also i'm using for a .net app mainly for the update feature not security i always assummed ubot locker needed visual studio c++ 2010 as its been mentioned in this thread before after installing tests on clients machines this seems to not be the case? was this infact just a ubot requirement and or the UbotLocker compiler requirement.

     

    thanks

    kev123

     

    Thanks kev, I might hit you up for that code in the future :) Visual Studio C++ 2010 redistributable is a requirement for Ubot yes, not necessarily UbotLocker. Still, all modern PCs should have it installed, since so much software depends on it.

     

    -meter

  2. meter have you any idea about features in your next update. I've added a few things in my custom install and I don't want to go any further without checking that things could conflict web backend wise

     

    Here is tentative feature list:

    - Add date of when license was added to database.

    - last access data, last access ip, and last access verion added to licenses.

    - smtp mailing

    - https support

    - changelog window on update

    - option for mutex that only lets one bot run at a time.

     

    I also have additional security features planned which might break backward compatibility. I am still not sure how to work them in. I am also waiting for new Ubot version to be released, since there might be major changes there.

  3. Unfortunately it isn't as protected as I thought, someone contacted me and asked for the download link, he also asked me if he could try to crack it.

    I told him if you can crack it you can get a normal license (because I was curious), he managed to do it within 20 minutes :(

     

    Sorry to hear that h.talei. A few questions:

     

    Was it Ubot exe that was protected, or non Ubot exe?

    Did you give him a valid license file?

    Was he only able to crack the bot, or able to crack and decompile it as well?

     

    Also, any chance you could send me cracked bot via PM, so I can see what he did?

     

    -meter

  4. What is the most appropriate way to include other projects in C# or NodeJS with your system?

    Can you explain how to contact server and ask for request if licenses are ok? Can you teach me so I can integrate other software Ive made with this system.

     

    Hi rodvaN,

     

    For now, this isn't supported. It takes a lot of work to port over to non Ubot apps, it's not something where you can simply write a wrapper and be done.

     

    -meter

  5. meter is 2checkout going to be in that update

     

    thanks

    kev123

     

    It's high on my priority list but I don't know if I'll get to it.

     

    @Meter

    Man I sent u a payment on the 24th and waiting for my license as u were abroad please check your paypal email. Am Not able to send u PMs as I don't have enough posts

    Thanks!

     

     

    Sorry you got list in the shuffle :< Package sent.

     

    Paypal sent this. Have you working on the update meter?

     

    Important PayPal dispute case tracking changes.

     

    Kreatus,

    If you are currently using the Instant Payment Notification (IPN) process or the Case report in your current integration, we want to notify you of a change that may impact your business.

    To ensure you don’t experience a disruption of PayPal service, we encourage you to make any applicable changes by 15 July 2015.

    What is happening?

    We’re enhancing our dispute management system to ensure you receive more detailed and timely information.

    The first phase of this enhancement will encompass chargebacks and ACH bank returns. As part of this enhancement, we’ll be updating the format of the Case ID which is the unique identifier we assign to a dispute case.

    Why is this happening?

    Enhancing our dispute management system will provide more detailed, accurate, and timely information regarding disputes.

    What do I need to do?

    If you are directly integrating data from the IPN process and/or the Case report into your systems, you will need to ensure that your configuration will accept the format change for the unique dispute identifier as outlined here.

    Data passed contains a case_id value. This value will now be formatted in two ways:

    • Existing format: PP-XXX-XXX-XXX-XXX
    • New format: PP-D-XXXX

    For the new format, XXXX is an integer. The “D” indicates the case is a dispute.

    Effective 15 July 2015, cases will be identified using either ID format until the transition to the new dispute management system is complete. This is expected to take several years.

    As a best practice, merchants are encouraged to integrate flexibly so that any future changes to the unique case identifier can be made without integration changes.

    When is this happening?

    We will begin generating cases using the new format after 15 July 2015. To avoid any disruption to the way you process IPNs or the Case report, please update your integration by 15 July.

    Thanks for your patience as we continue to improve our services.

    Your Merchant Services Support Team

     

    Hi Kreatus,

     

    UbotLocker doesn't use case_id variable, so it will be unaffected by this change. In fact, I don't see them sending this variable right now at all.

     

    After July 15, according to their documentation here, UbotLocker should be able to automatically detect and block licenses under dispute, so that's good news :)

    https://developer.paypal.com/docs/classic/ipn/integration-guide/IPNandPDTVariables/

     

    We'll see when they release the feature.

     

    -meter

  6. Hi ewideweb.

     

    1) You cannot explicitly make a product stop working in 6 months. You could, however, delete the project in Ubotlocker for that product in 6 months. That would disable everyone's access to the product.

     

    2) Paypal sends an IPN not only when someone starts paying, but also every time they pay, then they stop paying, when they cancel their subscription, and when their subscription ends. UbotLocker disable the license when Paypal IPN notifies it that subscription has ended. The exact license message is "subscr_failed" OR "subscr_eot".

     

     

     

    -meter

  7. Such a thing is possible, but complicated and clunky. iirc it's possible to make a Ubot plugin run uscript using ubotStudio.RunScript() in C#. So what you do is create Ubot plugin which acts as a server, and listens for commands. Then you can send commands to this server from your own C# program. The plugin can then read the commands, and execute the corresponding uscript.

     

    -meter

  8. SHA-256 is just a hash function. This means it can only hash the value you give it, and it is impossible to reverse (decrypt). You can find various explanations for this by googling 'hashing vs encrypting'.

     

    Also, Ubot devs should probably change function parameter: Sha256 $Encrypt => Sha256 $Data , since you're hashing data usually, not encrypting it.

     

    -meter

    • Like 1
×
×
  • Create New...