Quantcast
Channel: XLS Padlock - G.D.G. Software Forum
Viewing all 1024 articles
Browse latest View live

Cannot open macbook demo

$
0
0

@JohnBrennan wrote:

Hi there

Congrats with the new version I tried to test the demo but the macbook demo I cant open because it BOMBS my excel 2007 -can you do that macbook demo without the Workbook loading as my excel cannot open it even after I click refresh -that does not work with excel 2007 it bombs out

Thanks

Posts: 4

Participants: 2

Read full topic


XLSPadlock activation code not recognized

$
0
0

@ArthurBorsboom wrote:

I have send this message on the contact form and to info@xlspadlock.com to no avail, so I’m posting it here.

I have renewed the software maintenance for XLS Padlock and according to the xlspadlock site I have now an active maintenance.

However, I am unable to activate XLS Padlock v3.0.0, neither by Internet, nor manually.

XLSPadlock-activation-issue-4

Can somebody help?

Posts: 3

Participants: 2

Read full topic

Major release: XLS Padlock 3 - September 9th, 2017

$
0
0

@gdgsupport wrote:

XLS Padlock 3 - a major release

Protect your Excel workbooks, formulas and VBA code against copy. XLS Padlock 3 lets you sell licenses for your Excel workbooks with new online activation and validation, WooCommerce integration and much more. Upgrade is recommended for registered users with an active maintenance.

What’s new

  • New online validation feature: ask a web server to validate the end user’s activation key before letting him access the workbook. Since it can be performed periodically, validation allows you to control the use of your Excel workbook: for instance, you can remotely block access in case of fraudulent purchases or refunds.
  • New WooCommerce integration kit: you can now sell and automate licensing of compiled Excel workbooks. Activation and validation features of XLS Padlock can be automated and fully integrated with your existing WooCommerce shop. See a fully-functional online demo. The WooCommerce Integration Kit is available for free to every XLS Padlock customer.
  • New security option: Hide Formula Bar (and disable the option so that users can’t activate it again in the secure Excel session).
  • New feature: secure save files can be configured to be readable only on the computer they were saved on (hardware-locking).
  • New feature: clear activation data. Lets you remove activation keys on your local computer for testing purposes.
  • When selecting a secure save file, if the user chooses Cancel, the EXE goes back to the previous dialog box (where the user can choose what to do).
  • The Print option is now disabled when print is forbidden.
  • Users must confirm now when they save over an existing save file (prompt for overwriting save files).
  • Optimized loading of secure workbooks.
  • The “Protect Sheet” context menu command is now disabled.
  • Disabled “Share” button on Excel 2016.
  • Improved disabling of UI controls for all Excel versions.
  • The QAT (Quick Access Toolbar) is now always reset in a secure Excel session (can be disabled in the XLS Padlock’s Advanced Options).
  • Several Excel constants are now properly recognized by the VBA compiler.
  • The secure Excel session will no more open workbooks executed from Windows Explorer. Instead, they will be opened in a new Excel instance.
  • New VBA API related to online validation.
  • Updated user guide.
  • Updated core components.
  • Minor improvements.

XLS Padlock is software for protecting your Excel workbooks, VBA code and formulas.
XLS Padlock works as an Excel compiler that allows you to turn your Excel workbooks into secure applications (XLS to EXE). A lot of security options and customization possibilities. Learn more about our Excel workbook protection software.

Free fully-functional trial available at https://www.xlspadlock.com/download

More information at https://www.xlspadlock.com

Posts: 3

Participants: 1

Read full topic

VBA compiler error command offset

$
0
0

@JohnBrennan wrote:

when I try to compile .Offset(, 1) gives an error ? WHY ??? Is offset not supported ? Syntax error on 1 in the bracket (red line underneath)

