chrisdutz commented on issue #2173: URL: https://github.com/apache/plc4x/issues/2173#issuecomment-3067951828
Generally, I would say you'd be on the right track. However, observing tls secured connection via wireshark will not help unless you can provide the session key. However, I had a gut feeling that Beckhoff might have done something more sensible than Siemens with s7comm Pluss, where they mixed in the tls in the middle between multiple layers of the protocol. Beckhoff seems to simply use tls secured tcp and tunnel ordinary ads via that. In theory you wouldn't need to adjust anything in the mspec. Also, should the protocol code most probably not need changing. I could imagine implementing a new transport should be enough. With that something like ads:tls-tcp://hostname... Could be enough. A quick check showed me that netty generally has this available. But regarding your other questions: yes you were correct. Mspec -> src/main/generated src/main/Java is not automatically updated. If you need to change the mspec in a way that breaks implementations in other languages, you would create a new version of the mspec and use that. This way we don't have to disable drivers in other languages til someone has the time to fix things. Hope that helps as a starting point. If you have questions, feel free to ask. I'm always happy to help that way. I guess I'd implement it for something round 600€ (assuming my research during the first coffee of the morning wasn't compketely wrong 😂) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@plc4x.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
