[Boards: 3 / a / aco / adv / an / asp / b / biz / c / cgl / ck / cm / co / d / diy / e / fa / fit / g / gd / gif / h / hc / his / hm / hr / i / ic / int / jp / k / lgbt / lit / m / mlp / mu / n / news / o / out / p / po / pol / qa / qst / r / r9k / s / s4s / sci / soc / sp / t / tg / toy / trash / trv / tv / u / v / vg / vip /vp / vr / w / wg / wsg / wsr / x / y ] [Search | Home]
4Archive logo
You can never trust a computer:
If images are not shown try to refresh the page. If you like this website, please disable any AdBlock software!

You are currently reading a thread in /g/ - Technology

Thread replies: 51
Thread images: 8
File: 1454813739049.jpg (686 KB, 2048x1152) Image search: [iqdb] [SauceNao] [Google]
1454813739049.jpg
686 KB, 2048x1152
You can never trust a computer:

1. When you use proprietary software, there's no way to find backdoors in them

>Use free software

2. When you use free software, there can be bugs and also well hidden backdoors
(read Trusting Trust)

>Write your own software then

3. The library you link to may be compromised and even the compiler may add something malicious.

>Don't use the libraries then and write everything in assembly

4. The assembly code you write will use system interrupts, which again can have malicious code.

>FUCK YOU WRITE EVERYTHING IN MACHINE CODE

5. You can't trust the ISA of a CPU, because it may contain hardware backdoors which make machine instructions that you call do something malicious except the operation you wish them to do.

>DESIGN YOUR OWN HARDWARE FROM SCRATCH AND GTFO

6. Then you will have to fabricate your CPU somewhere and there may be an enemy agent injecting modifications to your CPU in the complicated fabrication process that has many steps.

There's nothing to save us, /g/. Information security doesn't exist, we're doomed.
>>
File: 1454706111793.jpg (275 KB, 1000x1500) Image search: [iqdb] [SauceNao] [Google]
1454706111793.jpg
275 KB, 1000x1500
bump
>>
File: 1454812277662.jpg (162 KB, 1280x852) Image search: [iqdb] [SauceNao] [Google]
1454812277662.jpg
162 KB, 1280x852
Anyone?
>>
I remember /g/ used to discuss botnets all the time, what the fuck happened?
>>
File: 1453853328802.jpg (273 KB, 960x686) Image search: [iqdb] [SauceNao] [Google]
1453853328802.jpg
273 KB, 960x686
>>
>>52963405
Noice
>>
Pen and paper
>>
>implying open source software doesn't have the same backdoors

They just change those snippet's text color to transparent.
>>
>>52963456
Damn that looks cozy as fuck.
>>
>>52963361
but it never existed?
Maybe with analog equipment, but thete was no encryption as strong as pgp, so?
Hardware security (big steel shed, vault) is still best!
>>
>>52963487
Turns out the botnet was good in bed, and seeing as the majority of /g/ are virgin autists, they just let the botnet fuck their boi pussy
>>
File: 1454350951458.png (57 KB, 500x500) Image search: [iqdb] [SauceNao] [Google]
1454350951458.png
57 KB, 500x500
>>52965246
> majority of /g/
wtf?
I thought the majority of /g/ were arch using ricers + gentoo (i know both of them are meme, so frog?)ebin
>>
>>52963361
>5. You can't trust the ISA of a CPU, because it may contain hardware backdoors which make machine instructions that you call do something malicious except the operation you wish them to do.
This one is true. Does anyone have the link to the article someone wrote about Intel doing this?
>>
>>52963456
This thread didn't work out because it was one of the millions iShill vs Lagdroid or other futile threads.
>>
File: 1432427984539.jpg (86 KB, 651x940) Image search: [iqdb] [SauceNao] [Google]
1432427984539.jpg
86 KB, 651x940
>>52965291
>>52965291
Why do you think arch users / ricers aren't virgin autists. Don't they go hand in hand?
>>
AMD is your friend. Literally no backdoors.
>>
you can counteract trusting trust https://www.schneier.com/blog/archives/2006/01/countering_trus.html
>>
>>52965374
what
the
fuck
is
pic related
>>
>>52965422
really? I don't know ... why would the not do the same as intel?
>>
>>52965449
Watch it, it's bretty gud: https://www.youtube.com/watch?v=XcySXoQLI5Q
>>
>>52963361
I don't trust my computer, I trust my hardware firewall.
>>
File: bmow.jpg (52 KB, 400x300) Image search: [iqdb] [SauceNao] [Google]
bmow.jpg
52 KB, 400x300
>>52963361
>not wiring your own cpu
stay pleb
>>
>>52965512
Hello, Ahmed.
>>
>>52965320
Bumping my own request
>inb4 >>>/wsr/
>>
File: :).png (65 KB, 480x359) Image search: [iqdb] [SauceNao] [Google]
:).png
65 KB, 480x359
saving this thread
>>
>>52964125
>>52964728
It's from a cozy thread. I don't have any /g/ pics at the moment.

>>52964667
Inconvenient for photos, audio etc.

>>52964718
yeah...

>>52964879
>>52965246
>>52965358
You're right.

>>52965320
Adam Waksman wrote a phd thesis about hardware backdoors in CPUs, it's available on his homepage.

