looks like pymodbus was heavily changed hence creating import issues with the attack scripts

[hakankusne]

[jseidl]

Oh darn. Will take a look into it this week. Thanks for the heads up

…

On Jan 28, 2018 23:29, "Hakan Küsne" ***@***.***> wrote: [image: capture] <https://user-images.githubusercontent.com/11094310/35498414-73132db2-04ce-11e8-9404-701b3080cde1.PNG> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#8>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AARRofzi2CGQvAIKlwrdAyqmSEYwHZydks5tPXNxgaJpZM4RwKuv> .

[mloom00]

@jseidl Any updates on these attack scripts?

[jseidl]

Hi, sorry for the delay. I'm waiting on some changes by a contributor to accept his pull request so I can then address this issue. Hope to have this back working ASAP. Cheers

…

On Tue, Apr 3, 2018 at 9:53 AM, Michael Loomis ***@***.***> wrote: @jseidl <https://github.com/jseidl> Any updates on these attack scripts? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AARRobEWgBmhn2ZAdyw7mUFaFoHG3TBCks5tk6kjgaJpZM4RwKuv> .

[Isaac-RAL]

Hello,
I am getting thesame import error "no module named modbus".
any new updates?

[setsecurity]

move the attack script 1 directory back, then run them.

[gilzin]

Any news regarding the virtual plant?