Raphael Ahrens

Adding a serde feature for PublicKey, SecretKey and KeyPair

2

Hi, would you be open to the idea of adding a feature for serde serialization to the crate?

documentation improvemnt for algorithms in petgraph::algo::isomorphism

5

### Summary The documentation for all algorithms in petgraph::algo::[isomorphism](https://docs.rs/petgraph/latest/petgraph/algo/isomorphism/index.html#) is vague in regards to multigraphs. ### Motivation For all functions there is the statement "The graphs should not be multigraphs.",...

[bug] The plugin fails to load the stores session, when /home or the workspace path is a symlink

3

**Basic checklist** - [ x] I have read the README - [ x] I have read the wiki - [ x] I have read `:h session`, `:h mksession`, and `:h...

Replaced AC22 with AC23 and AC24

7

As mentioned in #239 AC22 Credential Aging review the threat AC22 Credential Aging was not helpful. This commit replaces AC22 with two new threats AC23 Credential Disclosure and AC24 Hardcoded...

Alternative format for threat lib for better readability and editing

5

So I looked through the threats recently and again and again I find it difficult to read through the JSON document. What bothers me the most is the combination of...

Replaced the encryption with age

12

The old encryption protocol has some flaws. In this commit the encryption is replaced by the age library.

Refactor of the `serialize` and `to_serializable` function

2

This commit tries to tackle #268 and rewrite the `serialize` function to handle less class specific cases and move it into the single dispatch function `to_serializable`.

In a recent PR https://github.com/OWASP/pytm/pull/263 the `to_serializable` function misbehaved and serialized a set of strings into the string `"{'pytm/threatlib/threats.json'}"`. The issue is caused by the default `to_serializable`, which is used...

Applying custom threats only to specific elements.

1

> Thanks guys for your comments, I'll see what I can share in terms of threat library with putting my org at risk. > > Usually I run into another...