Mac: Unable to enumerate and Access is denied error (despite enabling full disk access)

[garyhooks]

I have an Intel based Macbook Pro and when I run CyLR I get a lot of errors or "Warnings" before it starts to acquire other data. I'm unsure whether this is of concern or not.

It looks to be all in /System/ and /private/ directories

I have enabled full disk access for Terminal

[orlikoski]

It looks like this is a permissions issue. To collect system and protected files on a Mac, use the root user or the sudo command when launching CyLR. If that doesn't fix this error please let us know!

On Wed, Aug 16, 2023 at 4:38 AM Gary Hooks @.***> wrote:

I have an Intel based Macbook Pro and when I run CyLR I get a lot of errors or "Warnings" before it starts to acquire other data. I'm unsure whether this is of concern or not.

It looks to be all in /System/ and /private/ directories

I have enabled full disk access for Terminal

[image: 2023-08-16 10_36_38-YAkX5gJ png (2718×1110)] https://user-images.githubusercontent.com/3117532/260967417-6b187636-4ea1-4784-a5e1-921bf042cd38.png

— Reply to this email directly, view it on GitHub https://github.com/orlikoski/CyLR/issues/134, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHUEHAPTMWDUKCHDA6EVBLXVSIJLANCNFSM6AAAAAA3SIBUBU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[garyhooks]

Hi,

The errors and warnings are produced after running using sudo.

I wasn't sure if /system/ and /private/ were always generally off limits?

My Mac knowledge isn't very good.

Thanks Gary

[orlikoski]

It really does seem that it is a permissions issue. I'm unsure of why sudo wouldn't work to fix that.

Here is a test you can perform to ensure that CyLR is running as root. The first command will switch the user to root and then execute the CyLR command from there.

Commands %/sudo su - %/

On Wed, Aug 16, 2023 at 8:21 AM Gary Hooks @.***> wrote:

Hi,

The errors and warnings are produced after running using sudo.

I wasn't sure if /system/ and /private/ were always generally off limits?

My Mac knowledge isn't very good.

Thanks Gary

— Reply to this email directly, view it on GitHub https://github.com/orlikoski/CyLR/issues/134#issuecomment-1680595396, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHUEHEV7BQYHN3HDDCETXLXVTCMVANCNFSM6AAAAAA3SIBUBU . You are receiving this because you commented.Message ID: @.***>

[garyhooks]

Thanks, to show you the root usage and output I've attached another similar screenshot.

I also did exactly the same command as you listed above with the same output

[garyhooks]

I let the application run all the way through - on a new install map as I am testing it. Full log is here: https://pastebin.com/VQ3Ydbxc

It errors on:

• /private/var/folders which is only about 60mb of data
• /System/ which is about 250mb of data

I don't believe it is critical information or of high value

[colorenz]

We see a similar problem. We try to run cylr with our management tool Jamf and get the following errors. Jamf actually has full disk access on the device. Is anything else necessary?

Get CyLR Logs Unhandled exception. System.IO.IOException: Read-only file system at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirectory, Func`2 errorRewriter) at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode) at System.IO.FileStream.OpenHandle(FileMode mode, FileShare share, FileOptions options) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options) at System.IO.StreamWriter.ValidateArgsAndOpenPath(String path, Boolean append, Encoding encoding, Int32 bufferSize) at System.IO.StreamWriter..ctor(String path, Boolean append) at CyLR.Logger.Setup() at CyLR.Program.Main(String[] args)