Set rngNumbers = Range(“B2”, Cells(Rows.Count, “A”).End(xlUp).Offset(, 1)
var = Application.Transpose(rngNumbers.Offset(, -1))
Range(“G2:G” & Rows.Count).ClearContents

Posts: 2

Participants: 1

Read full topic

Wish list for the future release of XLS Padlock

$
0
0

@PhuongM wrote:

Hi XLS Padlock team,

I would like to have the following features available in the future version of XLS Padlock:

  • A CANCEL button in the opening dialog box to allow me to cancel opening the workbook. It would be helpful especially when we just accidentally click on the EXE file and we don’t really want to run it.
  • Support opening secure saved workbooks within a running session.

Thanks.

Posts: 2

Participants: 2

Read full topic

Retrieve Expiration Date

$
0
0

@PhuongM wrote:

I want to show the expiration date and number of days left in order to remind customers to renew their subscription before it is expired.
How can I use VBA to retrieve the expiration date from the activated licence?

Posts: 4

Participants: 2

Read full topic

Create trial without activation key

$
0
0

@LawnBowls wrote:

I would like to create a 14 day trial version of my workbook which doesn’t require an activation key. It seems I have to generate a key to create a trial. Can anyone help.

Posts: 2

Participants: 2

Read full topic

Activation Kit error 404

$
0
0

@selestasvz wrote:

I uploaded the Activation Kit to the server and received an error of 404. The address is registered correctly. The same error is output from the browser. What can I do wrong?

2017-09-22_13-40-47

Posts: 1

Participants: 1

Read full topic


Validation Errors

Xls-Padlock v3 – issues and question

$
0
0

@nd09 wrote:

Hello, I have a few issues and questions with your new version

Issus:

  1. Still have problems with the right to left language, Specially when I’m trying to use the “registration form”, for example (of curse after the “enable right to left” checked) I have no control on the alight direction, I want to center the text and it always go right, I want alight to left the text inside the TextBox (so the end-user can insert an Email address left to right) and its start from the right
  2. I did exactly like it says in the woo commerce kit PDF instructions and after I try to contact the EXE workbook with the my website I get this massage.
    2017-09-25_10h32_39

Questions:

  1. You didn’t guide us in the woo commerce kit PDF instructions how can I add second-different item/product. Do I need to upload the all “xlspadlock-woocom” folder again with a different name or do I just need to duplicate some PHP file with a different information of the EXE workbook?
  2. If the user does not have an internet connection and I use the “online validation”, is his EXE workbook going to open?
  3. I’m not sure that I understand the Max activation per order variable, it means that if the variable value is 2 and the customer order 1 quantity he gets 2 activations? or the maximum of the order can be 2?

Thank you for your great job!

Posts: 1

Participants: 1

Read full topic

Create a save a sheet as CSV format

$
0
0

@burkeypg wrote:

I have a macro that will copy a sheet and then save it as a CSV format. It uses the Application.GetSaveAsFilename to get the location and file name, then I use the With Activeworkbook .saveas to save the file.

It does save the file just fine in the compiled version, but after it save the file to csv, it will prompt the users to save the local workbook in a secured file format .xlsc. Even if I go along and say to save it, it doesn’t actually seem to update the file with any changes. My preference would be to not have this second “secured” file save be asked at all.

The only security setting that I have enabled is “Allow secure save”

Posts: 1

Participants: 1

Read full topic

XLS Padlock with Yubikey and generic FIDO U2F Security Key

$
0
0

@PhuongM wrote:

Is it possible to add Yubikey or a generic FIDO U2F Security Key as additional option for protection with hard keys?
Protection with USB stick is not good enough since these sticks are easily to be cloned.
Going with Enky SL dongle only is not really a good business decision since we hardly get a good deal with that single player in the market, or worst Enky might go out of business then we would be stuck.

Posts: 1

Participants: 1

Read full topic

Help me please to Compile this code with StrConv()

$
0
0

@selestasvz wrote:

Help me please to Compile this code.
I can’t understand what to do with Arrays BKey, BTxt and how to replace the function StrConv


Function ComputeHash_C(Meth As String, ByVal clearText As String, ByVal Key As String, Optional OutType As String) As Variant

Dim BKey() As Byte
Dim BTxt() As Byte

Dim oT As Object
Dim TextToHash() As Byte
Dim bytes() As Byte
Dim SHAhasher

BTxt = StrConv(clearText, vbFromUnicode)
BKey = StrConv(Key, vbFromUnicode)

If Key <> "" Then
    If Meth = "SHA512" Then
        Set SHAhasher = CreateObject("System.Security.Cryptography.HMACSHA512")
    ElseIf Meth = "SHA384" Then
        Set SHAhasher = CreateObject("System.Security.Cryptography.HMACSHA384")
    ElseIf Meth = "SHA256" Then
        Set SHAhasher = CreateObject("System.Security.Cryptography.HMACSHA256")
    Else
        Set SHAhasher = CreateObject("System.Security.Cryptography.HMACSHA1")
    End If
    SHAhasher.Key = BKey
    bytes = SHAhasher.ComputeHash_2(BTxt)
Else
    If Meth = "SHA512" Then
        Set SHAhasher = CreateObject("System.Security.Cryptography.SHA512Managed")
    ElseIf Meth = "SHA256" Then
        Set SHAhasher = CreateObject("System.Security.Cryptography.SHA256Managed")
    ElseIf Meth = "SHA384" Then
        Set SHAhasher = CreateObject("System.Security.Cryptography.SHA256Managed")
    Else
        Set SHAhasher = CreateObject("System.Security.Cryptography.SHA1Managed")
    End If
    Set oT = CreateObject("System.Text.UTF8Encoding")
    TextToHash = oT.GetBytes_4(clearText)
    bytes = SHAhasher.ComputeHash_2((TextToHash))
End If

If OutType = "STR64" Then
   ComputeHash_C = ConvToBase64String(bytes)
ElseIf OutType = "STRHEX" Then
   ComputeHash_C = ConvToHexString(bytes)
ElseIf OutType = "RAW" Then
    ComputeHash_C = Base64Decode(ConvToBase64String(bytes))
Else
   ComputeHash_C = bytes
End If
Set SHAhasher = Nothing

End Function

Posts: 1

Participants: 1

Read full topic

How to compile DateDiff

Vba compiler errors x3


XLS Padlock Discount Code

XLS Padlock with Enky SL dongle

$
0
0

@PhuongM wrote:

To work around the poor performance issue of arrays calculation as mentioned in my earlier post, I’ve developed my own compiled DLL for the main calculation engine in VB6 in stead of moving the code into the XLS Padlock compiler. I’m aware that my spreadsheet and the DLL could be stripped off the XLS padlock compiled EXE file by some advanced users so I want to tie the DLL to the EXE file as well as to the Enky dongle by using AES encrypted connection strings . The problem is to find out where to save the AES secret encryption/decryption key. I don’t want to hard code it within the XLS Padlock compiler or the DLL for some reasons.

Hence, I want to use the secret key saved in the Enky dongle as the AES key to encrypt/decrypt the connection strings. How can I do this with XLS Padlock?

Posts: 1

Participants: 1

Read full topic

XLS Padlock - System ID

VBA Compiler - Dynamic Array

$
0
0

@PhuongM wrote:

I was thrown an error when trying to recall the value stored in an array, see code below. What am I missing here?

Public XS2RunList as Variant
Public nXS as long

Sub XS2Run
Dim i as long
Dim XS2RunList = VarArrayCreate([1, nXS],12)
For i = 1 to nXS
XS2RunList[i] = i
Next
Msgbox (XS2RunList[1])
End Sub

Sub MAIN_XP (Param1)
nXS = 3
XS2Run
Msgbox (XS2RunList[1])
End Sub

Posts: 3

Participants: 2

Read full topic

VBA Compiler - Debugger exposes secret strings

$
0
0

@PhuongM wrote:

I tested my compiled workbook on different machines with different configurations to see how it behaves. The workbook works well on most of testing machines, one failed. That’s ok to me since the failure is just because the machine is missing some components, BUT the there is an issue happened with the VBA compiler where I saved my secret strings to tie the DLL module into the compiled workbook - the debugger of the XLSPadlock VBA compiler kicked in and exposed all my secret strings in plain texts though I had tried to hide them by using some old tricks ie. using CHR() function to replace the strings combined with whatever encryption techniques. Please see attached screenshot.

The debugging information is helpful as it helps to pin down where the errors are, BUT I really don’t want it to show the STACK CONTENT as it fails the security of my workbook.

Is there anyway to prevent the stack content from showing up, And/Or totally turn off the debugger?

By the way, I really want to have an extra security layer by using the dongle as mentioned in my earlier post. Please let me know when it is available as my project is being stuck at this point.

Posts: 2

Participants: 2

Read full topic

Viewing all 1024 articles
Browse latest View live