{5} Assigned, Active Tickets by Owner (Full Description) (7 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

bwilliams

Ticket Summary Component Milestone Type Created
Description
#5 Parse errors from builder output Misc Release 1.0 Feature 01/19/06

Read the output from the policy build process and make sense of errors, as much as possible. This task may require

1) modifications to checkpolicy (to improve its error reporting) 2) modifications to the signposts in refpolicy (so checkpolicy knows where problems occurred) 3) a JavaCC parser to read the output from Make

dsugar

Ticket Summary Component Milestone Type Created
Description
#204 preferences for rpm building Plugin Preferences Feature 08/16/07

SLIDE needs a preference for specifying the Version, Release, Vendor, and Packager that will end up in the rpm metadata when building a policy rpm.

#66 Comments included in Search Results Search None Bug 05/22/06

Setup: 1. Ran as Eclipse Application from source 2. Created Full Policy Project with RefPolicy? Version 20060307

Example that shows the issue: 1. Action: Selected the Project and selected "Search -> Search" menu item

Result: "Search" dialog opened

2. Action: Selected "Slide Search" tab in Search window

Result: "Slide Search" page displayed

3. Action: With "Selected resources" radio button selected, entered "port" in th text box; fill the

"Type Enforcment Interface Call" check box. Click on the "Search" button

Comments were included in the results. For example,

#coronet_tcp_bind_stunnel_port(stunnel_t)

#146 In the Find/Replace tool, you can only find in one of the three editors Editors Release 1.2 Bug 12/26/06

When you hit Find/Replace in the edit menu, it will only search the active(or possibly only the if editor) editor in the Module Editor.

#30 Underline errors where possible Builders None Feature 03/30/06

Now that reference policy has proper line markers, it would be worthwhile to use the other information that error messages provide so that SLIDE can underline the token at fault.

For example, the following error message tells you what token to underline.

policy/modules/admin/netutils.te:120:ERROR 'syntax error' at token 'corenet_raw_sendrecv_wrong_if' on line 470831:

corenet_udp_sendrecv_all_if(ping_t) corenet_raw_sendrecv_wrong_if(ping_t)

/usr/bin/checkpolicy: error(s) encountered while parsing configuration

Most of the time, just underlining the first instance of that token on the line in question will be correct. In the future, SLIDE should tokenize the line the same way that checkpolicy does (via libsepol?) to actually get the right token.

#138 Team Integration Policy Explorer Feature 11/17/06

The ability to add a module in to svn in the Policy Explorer view.

#13 Things to verify Misc None Inquiry 02/08/06

Just some things to look at during testing that I don't want to forget about

1) Creating a module project that linkes to installed policy 2) Creating a module project against refpolicy source 3) Creating a project with missing build.conf is ref policy directory (and thus missing to project) 4) Other missing files in module or regular project 5)

Note: See TracReports for help on using and creating reports.