Closed mbenkmann closed 9 years ago
From mux2...@gmail.com on March 13, 2013 10:16:28
Hmm. Even though the sending system was a server it looks like the message were coming from the gosa-si-client on that server. It's strange that a gosa-si-client from a server should not register at its own server but maybe its server has crashed, who knows. In any case, to fix this issue, it may be enough to change the code in process_msg.go so that a ping is not only sent when an undecryptable message is received from a client we believe to be ours but always. On the other hand it can't hurt to send a new_server message to the server port of the spammer.
From matthias...@gmail.com on May 08, 2013 09:12:37
Retargeting tickets unrealistic for MS 4 timeframe to MS 5
Labels: -Milestone-4 Milestone-5
From matthias...@gmail.com on July 06, 2013 02:34:37
Retargetting issues unrealistic for MS 5 timeframe to MS 6
Labels: -Milestone-5 Milestone-6
From mux2...@gmail.com on August 23, 2013 02:09:18
Stub is already there: message/process_msg.go:tryToReestablishCommunicationWith()
From mux2...@gmail.com on August 23, 2013 02:20:11
If a new_server message is received by a go-susi with config.RunServer = false, it should send a here_i_am to its server to make it send out new_foreign_client messages so that other servers (including the sender, hopefully) learn that the recipient is not a server. This also serves to re-establish communication when go-susi's own server has lost the key. In ClientUpdate()/ServerUpdate() make sure to remove the respective IP:HOST address from the other database to deal with client<->server conversions.
From mux2...@gmail.com on August 23, 2013 06:13:26
ATTENTION! When receiving a new_foreign_client, ONLY delete the address from the serversdb if
From mux2...@gmail.com on August 27, 2013 05:45:37
message.ConfirmRegistration() is already implemented
From mux2...@gmail.com on March 13, 2013 18:09:36
I'm seeing a series of undecryptable messages from a peer. go-susi should whenever it gets an undecryptable message send a ping to the client port and a new_server to the server port.
Original issue: http://code.google.com/p/go-susi/issues/detail?id=81