Closed kirbyju closed 1 month ago
Hi Justin,
Did you follow the install instructions and run the xattr command from the terminal?
On Wed, 31 Jul 2024, 20:35 Justin Kirby, @.***> wrote:
I tried it out on my Macbook but it appears to be a corrupted file that my system won't open.
image.png (view on web) https://github.com/user-attachments/assets/80cb2034-a98f-4182-980d-fb264d7e0363
— Reply to this email directly, view it on GitHub https://github.com/RSNA/anonymizer/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIXFIEZ2LYUCX2XTSK3DGLZPEVA7AVCNFSM6AAAAABLZBBVHKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ2DANRYGQYDGMI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Oops. My mistake, I overlooked that. However, running:
% xattr -rc /Applications/Anonymizer_17.*.app
Produced:
option -r not recognized
usage: xattr [-slz] file [file ...]
xattr -p [-slz] attr_name file [file ...]
xattr -w [-sz] attr_name attr_value file [file ...]
xattr -d [-s] attr_name file [file ...]
xattr -c [-s] file [file ...]
The first form lists the names of all xattrs on the given file(s).
The second form (-p) prints the value of the xattr attr_name.
The third form (-w) sets the value of the xattr attr_name to attr_value.
The fourth form (-d) deletes the xattr attr_name.
The fifth form (-c) deletes (clears) all xattrs.
Seems to work if I drop the 'r' from the command. Looking forward to trying this out!
Which version of MacOS and chipset are you using?
On Wed, 31 Jul 2024, 21:08 Justin Kirby, @.***> wrote:
Oops. My mistake, I overlooked that. However, running: % xattr -rc /Applications/Anonymizer_17.*.app
Produced:
option -r not recognized
usage: xattr [-slz] file [file ...] xattr -p [-slz] attr_name file [file ...] xattr -w [-sz] attr_name attr_value file [file ...] xattr -d [-s] attr_name file [file ...] xattr -c [-s] file [file ...]
The first form lists the names of all xattrs on the given file(s). The second form (-p) prints the value of the xattr attr_name. The third form (-w) sets the value of the xattr attr_name to attr_value. The fourth form (-d) deletes the xattr attr_name. The fifth form (-c) deletes (clears) all xattrs.
Seems to work if I drop the 'r' from the command. Looking forward to trying this out!
— Reply to this email directly, view it on GitHub https://github.com/RSNA/anonymizer/issues/1#issuecomment-2261224563, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIXFIFWT33C5YFSFI2K6FLZPEY4LAVCNFSM6AAAAABLZBBVHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRRGIZDINJWGM . You are receiving this because you commented.Message ID: @.***>
Apple M2 Pro on Sonoma 14.5
That's strange, Apple Macbook Air on Sonoma 14.5 the recursive switch is there:
xattr -h
usage: xattr [-l] [-r] [-s] [-v] [-x] file [file ...]
xattr -p [-l] [-r] [-s] [-v] [-x] attr_name file [file ...]
xattr -w [-r] [-s] [-x] attr_name attr_value file [file ...]
xattr -d [-r] [-s] attr_name file [file ...]
xattr -c [-r] [-s] file [file ...]
The first form lists the names of all xattrs on the given file(s).
The second form (-p) prints the value of the xattr attr_name.
The third form (-w) sets the value of the xattr attr_name to the string attr_value.
The fourth form (-d) deletes the xattr attr_name.
The fifth form (-c) deletes (clears) all xattrs.
options:
-h: print this help
-l: print long format (attr_name: attr_value and hex output has offsets and
ascii representation)
-r: act recursively
-s: act on the symbolic link itself rather than what the link points to
-v: also print filename (automatic with -r and with multiple files)
-x: attr_value is represented as a hex string for input and output
This is an interim measure whilst arranging the relevant digital certificates to sign the executables of all three platforms. Did the program run successfully after running xattr without the recursive switch?
On Thu, 1 Aug 2024 at 16:53, Justin Kirby @.***> wrote:
Apple M2 Pro on Sonoma 14.5
— Reply to this email directly, view it on GitHub https://github.com/RSNA/anonymizer/issues/1#issuecomment-2263278109, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIXFIB3ZAEOQETUFKJG2J3ZPJDWNAVCNFSM6AAAAABLZBBVHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGI3TQMJQHE . You are receiving this because you commented.Message ID: @.***>
-- Michael Evans DX.LIFE (Pty) Ltd. +27 72 584 6989
... apologies, meant to include Apple Macbook Air M1 I will check on Macbook Air M2
On Thu, 1 Aug 2024 at 18:43, Michael Evans @.***> wrote:
That's strange, Apple Macbook Air on Sonoma 14.5 the recursive switch is there:
xattr -h
usage: xattr [-l] [-r] [-s] [-v] [-x] file [file ...]
xattr -p [-l] [-r] [-s] [-v] [-x] attr_name file [file ...] xattr -w [-r] [-s] [-x] attr_name attr_value file [file ...] xattr -d [-r] [-s] attr_name file [file ...] xattr -c [-r] [-s] file [file ...]
The first form lists the names of all xattrs on the given file(s).
The second form (-p) prints the value of the xattr attr_name.
The third form (-w) sets the value of the xattr attr_name to the string attr_value.
The fourth form (-d) deletes the xattr attr_name.
The fifth form (-c) deletes (clears) all xattrs.
options:
-h: print this help
-l: print long format (attr_name: attr_value and hex output has offsets and
ascii representation)
-r: act recursively
-s: act on the symbolic link itself rather than what the link points to
-v: also print filename (automatic with -r and with multiple files)
-x: attr_value is represented as a hex string for input and output
This is an interim measure whilst arranging the relevant digital certificates to sign the executables of all three platforms. Did the program run successfully after running xattr without the recursive switch?
On Thu, 1 Aug 2024 at 16:53, Justin Kirby @.***> wrote:
Apple M2 Pro on Sonoma 14.5
— Reply to this email directly, view it on GitHub https://github.com/RSNA/anonymizer/issues/1#issuecomment-2263278109, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIXFIB3ZAEOQETUFKJG2J3ZPJDWNAVCNFSM6AAAAABLZBBVHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGI3TQMJQHE . You are receiving this because you commented.Message ID: @.***>
-- Michael Evans DX.LIFE (Pty) Ltd. +27 72 584 6989
-- Michael Evans DX.LIFE (Pty) Ltd. +27 72 584 6989
Are you using the standard xattr command that's built into macOS? Try running type xattr You should receive "xattr is /usr/bin/xattr" if you're using the standard command
On Thu, 1 Aug 2024 at 18:43, Michael Evans @.***> wrote:
That's strange, Apple Macbook Air on Sonoma 14.5 the recursive switch is there:
xattr -h
usage: xattr [-l] [-r] [-s] [-v] [-x] file [file ...]
xattr -p [-l] [-r] [-s] [-v] [-x] attr_name file [file ...] xattr -w [-r] [-s] [-x] attr_name attr_value file [file ...] xattr -d [-r] [-s] attr_name file [file ...] xattr -c [-r] [-s] file [file ...]
The first form lists the names of all xattrs on the given file(s).
The second form (-p) prints the value of the xattr attr_name.
The third form (-w) sets the value of the xattr attr_name to the string attr_value.
The fourth form (-d) deletes the xattr attr_name.
The fifth form (-c) deletes (clears) all xattrs.
options:
-h: print this help
-l: print long format (attr_name: attr_value and hex output has offsets and
ascii representation)
-r: act recursively
-s: act on the symbolic link itself rather than what the link points to
-v: also print filename (automatic with -r and with multiple files)
-x: attr_value is represented as a hex string for input and output
This is an interim measure whilst arranging the relevant digital certificates to sign the executables of all three platforms. Did the program run successfully after running xattr without the recursive switch?
On Thu, 1 Aug 2024 at 16:53, Justin Kirby @.***> wrote:
Apple M2 Pro on Sonoma 14.5
— Reply to this email directly, view it on GitHub https://github.com/RSNA/anonymizer/issues/1#issuecomment-2263278109, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIXFIB3ZAEOQETUFKJG2J3ZPJDWNAVCNFSM6AAAAABLZBBVHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGI3TQMJQHE . You are receiving this because you commented.Message ID: @.***>
-- Michael Evans DX.LIFE (Pty) Ltd. +27 72 584 6989
-- Michael Evans DX.LIFE (Pty) Ltd. +27 72 584 6989
Apparently not! I guess this default was overridden when I installed python 3.11.
% type xattr
xattr is /Library/Frameworks/Python.framework/Versions/3.11/bin/xattr
Hmmm, I wasn't aware of the python wrapper (https://github.com/xattr/xattr)
Did you manage to get the anonymizer running?
On Thu, 1 Aug 2024 at 19:08, Justin Kirby @.***> wrote:
Apparently not! I guess this default was overridden when I installed python 3.11.
% type xattr xattr is /Library/Frameworks/Python.framework/Versions/3.11/bin/xattr
— Reply to this email directly, view it on GitHub https://github.com/RSNA/anonymizer/issues/1#issuecomment-2263551133, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIXFIGL6JU6AUMRCP22W7DZPJTRNAVCNFSM6AAAAABLZBBVHKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTGU2TCMJTGM . You are receiving this because you commented.Message ID: @.***>
-- Michael Evans DX.LIFE (Pty) Ltd. +27 72 584 6989
Yep, I just ran a test subject through it. Upon a cursory check it appears everything was processed. Glad to hear this is an interim measure. It'll definitely make our less tech-savvy users happy if they don't have to fuss with command line interfaces. If that's on your roadmap I don't see any reason to keep this issue open anymore.
Glad you have it running now, I agree, distribution & installation of the executables for the 3 platforms should be as user friendly as possible.
Issue opened to create authorized binaries/distros
I tried it out on my Macbook but it appears to be a corrupted file that my system won't open.