Well I think that if we should integrate your patch, we need a system to test the code on.
If it's possible, could you talk to somebody to see if they are willing to give some information about how to set this up? I never heard of NetConf before, and I don't know what it's used for.
Is this the NetConf you are referring to: The Network Configuration Protocol,
NETCONF, is an IETF network management protocol.
Do you know of any open source projects that specifically targets this protocol? Because this seems to be on a layer on top of SSH (or others). Like sending HTTP requests over an SSH tunnel, so I'm not sure if this patch is
formally valid for this particular project.
If this is the case, and it's not valid for this project, I can leave the patch up, and later make a reference to it for those who need NetConf compatibility. But if you are basing your project on this compatibility layer, and are willing to maintain the
patch if any problems should arise, I see no evil so to speak.
The reason I pointed out Formally, is that this is a pure SSH client project. Proxy servers isn't supported as of yet (this is one of my ToDo's thats lagging seriously behind) , so you can't proxy via a ssh tunnel to a HTTP(S) server. Nobody except me has
given this feature any interest, so it's kind of low on the priorities. If this is a possible solution you can +1 the
You could create a project here on CodePlex where you provide a library for this protocol, if I have the time I would like to contribute, both on the core of it and possibly a SSH.Net compatibility layer of sorts.
I'm not against this patch, and it's not up to me if this patch should be applied. I'm just letting you know my perspective on this patch and this project.