Description

IDs are being repeated. Not sure if this is intended or a bug

Steps to Reproduce

1. Start a fresh session and do some network calls. Notice the ID numbers in Domains tab are increasing.
2. Save the session to file.
3. Load the session.
4. Do some network calls. Notice the ID numbers in the Domains tab start from 1, clashing with the old IDs, instead of the next biggest ID we would expect.

Current Behavior

ID counter are reset to 1 in a saved Proxyman session file, instead of resuming from the next biggest ID currently in the session.

Expected Behavior

IDs should not clash with existing IDs but should continue where it left off.

Environment

• App version: e.g Proxyman 3.1.3
• macOS version: e.g macOS 12.6.1

Ah ok got it then I will sort by time instead. Thanks for confirming.

Description

IDs are being repeated. Not sure if this is intended or a bug

Steps to Reproduce

1. Start a fresh session and do some network calls. Notice the ID numbers in Domains tab are increasing.
2. Save the session to file.
3. Load the session.
4. Do some network calls. Notice the ID numbers in the Domains tab start from 1, clashing with the old IDs, instead of the next biggest ID we would expect.

Current Behavior

IDs are reset to 1 in a saved Proxyman session file.

Expected Behavior

IDs should not clash with existing IDs but should continue where it left off.

Environment

• App version: e.g Proxyman 3.1.3
• macOS version: e.g macOS 12.6.1

Has this been fixed?

The verifier is throwing signature invalid, but it catches its own error and throw verifying failed instead, printing Jose swift error 9.

Instead of nesting the throw calls, can we flatten the calls? Seems like no reason to catch its own error.

I don’t see A*GCMKW as the enum when creating a JWE. Is this planned to be added?

Version(s) affected

3.1.2

Description

I followed the JWE Creation guide and its similar except the algorithms used is A256GCMKW with A256GCM. I’m unable to validate it.

It is able to encrypt and decrypt the payload by itself, but when I tried a variety of other libraries and none can decrypt this library’s JWE, and this library’s JWE can’t decrypt the JWEs made by other libraries. I tried a few libraries of different platforms and they all can encrypt and decrypt JWEs made by/for each other.

Is it possible to look further into this combination? Or is there something I am missing from the guide and using it wrongly?

How to reproduce

Just follow the JWE creation document and set the strings for alg to A256GCMKW and enc to A256GCM.

Possible Solution

No response

Additional Context

No response