Oura Ring Parser paths too generic

[charpy4n6]

@Slay3r00
The Oura ring parsers are parsing oura ring artifacts in my test data but I do not have Oura ring. Some of the paths are too generic and are including data from other applications. See below screenshot. It appears to me that these paths may be the issue as they are similarly named for other applications (including life360 which you see in my screenshot):

/Containers/Data/Application//Library/Preferences/com.segment.storage..plist'
/Containers/Data/Application//Library/Preferences/com.zendesk..plist'
/Containers/Data/Application//Library/Preferences/????????-????-????-????-????????????.plist'

[charpy4n6]

@Slay3r00 I think we also need to add the source and make sure it shows in the report. Currently the source of the data is not showing.

[Slay3r00]

@charpy4n6 Thanks for pointing that out! I’ll take care of both issues.

I’ll update the parser to include the artifact source so it appears in the report, and I’ll tighten up the Oura Ring parser by removing or refining those overly generic paths so they don’t pull data from unrelated applications. I’ll push a fix once I’ve tested it against the sample data.