Gotcha. I think I have all the info to do the commit now. I
appreciate the guidance everyone.
-- Adam
On Sat, Jun 6, 2015 at 11:17 AM, Gerald Combs wrote:
> Short answer: Go to https://code.wireshark.org/review/login/ and log in
> using your Google, GitHub, or an OpenID account.
>
> The long a
Short answer: Go to https://code.wireshark.org/review/login/ and log in
using your Google, GitHub, or an OpenID account.
The long answer involves OpenID, OAuth, a group in very large company
deprecating one of its authentication services, a different group in
*that same very large company* refusin
Anil,
Thanks for the break down. One final question, how do I set up an
account to submit code.wireshark.com, or do I even need too? Thanks,
-- Adam
On Sat, Jun 6, 2015 at 3:10 AM, Anil wrote:
> Adam,
>
> I recently submitted some code to wireshark. I found that the process is
> simple. Can y
On Fri, Jun 5, 2015 at 10:09 PM, Adam Pridgen <
adam.prid...@thecoverofnight.com> wrote:
> Hello,
>
> Hi Adam,
> I would like to make a minor code contribution that allows TLS1.1/1.2
> traffic to be decrypted with a known PMS. I have read over the
> Gerritt submission process twice, and I am no
Adam,
I recently submitted some code to wireshark. I found that the process is
simple. Can you share the link where you found the instructions?
This is what I do (This may have some mistakes, but it worked).
1) git clone
git clone https://code.wireshark.org/review/wireshark
2) Install the
Hello,
I would like to make a minor code contribution that allows TLS1.1/1.2
traffic to be decrypted with a known PMS. I have read over the
Gerritt submission process twice, and I am not sure how I can submit
my changes back to Wireshark.
For the time being, I have posted them up to GitHub
(http
