@AnnonomusPerson I don't think that's possible, really. Building computer systems smartly would not mitigate security issues. The majority of security issues come from stupidity of the user and/or developer, and is hard to mitigate even from an architectural change.
Though some types of security issues could be mitigated. Use after free errors and all can be fixed with smarter memory management. I'm currently helping out on a browser in Rust (Servo) that is built to be memory safe but extemely multithreaded (Rust has a very efficient way of being memory safe)
@ManishEarth True, but I'm just saying that a lot of easy stuff could be avoided (like SQl injection, maybe less risk of session hijacking, harder to launch a XSS attack, etc.)
I doubt XSS could be fixed. Ultimately, you have to get responsibilities straight. XSS is a fault of the website, and not the browser. It can't be fixed by browsers. Except little holes which were patched up years ago.
@HamZa So you know how you can send a file with cURL and '@' . $file, right? Does this work with URL's? Like where $file = "www.google.com/agoodimagehere.jpg?
Or would it have to be '@' . file_get_contents($url)?
I know this to be true:
... you can post a file that is already on the filesystem by prefixing the filepath with "@".
However, I'm trying to POST a file with cURL that's not local. It's stored on some other URL. Let's just say this photo is Google's logo (it isn't). The URL of that is https...
Sounds like suffle your array is beter than generating random numbers :
int[] ShuffleArray(int[] array)
{
Random r = new Random();
for (int i = array.Length; i > 0; i--)
{
int j = r.Next(i);
int k = array[j];
array[j] = array[i - 1];
array[i - 1] = k;
}
return array;
}...