protobuf-grammar
wireshark
| protobuf-grammar | wireshark | |
|---|---|---|
| 1 | 28 | |
| 25 | - | |
| - | - | |
| 10.0 | - | |
| almost 5 years ago | - | |
| BSD 3-clause "New" or "Revised" License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
protobuf-grammar
-
Finally: A Language Specification for Protocol Buffers
bufdev brought up some good concerns on that issue:
> This as a community project defeats the purpose of creating a definitive grammar/spec that protocolbuffers/protobuf holds itself to - without that component, having a community-written spec is no improvement over the current situation from what I can see, and in fact could create even more fragmentation and confusion, just my two cents.
It looks like the protobuf team created a repo intended for this (https://github.com/protocolbuffers/protobuf-grammar), perhaps the spec could be contributed there, including a review/blessing from the official team.
wireshark
-
Wireshark is showing me "unknown" on some of the HTTP2 headers
https://gitlab.com/wireshark/wireshark/-/issues/19297 ? maybe related
-
GNS3 ethernet cloud error
Might be related to this: https://github.com/nmap/npcap/issues/628 https://gitlab.com/wireshark/wireshark/-/issues/18414
-
Need help running Wifite on Parrot OS with UTM on MacBook M1 chip*
Another problem might be that M1 mavs might not (but probably is) supporting monitor mode. While wireshark is currently working on a native version it ptobably supports. But the ecosystem (M1/M2) is fairly New and might require some tweaking/configuration to enable monitor mode
- Wireshark doesn't show data as a text, just raw bytes
- Could be there two identical MAC adresses?
-
Hello Hello, tried to use wireshark but have a little problem
Rather than simply running Wireshark via "sudo" you should really follow the instructions described here, since doing that minimizes the number of processes running with elevated privileges, which is a good thing. There's a link on that page to specific instructions for Debian-based distros, which I'd expect to include Mint. Related to this, I'm pretty sure all the Wireshark installations I remember doing in the past few years on various Linux platforms via the appropriate package mangers have popped up a window on first launch describing the appropriate measures to take to allow non-root users to capture traffic, which were pretty much just a summary of the steps described in the second link I mentioned, but I'm not a heavy Linux user so my experience with this is a bit limited.
-
Need help identifying and labeling network cables
I then pasted all this into Excel and using LEFT, RIGHT I pared the information in the cell to their own cells. So now I have Interface, VLAN, MAC, and OUI columns. I then took the Wireshark database and pasted it onto a different sheet. I then used VLOOKUP and made a column where I resolved the OUI to its corresponding Vendor.
- Issue with the endpoint statistics screen
- Finally: A Language Specification for Protocol Buffers
- Anti-vaxxer thinks we're all phones now
What are some alternatives?
ASRock-B460M-Pro4-OpenCore-Hackintosh - Hackintosh OpenCore EFI Bootloader for ASRock B460M Pro4 (Intel Comet Lake)
wifite2 - Rewrite of the popular wireless network auditor, "wifite" - original by @derv82
npcap - Nmap Project's Windows packet capture and transmission library
intellij-protobuf-editor - Protocol Buffers for IntelliJ-based IDEs
macchiato - MAC spoofing with a restricted range of OUI prefixes
ImportExcel - PowerShell module to import/export Excel spreadsheets, without Excel
Pyrit
buf - The best way of working with Protocol Buffers.
Protobuf - Protocol Buffers - Google's data interchange format
rubinius-website-archive