@bluebaytuna said:
Hi! Anyone I can PM regarding this challenge? The API of the “website” keeps on returning an error message. I’ve double checked the parameters and they seem to be the correct ones. Is there anything I’m missing?
I think I am at the same point. Have you any news about this?
Took me quite a while, first time I’ve done anything like this. Really fun challenge. The hard part is just learning how to use wireshark imo, it’s such a complex tool with so many capabilities that it can be difficult to figure out how to use them and what they do.
If you’re at the spot that I was stuck on for a while, and most other people seem to be stuck on, where you think you’ve found out what was stolen, but only have 4 lines or so, you’re on the right track. Refer to the link in @TazWake’s previous post and research how to perform this action in wireshark. There’s some pretty good tutorials out there.
I am looking at those Bro log files but I can’t find anything that would stand out… I am obviously not suppose to go through all the 13000 lines manually. HTB is killing me Any hints? I know pretty well how to search stuff in wireshark but I’m kind of lost. Hard to search if no ideas what to look for. Any hints?
Got it! Man… Once I got over the decryption hurdle if was like 2 minutes… That’s me… I get stuck on some trivial technicality. But hey, I learned something new. I never had to decrypt stuff in Wireshark before.
@TazWake said:
I still havent managed to get anywhere with this.
Is there anyone out there who has solved it and doesn’t mind giving me a tip or two about why I dont seem to be able to get wireshark to decrypt the vital SSL traffic?
I can see the cleartext suspicious traffic on the next stream, and then a huge amount of traffic which looks like normal web browsing. But nothing I do seems to be able to assign the private key to the traffic I want it to decrypt.
For me, the best tip I can give is dont try to read the streams - nothing I did make that work. However, there are other things you can do in WireShark to get it to dump data to a folder, which you can then analyse.
Just spent a lot of time on this one just to figure out Wireshark 2.4.6 and 3.0.0 on OS X neither would decrypt correctly. 2.6.7 worked fine with exact same settings as other 2 versions so I don’t think it was misconfiguration. 2.6.6 in Kali worked fine too, didn’t try any other versions. Once decrypt worked, the flag was obvious in expected format.
ya I have figured it was an issue I almost wondered why it was not working and I kind of figured the bundle was needed to be modified to get the decryption working once I noticed I wasn’t getting decryption I just put it aside I am glad you cleared up which version worked I will do a reinstall of that version later
Finally I got it and this worked with the last version of Wireshark on Win10 also in Kali linux. check out very well advance preferences on Wireshark, if you need any help PM… Cheers.