Google chrome didnt like this download at all, telling me its a virus.
WireEdit – A Full Stack WYSIWYG Editor for Network Packets
61–70 of 82 posts
Re: WireEdit – A Full Stack WYSIWYG Editor for Network Packets
#62Earlier quoted context omitted.
For starters, it looks like this could be an issue: Can I add support for stack Y myself? No but we’d be happy to talk about it. If this was FOSS, you could easily add support for your own stack rather than being at the mercy of their limited amount of time to work on it.
And who is really going to do that? Do I have time at my day job to port some network packet editor to the platform of my choice? Is management going to fund such an effort, or are they just gonna pay for the app?
Re: WireEdit – A Full Stack WYSIWYG Editor for Network Packets
#63Earlier quoted context omitted.
For starters, it looks like this could be an issue: Can I add support for stack Y myself? No but we’d be happy to talk about it. If this was FOSS, you could easily add support for your own stack rather than being at the mercy of their limited amount of time to work on it.
And who is really going to do that? Do I have time at my day job to port some network packet editor to the platform of my choice? Is management going to fund such an effort, or are they just gonna pay for the app?
Re: WireEdit – A Full Stack WYSIWYG Editor for Network Packets
#64Earlier quoted context omitted.
What assurances do we have that you'll live up to your privacy policy?
I'm afraid there is no such thing. Even open source products have critical security bugs as you may very well know. If you do just a bit of research you can find who I am, and where I live. Code is not obfuscated. This is the best I can do.
Except they get fixed without someone threatening to disclose them.
> If you do just a bit of research you can find who I am, and where I live.
What do you expect me to do with that information? I'm being honest: I don't really get what that information would do for me if I found your code was doing something wrong, unless I thought it was worth my time to file a lawsuit.
> Code is not obfuscated.
We have very different definitions of this term.
> This is the best I can do.
Examples exist which show this statement to be wrong.
Re: WireEdit – A Full Stack WYSIWYG Editor for Network Packets
#65Earlier quoted context omitted.
Without source why should we trust the privacy policy?
Presumably the crowd that a packet editor is targeted at knows their way around something like WireShark, and could easily monitor the software for phoning home. That's a pretty strong incentive to not do it.
Re: WireEdit – A Full Stack WYSIWYG Editor for Network Packets
#66Earlier quoted context omitted.
And who is really going to do that? Do I have time at my day job to port some network packet editor to the platform of my choice? Is management going to fund such an effort, or are they just gonna pay for the app?
I presume by 'Stack Y' they mean a network protocol not supported out of the box, rather than a platform the editor doesn't yet run on.
Re: WireEdit – A Full Stack WYSIWYG Editor for Network Packets
#67You should add the licence on the website. It's a nice concept but I'll start using it as soon as someone creates a FOSS clone.
>It's a nice concept but I'll start using it as soon as someone creates a FOSS clone. I like FOSS, and am grateful for the work open source engineers put into software, and I have also contributed, but this attitude right here where you wont even consider something because it's closed source? What's the point of that? Why shouldn't an engineer be paid? It's very difficult to capture value with open source software. P…
Q.E.D.
Re: WireEdit – A Full Stack WYSIWYG Editor for Network Packets
#68Re: WireEdit – A Full Stack WYSIWYG Editor for Network Packets
#69Re: WireEdit – A Full Stack WYSIWYG Editor for Network Packets
#70Earlier quoted context omitted.
>It's a nice concept but I'll start using it as soon as someone creates a FOSS clone. I like FOSS, and am grateful for the work open source engineers put into software, and I have also contributed, but this attitude right here where you wont even consider something because it's closed source? What's the point of that? Why shouldn't an engineer be paid? It's very difficult to capture value with open source software. P…
It is windows 7 only. So if anyone wanted to port it to OSX or Linux they would need to do a clean room implementation. Q.E.D.