Nothing you wrote contradicts the observation that it’s easier to apply for a job and get it than to construct a full blown company which needs to be acquired. If there are already 99 ‘spies’ at Google, there’s hardly need for such elaborate schemes.
mina86
joined 1 week ago
The thread linked by the OP is Jarkko Sakkinen (kernel maintainer) seemingly saying “show your work, your patch is full of nonsense” in a patch submitted for review to the Linux kernel.
That’s not what he’s saying. He’s saying: ‘You’re using terms which aren’t that familiar to everyone. Could you explain them?’
Another interesting part is that HTML5 supports embedding SVG. That is, you can put SVG code directly in your HTML5 document and it’s going to render correctly. You can also style it through your website’s CSS file and manipulate the elements via JavaScript.
Though as others pointed out, it’s technically not HTML but XML. For
example, you have to close all the elements and quote all the
attribute values. But when you embed it inside a HTML document, those
rules get relaxed to adhere with HTML. (I.e., you cannot write
<circle r=5> in SVG (it must be <circle r="5" />) but you can when
you embed it in HTML).
Which is why I haven’t wrote ‘EOF character’, ‘EOT’ or ‘EOT character’. Neither have I claimed that \x4 character is interpreted by the shell as end of file.
Edit: Actually, I did say ‘EOF character’ originally (though I still haven’t claimed that it sends EOF character to the program). I’ve updated the comment to clear things up more.
Sure, though I advise against it. The following C program can do that:
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
int main(int argc, char **argv) {
if (argc < 2) {
fprintf(stderr, "usage: %s <command> <args>...", argv[0]);
return EXIT_FAILURE;
}
printf("Executing");
for (int i = 1; i < argc; ++i) {
printf(" %s", argv[i]);
}
puts("\nPress ^C to abort.");
sleep(5);
if (setuid(0)) {
perror("setuid");
return EXIT_FAILURE;
}
execvp(argv[1], argv + 1);
perror(argv[1]);
return EXIT_FAILURE;
}
As seen in:
$ gcc -O2 -o delay-su delay-su.c
$ sudo chown root:sudo delay-su
$ sudo chmod 4750 delay-su
$ ./delay-su id
$ id -u
1000
$ ./delay-su id -u
Executing id -u
^C to abort
0
This will allow anyone in group sudo to execute any command as root.
You may change the group to something else to control who exactly can
run the program (you cannot change the user of the program).
If there’s some specific command you want to run, it’s better to
hard-code it or configure sudo to allow execution of that command
without password.
view more: next ›
Everything you’re describing is further speculation and unfalsifiable statements for events which already have a simpler explanation. That’s a tell-tale sign of a conspiracy theory.
Google buying the company as some kind of plot to get spies into Google requires more assumptions than Google buying the company for the technology (as it has done with plethora of other companies). If Google is somehow complicit in it, they could just hire those people directly. And if it’s all covert operation, Israel is capable of training and coaching their spies to pass Google’s interviews. Google interviews aren’t trivial, but it’s also not some super-elite company which hires only the top 0.01% of software engineers.
If you want to convince me otherwise, you need to demonstrate why your explanation is more likely than the obvious one.