Solved!
Go to SolutionDirective Parse Issue
I'm having problems with the following directive:
<<\>>
+skip: *.xcg
+skip: G:\DataFiles\XSMFiles\Messages
+skip: G:\DataFiles\XSMFiles\RemoteWebRequests
+skip: G:\DataFiles\XSMFiles\XCG
I receive the following errors:
-2:(pid 3908): bad dir spec, line 0 of C:\Program Files\Legato\nsr\tmp\sd000004
C:\Program Files\Legato\nsr\tmp\sd000004 line 0: illegal token
-2:(pid 3908): ignoring illegal external ASM name `>' in C:\Program Files\Legato\nsr\tmp\sd000004
C:\Program Files\Legato\nsr\tmp\sd000004 line 2: parse error
C:\Program Files\Legato\nsr\tmp\sd000004 line 3: parse error
C:\Program Files\Legato\nsr\tmp\sd000004 line 4: parse error
I'm not sure what the issue is. I appreciate any assistance. I was having trouble making and progress using the manuals.
Aaron
<<\>>
+skip: *.xcg
+skip: G:\DataFiles\XSMFiles\Messages
+skip: G:\DataFiles\XSMFiles\RemoteWebRequests
+skip: G:\DataFiles\XSMFiles\XCG
I receive the following errors:
-2:(pid 3908): bad dir spec, line 0 of C:\Program Files\Legato\nsr\tmp\sd000004
C:\Program Files\Legato\nsr\tmp\sd000004 line 0: illegal token
-2:(pid 3908): ignoring illegal external ASM name `>' in C:\Program Files\Legato\nsr\tmp\sd000004
C:\Program Files\Legato\nsr\tmp\sd000004 line 2: parse error
C:\Program Files\Legato\nsr\tmp\sd000004 line 3: parse error
C:\Program Files\Legato\nsr\tmp\sd000004 line 4: parse error
I'm not sure what the issue is. I appreciate any assistance. I was having trouble making and progress using the manuals.
Aaron
855
0
Posted June 4th, 2009 07:00
Thanks, I'll give that a try. That would mean I couldn't use the same directive for all servers since they have different drive letters, but that's ok. Not a big problem.855
0
Posted June 4th, 2009 07:00
I don't know if <<\>> will work under Windows, you have to use drive letters, like < >855
0
Posted June 4th, 2009 08:00
Change <<\>> to <> and it will work.856
0
Posted June 4th, 2009 08:00
Change << \ >>
to
<< forward slash character >>
For some reason the forum removes forward slashes....?855
0
Posted June 4th, 2009 08:00
Change <<\>> to <> and it will work - that is a forward slash in the second part if it doesn't show up again....856
0
Posted June 5th, 2009 06:00
Hmm, interesting that the forward slash is blocked in forum posts. I've seen it used for directory traversal attacks in the URL, but not for SQL Injection
I'll try the slash. Changing to the drive letter didn't work.856
0
Posted June 5th, 2009 08:00
Strange, especially when a backslash works; the second attempt I tried escaping it and both characters vanished856
0
Posted June 5th, 2009 19:00
Sorry just checking
<< \/ >>856
0
Posted June 5th, 2009 19:00
Sorry one more time
<< // >>
pbina
75 Posts
1233
0
Posted June 5th, 2009 19:00
<< forward-slash >> works for Windows as well and it means all drives. But your configuration is not correct somewhere else too.
"+skip: G:\DataFiles\XSMFiles\Messages" This does not work and you have to configure your dirctive as follows:
<< forward-slash >>
+skip: *.xcg
<< "G:\DataFiles\XSMFiles\Messages" >>
+skip: *.*
<< "G:\DataFiles\XSMFiles\RemoteWebRequests" >>
+skip:*.*
<< "G:\DataFiles\XSMFiles\XCG" >>
+skip:*.*
Regards...