Skip to content

Commit

Permalink
New release: v1.0
Browse files Browse the repository at this point in the history
  • Loading branch information
airween committed Sep 25, 2020
1 parent b932601 commit 2c7ea32
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion CHANGES
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
v1.0 - YYYY-MM-DD
v1.0 - 2020-09-25
-----------------
* Entire code base has been rewritten
* see README.md for detailed changes
Expand Down
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ The module is published as a pip3 module.
**Method 1** You can install it using:

```
pip3 install msc-pyparser==0.3
pip3 install msc-pyparser==1.0
```

That will install it system-wide.
Expand Down Expand Up @@ -189,7 +189,7 @@ The `MSCParser` class is a wrapper for Ply's `parser` object. The parser object
Here is a simple example:

```python
python3
$ python3
Python 3.8.5 (default, Aug 2 2020, 15:09:07)
[GCC 10.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
Expand Down Expand Up @@ -828,7 +828,7 @@ Actually, there isn't any know bug.
Testing rulesets
================
There are four set which has tested: CRS (of course), Comodo WAF rules, Atomicorp and TrustWave sets. All of them are parsable, but the comparison is a bit difficult. The reason is simple: `msc_pyparser` drops the control tokens and identations. Eg. if the rule uses mixed indentations, that will be replaced by a fix indent string (can be passed to writer class). Or if the rule uses `,` as variable separator, eg `ARGS,ARGS_NAMES`, then the written rules will have `|`. Action list will always quoted, eg: ` ...t:none` will be `... "t:none"`.
There are four set which has tested: CRS (of course), Comodo WAF rules and Atomicorp sets. All of them are parsable, but the comparison is a bit difficult. The reason is simple: `msc_pyparser` drops the control tokens and identations. Eg. if the rule uses mixed indentations, that will be replaced by a fix indent string (can be passed to writer class). Or if the rule uses `,` as variable separator, eg `ARGS,ARGS_NAMES`, then the written rules will have `|`. Action list will always quoted, eg: ` ...t:none` will be `... "t:none"`.
There are four script in the `examples/` directory to help the reading and writing of each set:
Expand Down
2 changes: 1 addition & 1 deletion msc_pyparser.py
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
import os.path
import glob

__version__ = "1.0b"
__version__ = "1.0"

class MSCLexer(object):
"""Lexer class"""
Expand Down
2 changes: 1 addition & 1 deletion setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@
""",
python_requires=">=3",
license="""GPLv3""",
version = "1.0b",
version = "1.0",
author = "Ervin Hegedus",
author_email = "[email protected]",
maintainer = "Ervin Hegedus",
Expand Down

0 comments on commit 2c7ea32

Please sign in to comment.