How to DDOS yourself
devblog.bu.mp
How to DDOS yourself
1–10 of 22 posts
Re: How to DDOS yourself
#2I guess just setting the phone to state to sending file while uploading the logs to the server was the solution. Is there a better way to solve this issue? The user did not put it as part of the article.
Re: How to DDOS yourself
#3So this is actually an Android/phone issue, not really your mistake.
The thing the developers will all have to learn in time, is that absolutely nothing is granted with Android. Until now, this usually only meant hardware features, since Google (supposedly) verifies it's OS on all phone models before granting them access to GApps (market, gmail, maps, etc...).
Re: How to DDOS yourself
#4[deleted]
Re: How to DDOS yourself
#5I guess just setting the phone to state to sending file while uploading the logs to the server was the solution. Is there a better way to solve this issue? The user did not put it as part of the article.
Meh, to me that's just band-aiding the problem. The core issue here is that they anticipate getting the log from each user approximately once every day or two (that's on average when people plug in their phones to charge). I would just keep track of the timestamp of the previous log upload, and simply ignore the Intent if it's within a certain threshold (say, less than 12 hours ago).
Re: How to DDOS yourself
#6[deleted]
Blocking off 4 /16 networks that were triggering a (self-induced) attack from 10s of thousands of devices sounds pretty distributed to me.
(I work at Bump and fought these very Zombies.)
Re: How to DDOS yourself
#7[deleted]
The "distributed" part can simply reference the number of systems involved, it doesn't have to span networks all over the world.
Re: How to DDOS yourself
#8I guess just setting the phone to state to sending file while uploading the logs to the server was the solution. Is there a better way to solve this issue? The user did not put it as part of the article.
Meh, to me that's just band-aiding the problem. The core issue here is that they anticipate getting the log from each user approximately once every day or two (that's on average when people plug in their phones to charge). I would just keep track of the timestamp of the previous log upload, and simply ignore the Intent if it's within a certain threshold (say, less than 12 hours ago).
Do you think it makes sense with the mobile architecture to have an application store its current state? This is obviously a more general question regarding mobile application architecture. This would specifically to be handle broadcast listeners performing conflicting actions.
Re: How to DDOS yourself
#9Testing software before shipping found to help reduce undesired behavior in the field, film at 11.
Also, unconditionally opening a connection before finding out if they even have data to shoot across?
Re: How to DDOS yourself
#10Testing software before shipping found to help reduce undesired behavior in the field, film at 11. Also, unconditionally opening a connection before finding out if they even have data to shoot across?
Buying every existing phone that is sold in reasonable volume across all major networks in all major countries and testing them individually on each release is probably not the testing plan I would go with.