>>52965422
Because they sold their HQ, so they really have no doors, no windows, no anything. Good point.

>>52965505
Have you verified that your hardware firewall's integrated circuits really do what they should?

>>52965512
It's inefficient as fuck to process important information using such hardware.
>>
Anon go put your tin foil hat back on and sit in the corner.
>>
>>52965731
fuck no! i don't have a corner!
>>
>>52964879
I get a feeling you're mootwo, he writes in a specific way just like you.
>>
>>52965483
Thanks senpai. Actually only had the picture, hadn't seen the film but it's pretty sick dude.
>>
>>52965739
Just move your mouse to the corner of the screen.

It's the same thing for autists.
>>
>>52965754
Hiroshima has broken English and half his sentences don't actually make sense.

It can't be him.
>>
>>52965845
>Hiroshima has broken English
I have bad news for you...
>>
>>52963361
>1. When you use proprietary software, there's no way to find backdoors in them
reverse engineer it

>2. When you use free software, there can be bugs and also well hidden backdoors
>(read Trusting Trust)
well write your own then

>3. The library you link to may be compromised and even the compiler may add something malicious.
welp

>4. The assembly code you write will use system interrupts, which again can have malicious code.
well yeah but so what

>5. You can't trust the ISA of a CPU, because it may contain hardware backdoors which make machine instructions that you call do something malicious except the operation you wish them to do.
I haven't seen an ISA slot in years didn't PCI replace that shit wasn't it only 8 bit or something

>6. Then you will have to fabricate your CPU somewhere and there may be an enemy agent injecting modifications to your CPU in the complicated fabrication process that has many steps.
are you crazy designing a cpu is very hard

I'm sorry what was this thread about and who am I quoting

>There's nothing to save us, /g/. Information security doesn't exist, we're doomed.
Oh.
>>
>>52965939
>I haven't seen an ISA slot in years didn't PCI replace that shit wasn't it only 8 bit or something
/v/ everybody
>>
>>52963361
Use proprietary software. Windows 10 and chrome and shit. Embrace BOTNET. We join them.

Do not be afraid. Assimilation will start few centuries from now.
>>
>>52963456
>>52963361

Keep posting cozy shit like this.

I don't care about your stupid code, though.
>>
>>52965939
>reverse engineer it
Did you read on Trusting Trust?
Here, for you lazy ass: >>52965435
>>
>>52963456
Post more of these photos>>52963456
and this>>52963361
>>
>>52963361

I guess you'll have to stop using computers then.

If you would like to join the other 99.9% of us that don't have some conspiratard bullshit plugged up our assholes, we will be constructing cities and fusion reactors in the time being.

Have fun with your memes.
>>
>>52965483
was laughing at first but holy shit that's really fucking deep
thanks for the link
>>
>>52965691
>It's from a cozy thread
Link to the thread in the archive pls?
Which board was it in?
>>
>>52963361
>>52963405
>>52963456
>>52965691
>>52970094
http://fgts.jp/_/search/image/za4tZq6oiKwpL6ewi_cN6A/

Which one was it?
>>
Or you can just blacklist the botnets on your connection
>>
>>52965483
Looks like a Harmony Korine movie
>>
>>52963361
> 5. You can't trust the ISA of a CPU, because it may contain hardware backdoors which make machine instructions that you call do something malicious except the operation you wish them to do

Well, you can verify that an instruction works as intended. If you know what a CPU does, you know what your software does as well. This also applies for more complex mathematical routines.
You can for instance create a crypto routine and verify its output. If it's correct, you can expect it to work correctly everytime.
>>
>>52971485
How do you know that nothing is sent to NSA by your hardware?
>>
>>52971553
Intercepting traffic on a hardware level is really easy.
>>
>>52971566
Except if the hardware you use to intercept is corrupted too.
>>
>>52963361
Paper, books, old computers, consoles and phones, MP3 players, faraday cages.

Your well came.
>>
>>52965512
'mire my point-to-point handwired botique build
Thread replies: 51
Thread images: 8
Thread DB ID: 516225



[Boards: 3 / a / aco / adv / an / asp / b / biz / c / cgl / ck / cm / co / d / diy / e / fa / fit / g / gd / gif / h / hc / his / hm / hr / i / ic / int / jp / k / lgbt / lit / m / mlp / mu / n / news / o / out / p / po / pol / qa / qst / r / r9k / s / s4s / sci / soc / sp / t / tg / toy / trash / trv / tv / u / v / vg / vip /vp / vr / w / wg / wsg / wsr / x / y] [Search | Home]

[Boards: 3 / a / aco / adv / an / asp / b / biz / c / cgl / ck / cm / co / d / diy / e / fa / fit / g / gd / gif / h / hc / his / hm / hr / i / ic / int / jp / k / lgbt / lit / m / mlp / mu / n / news / o / out / p / po / pol / qa / qst / r / r9k / s / s4s / sci / soc / sp / t / tg / toy / trash / trv / tv / u / v / vg / vip /vp / vr / w / wg / wsg / wsr / x / y] [Search | Home]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.
This is a 4chan archive - all of the shown content originated from that site. This means that 4Archive shows their content, archived. If you need information for a Poster - contact them.
If a post contains personal/copyrighted/illegal content, then use the post's [Report] link! If a post is not removed within 24h contact me at [email protected] with the post's information.