LeBron Posted July 19, 2015 Share Posted July 19, 2015 How do you protect yourself from getting infected with shit? Like, let's say someone puts a rat, k logger or virus in a .jar and upload it to SDN, how do you find it without it rek'ing your computer? Probably a dumb af question, with a simple answer so please go easy on me Quote Link to comment Share on other sites More sharing options...
Deceiver Posted July 19, 2015 Share Posted July 19, 2015 I believe the Devs + Eric (SDN Manager) check through the scripts to check for malicious code. As well, scripts aren't instantly uploaded to the SDN, they need to be approved, which is why there is a wait like ~12 hours before the updates are 'pushed'. 1 Quote Link to comment Share on other sites More sharing options...
Foed Posted July 19, 2015 Share Posted July 19, 2015 Pretty sure the client won't allow that to happen.. Quote Link to comment Share on other sites More sharing options...
Khaleesi Posted July 19, 2015 Share Posted July 19, 2015 (edited) Nothing will get pushed to SDN before the SDN manager takes a look at the code. We(Scripters) push our scripts to some kind of "buffer" SDN. The devs and script manager can see our updates inside this "buffer" Once he approves the release/update, he pushed it to SDN. That's why it can take severals hours to approve some updates Khaleesi Edited July 19, 2015 by Khaleesi 1 Quote Link to comment Share on other sites More sharing options...
Botre Posted July 19, 2015 Share Posted July 19, 2015 You don't send a jar to the SDN, you send source code to be compiled. The source code is checked for compilation errors and malicious content by the SDN manager(s) (probably a mixture of software-assisted human checking and detection software). Quote Link to comment Share on other sites More sharing options...
Apaec Posted July 19, 2015 Share Posted July 19, 2015 As botre said, you 'send in' the source. Picture the source as just writing on a page... it cannot harm anyone until you read (run) it. There's no way anything malicious can get onto the SDN. However no scripter is stupid enough to submit malicious code onto the SDN to risk their rank, profits, friends, customers and wellbeing well, except from maybe @Eliot apa 4 Quote Link to comment Share on other sites More sharing options...
Definite Posted July 19, 2015 Share Posted July 19, 2015 As botre said, you 'send in' the source. Picture the source as just writing on a page... it cannot harm anyone until you read (run) it. There's no way anything malicious can get onto the SDN. However no scripter is stupid enough to submit malicious code onto the SDN to risk their rank, profits, friends, customers and wellbeing well, except from maybe @Eliot apa apa more like kappa Quote Link to comment Share on other sites More sharing options...
