Question regarding the new <filepath> element and recurse behavior...

3 messages Options
Embed this post
Permalink
Ken_Simone

Question regarding the new <filepath> element and recurse behavior...

Reply Threaded More More options
Print post
Permalink
Some javascript/style in this post has been disabled (why?)

Hi All,

 

I'm having a hard time grasping how the recurse behavior works with file-based objects that specify path and filename in one item entity (new to 5.6).

 

For instance:

 

<filehashobject>

  <behaviors recurse_direction='down' max_depth='3'/>

  <filepath operation='pattern match'>c:\a*txt$/</filepath>

</filehashobject>

 

I'm not sure what it means to recurse this. When file and path are specified separately the flow is:

 

1)  Get all matching paths.

2)  Expand this list of paths as directed by the recurse behavior.

3)  Look in those paths for matching files.

 

With path and file specified in one entity, I don't see how to perform step 1 because it's impossible to split out the path.

 

For instance...

 

Are the following folders to be recursed?

 

c:\abctxt

c:\a

 

What if c:\a had a file in it called readme.txt? What if c:\abctxt didn't?

 

Thanks,

Ken

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Danny Haynes

Re: Question regarding the new <filepath> element and recurse behavior...

Reply Threaded More More options
Print post
Permalink
Some javascript/style in this post has been disabled (why?)

                Hi Ken,

 

When the filepath entity was introduced into OVAL v5.6, it was decided that behaviors would only apply to the path and filename entities and not the filepath entity.  This was because the filepath entity was meant to specify an absolute path to a file and it would not make sense to recurse over a file.  For your convenience, I have included the documentation for the filehash_object regarding behaviors and the filepath entity.

 

<xsd:annotation>

  <xsd:documentation>The filehash_object element is used by a file hash test to define the specific file(s) to be evaluated. Each object extends the standard ObjectType as definied in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.</xsd:documentation>

  <xsd:documentation>A filehash_object defines the path and filename of the file(s). In addition, a number of behaviors may be provided that help guide the collection of objects. Please refer to the FilehashBehaviors complex type for more information about specific behaviors.</xsd:documentation>

  <xsd:documentation>The set of files to be evaluated may be identified with either a complete filepath or a path and filename. Only one of these options may be selected.</xsd:documentation>

  <xsd:documentation>It is important to note that the ‘max_depth’ and ‘recurse_direction’ attributes of the ‘behaviors’ element do not apply to the ‘filepath’ element, only to the ‘path’ and ‘filename’ elements. This is because the ‘filepath’ element represents an absolute path to a particular file and it is not possible to recurse over a file.</xsd:documentation>

</xsd:annotation>

 

Please let me know if you have any other questions regarding this issue.

 

Thanks,

 

Danny  

 

From: [hidden email] [mailto:[hidden email]]
Sent: Monday, October 26, 2009 4:59 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] Question regarding the new <filepath> element and recurse behavior...

 

Hi All,

 

I'm having a hard time grasping how the recurse behavior works with file-based objects that specify path and filename in one item entity (new to 5.6).

 

For instance:

 

<filehashobject>

  <behaviors recurse_direction='down' max_depth='3'/>

  <filepath operation='pattern match'>c:\a*txt$/</filepath>

</filehashobject>

 

I'm not sure what it means to recurse this. When file and path are specified separately the flow is:

 

1)  Get all matching paths.

2)  Expand this list of paths as directed by the recurse behavior.

3)  Look in those paths for matching files.

 

With path and file specified in one entity, I don't see how to perform step 1 because it's impossible to split out the path.

 

For instance...

 

Are the following folders to be recursed?

 

c:\abctxt

c:\a

 

What if c:\a had a file in it called readme.txt? What if c:\abctxt didn't?

 

Thanks,

Ken

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Ken_Simone

Re: Question regarding the new <filepath> element and recurse behavior...

Reply Threaded More More options
Print post
Permalink
Some javascript/style in this post has been disabled (why?)

Thanks Dan,

 

I was browsing the documentation in Eclipse, and it only shows the first <documentation> node in its GUI, so I missed this. I switched to source view and wow… Look at all that documentation :-)

 

Thanks,

Ken

 

From: Haynes, Dan [mailto:[hidden email]]
Sent: Monday, October 26, 2009 4:43 PM
To: [hidden email]
Subject: Re: [OVAL-DEVELOPER-LIST] Question regarding the new <filepath> element and recurse behavior...

 

                Hi Ken,

 

When the filepath entity was introduced into OVAL v5.6, it was decided that behaviors would only apply to the path and filename entities and not the filepath entity.  This was because the filepath entity was meant to specify an absolute path to a file and it would not make sense to recurse over a file.  For your convenience, I have included the documentation for the filehash_object regarding behaviors and the filepath entity.

 

<xsd:annotation>

  <xsd:documentation>The filehash_object element is used by a file hash test to define the specific file(s) to be evaluated. Each object extends the standard ObjectType as definied in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.</xsd:documentation>

  <xsd:documentation>A filehash_object defines the path and filename of the file(s). In addition, a number of behaviors may be provided that help guide the collection of objects. Please refer to the FilehashBehaviors complex type for more information about specific behaviors.</xsd:documentation>

  <xsd:documentation>The set of files to be evaluated may be identified with either a complete filepath or a path and filename. Only one of these options may be selected.</xsd:documentation>

  <xsd:documentation>It is important to note that the ‘max_depth’ and ‘recurse_direction’ attributes of the ‘behaviors’ element do not apply to the ‘filepath’ element, only to the ‘path’ and ‘filename’ elements. This is because the ‘filepath’ element represents an absolute path to a particular file and it is not possible to recurse over a file.</xsd:documentation>

</xsd:annotation>

 

Please let me know if you have any other questions regarding this issue.

 

Thanks,

 

Danny  

 

From: [hidden email] [mailto:[hidden email]]
Sent: Monday, October 26, 2009 4:59 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] Question regarding the new <filepath> element and recurse behavior...

 

Hi All,

 

I'm having a hard time grasping how the recurse behavior works with file-based objects that specify path and filename in one item entity (new to 5.6).

 

For instance:

 

<filehashobject>

  <behaviors recurse_direction='down' max_depth='3'/>

  <filepath operation='pattern match'>c:\a*txt$/</filepath>

</filehashobject>

 

I'm not sure what it means to recurse this. When file and path are specified separately the flow is:

 

1)  Get all matching paths.

2)  Expand this list of paths as directed by the recurse behavior.

3)  Look in those paths for matching files.

 

With path and file specified in one entity, I don't see how to perform step 1 because it's impossible to split out the path.

 

For instance...

 

Are the following folders to be recursed?

 

c:\abctxt

c:\a

 

What if c:\a had a file in it called readme.txt? What if c:\abctxt didn't?

 

Thanks,

Ken

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].