paxton_clone.lua: Could not open the file (reading/writing log file Paxton_log.txt)

[jamesmacwhite]

Hi @jareckib @doegox ,

I am trying to run the paxton_clone.lua script you created via: script run paxton_clone with a Proxmark 3 Easy running proxmark3-v4.20469

I get the following error when trying to read a tag.

----------------------------------------------------------------
  Select option:
  1 - Read Paxton blocks 4-7 to make a copy
  2 - Manually input data for Paxton blocks 4-7
  3 - Search in Paxton_log by name and use the data
----------------------------------------------------------------
  Your choice (1/2/3): 1
  Place the Paxton Fob on the coil to read..ENTER to continue..
----------------------------------------------------------------
[-] ⛔ error - .../jameswhite/proxmark3/client/luascripts/paxton_clone.lua:68:  Could not open the file

[+] finished paxton_clone

[usb] pm3 -->

It would appear to be something related to not being able to read the log file: https://github.com/RfidResearchGroup/proxmark3/blob/master/client/luascripts/paxton_clone.lua#L68

I tried creating it manually and set file permissions, but I continue to get the same error. I'm wondering if it is to do the path it is trying to read/write to?

My home directory is /home/jameswhite, the path /home/jameswhite/.proxmark3/logs exists.

Calling script run paxton_clone -h did not run the help info either. Ignore me, I was using the wrong help param.

I'm fairly new to running client scripts so if I'm doing something wrong, apologies.

[jamesmacwhite]

For reference, the values of the variables are:

dir: /home/jameswhite/.proxmark3/logs/
logfile: /home/jameswhite/.proxmark3/logs/:
log_file_path: /home/jameswhite/.proxmark3/logs/Paxton_log.txt

I am running this through WSL2.

[doegox]

hi, I was in the git log only for cosmetic reasons, I know nothing about Lua...
the script was apparently made for Windows only, probably Proxspace only, because of
io.popen('dir /a-d /o-d /tw /b/s and "dir" does not exist in linux (and wsl2 I suspect)

[doegox]

maybe @iceman1001 can help?

[jamesmacwhite]

Thanks and sorry for the noise! That would make sense, if the dir command is failing, causing issues with the logfile function. I didn't realise it was Windows only.

However now you highlighted it, it certainly does look like a Windows dir command, given the command line switches as forward slash. There is a dir command in Linux/WSL, but it wouldn't likely translate without modification.

I could potentially look at writing an equivalent with something like find or ls but then the script would need to do OS detection, but other parts might not function if it's a windows only script.

[iceman1001]

I have no time, feel free to fix the support of different platforms for the lua script.

[jareckib]

I’ll improve the code so that it works on Linux as well. I'm busy at the moment, but I think I’ll get the hang of it by Sunday.

[jamesmacwhite]

@jareckib That would be great! I have a couple of Paxton tags to test the script with, happy to help test on Linux/WSL2.

I can use the hitag commands manually as a workaround, but appreciate your script makes the cloning process simple and verifies the data.

[jamesmacwhite]

Doing some testing the main issue is the dir command, so the main thing for Linux support would be translating the current Windows only command to a Unix/Linux compatible equivalent.

Being totally transparent I tasked AI to rewrite the Windows dir call to a Linux equivalent. This may not be optimised, but it does appear to work.

local logfile = (io.popen('find "' .. dir .. '" -type f -printf "%T@ %p\\n" | sort -nr | cut -d" " -f2-'):read("*a"):match("%C+"))

This allows the script to work:

To improve compatibility, the luascript would potentially need to do OS detection to use the appropriate command for the logfile var.