Perock

Latest version: v0.2.2

Safety actively analyzes 623187 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

0.2.1

Bug fixes, refactor & improvements(44)

Attempts to fix some of issues mentioned at 44.
It involved changed to fix certain bugs or eliminate chances of them happening.
Whole source code refactor is needed to permanantly solve all problems

Changes
- Refactored attack classes by defining base attack class.
- Session and response are now never tried to be closed internally(42)
- Attack bytes classes removed as they were never used.
- Exception classes from previous commit applied to source code(42).
- Bugs fixes within runner module.

Future API and Implementation(36, 44)

Modules to be used for refactoring and changing perock API has been added.
They are similar to existing code but differ in that methods are static or class methods.
Methods are no longer tied to object such as 'success()'.

Modules added in this commit will change the way perock works.
Attack, bforce and runner classes will be removed after they are completed(decreased source code).
Existing modules are left to not break 'broote' library and fix bugs exposed to 'broote'.

Update tests(45)

- Tests were updated to match changes from previous commit.
- Tests were updated to match changes made added from previous weeks.
- Runner tests were updated with code from 'broote' library respository.

0.2.0

Fixed wrongly named methods of runner and bforce classes(39)

0.1.1

0.1.0

Bugs fixes & More features(33,34,38)

There were issues with bforce classes mostly being not sharing some functionality with runner classes.
Runner classes were mostly limited in what they can compared to what bforce classes are capable of.
Runners composites bforce object and their functionality depends on that bforce object they are compositing.

Bforce mostly did not expose methods for accessing its internal state which is disadvantage for runners.
Public methods were added for setting and geting state of bforce objects which were also added to runner.
It was duplicate proccess but it ensures that bforce objects will not be used directly as its code is ugly.

There were also bugs ithin bforce classes as referenced in each individual issues.
Some features were added including setting of maximum primary success items which limits success primary items.
Another one includes maximum primary success records which limits success records for each primarry item.
Excluded primary items were also added which allows setting primary items to be excluded.

Session and response closing are now handled by attack classes and no longer by bforce but it does close session.
Attack class will be used by bforce to close session but attack class if it wants it may not close session.
Its most better to let attack classes decide on how things are done rather bforce having to decide.

: There may be other features not included in this commit message.

0.0.4

0.0.3

Support for 'prodius' and 'fortable' libraries was added to perock.
The two libraries were developed based on this librarry(perock).
They are more matured and perform better than corresponding modules in perock.

Changes made were minimal as possible to avoid having to change many files.
The libraries are not compatiple with perock since the have lowercase classes.
Aliases were used to make the classes be imported as lowercase.

There are other things that made libraries incmpatible such as renamed functions.
Some portions had to be changed to match how that portion is defined in libraries.

Tests were also failing most of the time mostly integrated tests.
'forcetable' library had to be updated with new releases to fix certain bugs.
Currently all tests are doing well but there may be other compatibility issues.

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.