Jump to content
484 posts in this topic

Recommended Posts

6 hours ago, 5T33Z0 said:

it puts .icns files where they don't belong.

This should be a historical legacy, caused by the previous database. You can delete the database and select "Download Upgrade Package" under the "Help" menu, and it will probably be fine.

Which Commits are used in OCAT for updating OpenCore? OCAT does not provide information about that. But in order to discuss OpenCore issues it is necessary to know which build someone is using.

 

When I update it OpenCore manually, I use these nightly builds: https://dortania.github.io/builds/?product=OpenCorePkg&viewall=true

The official release are packages from Acidanthera https://github.com/acidanthera/OpenCorePkg/releases

 

I think being able to switch between these two trees (official/nightly) would be great. Then you know exactly which version someone is using.

 

Thanks

1 hour ago, 5T33Z0 said:

Which Commits are used in OCAT for updating OpenCore?

I only use the official OC version, I think it is reliable enough, as for the third party version you mentioned, I can consider it later. Thanks for the suggestion.
The version I use is here, officially released by OC.

https://github.com/acidanthera/OpenCorePkg/actions
 

17 minutes ago, ic005k said:

I only use the official OC version, I think it is reliable enough, as for the third party version you mentioned, I can consider it later. Thanks for the suggestion.
The version I use is here, officially released by OC.

https://github.com/acidanthera/OpenCorePkg/actions
 

I think that's identical with the one on the Dortania site. (Same Commit #)

2 hours ago, 5T33Z0 said:

I think that's identical with the one on the Dortania site. (Same Commit #)

Yes, there is not much difference, originating from the OC official. But I habitually use the official OC release.

@5T33Z0Come up with any new ideas and come together to improve the quality of OCAT's products.

When trying to update to https://github.com/ic005k/QtOpenCoreConfig/releases/tag/20211016 using the update feature, the program crashes.

 

I Updated manually.

 

Feature suggestion: A new sub-menu in the File menu for recently used files.  "File" > "Open Recent…"

33 minutes ago, 5T33Z0 said:

using the update feature, the program crashes.

Is there a download progress bar?

 

34 minutes ago, 5T33Z0 said:

A new sub-menu in the File menu for recently used files.  "File" > "Open Recent…"

This feature has been moved to the toolbar, the third button.

2 hours ago, ic005k said:

Is there a download progress bar?

 

This feature has been moved to the toolbar, the third button.

 

1. No, progress bar, it just crashed. Then I manually installed it.

 

2. A file path in the "Open recent…" menu would be helpful. Otherwise you just have entries without any references, like:

  1. config
  2. config
  3. config

 

 

3 minutes ago, 5T33Z0 said:

No, progress bar, it just crashed. Then I manually installed it.

Okay, I'll look for the reason.

 

6 minutes ago, 5T33Z0 said:

A file path in the "Open recent…" menu would be helpful.

Add this in the next release.

@5T33Z0When you select "Download upgrade package" under the "Help" menu, does it also cause the app to crash?

1 minute ago, 5T33Z0 said:

He is looking into it already, I think.

Oh, so far I can't find the reason, because it's very normal on my side, under Win11 and Mac12.0.

Maybe I should install a Windows 10 and use it to test OCAT.

@ic005k It still crashes when trying to update (macOS 10.15). I have a crash log for you. Looks like to old "empty" folder "*" bug is back

 

OCAuxiliaryTools_2021-10-13-153427_T530.crash

Edited by 5T33Z0

@eSaF @5T33Z0 @niknod 

Please download the file below, run it and select "Download Upgrade Package" under the "Help" menu to see if there are any problems.

 

https://github.com/ic005k/QtOpenCoreConfig/suites/4047318736/artifacts/102601922

@ic005k, from the crash log it seems that `i` is very large here: https://github.com/ic005k/QtOpenCoreConfig/blob/44992349aac10bff1721f0ff7eae13e5681154ae/autoupdatedialog.cpp#L259. It then takes SizeNames out of bounds and crashes when accessing invalid memory.

 

In general you should not rely that there is no intruder between your client app and your server. The intruder may manipulate the traffic, so you should sanitize really all the values you get and do not trust them.

 

Here most likely `size` is either 0, for a slow network, or very large. Since you take logarithm of `size`, taking both logarithm of zero (which is undefined, but generally silently yields 0xFFFFFFFF) and a very large number would result on an out of bounds read.

 

Hope it helps & thx for all your effort.

  • Thanks 1
×
×
  • Create New...