[ / / / / / / / / / / / / / ] [ dir / agatha / ausneets / cafechan / gayshame / hikki / leftpol / strek ][Options][ watchlist ]

/tech/ - Technology

You can now write text to your AI-generated image at https://aiproto.com It is currently free to use for Proto members.
Name
Email
Subject
Comment *
File
Select/drop/paste files here
* = required field[▶ Show post options & limits]
Confused? See the FAQ.
Expand all images

[–]

 No.876712>>876730 >>876733 >>876893 >>877239 [Watch Thread][Show All Posts]

 No.876715>>876753 >>876763

Wow, they found all 10 retards that had the XML-RPC feature compiled and enabled


 No.876723

>t. uTorrent users trying to feel better about themselves

Don't be a retard. If you expose service to the internet assume it's going to be owned and plan your security accordingly.


 No.876730

>>876712 (OP)

install qbittorrent or ktorrent, fag


 No.876733

>>876712 (OP)

Guess I will have to go back to Usenet then


 No.876734

File (hide): 9300ed07b09d860⋯.png (117.94 KB, 1366x768, 683:384, 2018-02-23-203043_1366x768….png) (h) (u)

I use rtorrent-ps without xmlrpc, latest git


 No.876738

>No 'default behavior' for rpc is enabled by rtorrent, and using unix sockets for RPC is what I'm recommending.

People fucked it up if they enabled it through TCP tbh


 No.876753>>876767

>>876715

literally everyone has it enabled so they can use rutorrent to control it.


 No.876763>>876783 >>876897

>>876715

I use flood instead of rutorent. flood is better. and use socket to talk to it.


 No.876767

File (hide): c19b5eb577553e2⋯.jpg (71.59 KB, 960x720, 4:3, mpv-shot0001.jpg) (h) (u)

>>876753

>Not SSHing to the server and controlling rtorrent


 No.876783>>876785

>>876763

>nodejs

t. dicklover


 No.876785>>876859 >>876880

>>876783

Also, the last commit encapsulate all the faggotry of node.js users:

>Replaces Slack with Discord


 No.876859

>>876785

Why is there no simple GUI for rtorrent?


 No.876880

>>876785

>replaces piss with shit

wow, something to worry about!


 No.876893

>>876712 (OP)

>direct linking that shitty website

https://archive.fo/t5Nnz


 No.876897>>876898 >>876910 >>877129

File (hide): 30290e2b7f9c796⋯.webm (715.07 KB, 768x559, 768:559, good job.webm) (h) (u) [play once] [loop]


 No.876898>>876904

>>876897

where is that cute loli from?


 No.876904>>876933

File (hide): 0835318f3262d52⋯.png (2.43 MB, 1920x1080, 16:9, way-of-the-samurai-4-4.png) (h) (u)

>>876898

Way of the Samurai 4.


 No.876910

>>876897

Your font rendering gave me aids


 No.876933

>>876904

Thanks.


 No.876945>>876963 >>876965

Tixati masterrace!


 No.876963

>>876945

Enjoy your ban for ratio cheating


 No.876965>>877014

>>876945

>proprietary software

botnet using degenerates out


 No.877014>>877018

>>876965

>using the centralized 8chan


 No.877018>>877039

>>877014

I don't need to use any proprietary software to post to 8chan and read from it.


 No.877035

The real trouble is the fact people put a fucking server on a computer and expect it to be able to securely communicate with anyone on the planet from average joe to chinese government botnets passively scanning and trying exploits against their box.

Why don't you make it so that ONLY YOU can connect to YOUR server? Drop ALL packets by default and only open ports to an authorized computer. Use something like port knocking, or even better single packet authorization. The idea is the network stack will read packet contents and drop them all, but when a packet that is signed by an authorized key comes in it will establish a secure connection to that computer only.

Security comes from TRUST, so don't let retards you don't even know much less trust talk to your server at all.


 No.877039>>877040

>>877018

>as long as the client is opensource its all good


 No.877040>>877041


 No.877041>>877042

>>877040

>Implying thats the code they run


 No.877042>>877050

File (hide): 89e311b09d77453⋯.gif (1.17 MB, 400x225, 16:9, 137145288563.gif) (h) (u)


 No.877050

>>877042

It used to not be. Just noticed the readme change.


 No.877129

>>876897

>node.js server for torrent client

How could they made this shit up, no wonder it's fucked.


 No.877186>>877206

Time to swtich to https://synapse-bt.org/ you faggots.


 No.877206>>877240

>>877186

Yeah, really following this one; we'll get to harvest more Windows luser tears.

But there's no curses UI, only a faggot node.js web interface. If the CLI is good enough, I'll use it, though.


 No.877239>>877260

>>876712 (OP)

what about qBittorrent?


 No.877240>>877260


 No.877260>>877692

>>877239

As some anon said

>Qt bloatware + libtorrent boost insanity

>so retarded it even depends on Qt for non-GUI stuff

>six millions issues on the github

>>877240

Cool. I expected one to be made soon anyway, just didn't know this one.


 No.877330

>Attackers have generated $3,900 so far in an ongoing campaign that's exploiting the popular rTorrent application to install currency-mining software on computers running Unix-like operating systems, researchers said Thursday.

It's unavoidable on UNIX-like operating systems. If they weren't running rTorrent, there would be something else to exploit, like finger.

Subject: What you once thought was a brain-dead misimplementation is now the protocol definition!
or, Unix Historical Revisionism At Work Again,
or, IETF-approved RFC1196

This whole thing is pretty sad, or pathetic, or depressing
or something.

Firstly, there's the rewriting of a protocol to conform
to a ubiquitous misimplementation -- the unix story over and
over.

Then there's the growing Balkanisation (or
Multics-ification) of the net -- I remember laughing out
loud when I found that MIT-MULTICS refused finger service on
security grounds.

Then, or course, there's the pathetic implementational
warnings about how one should be very very careful in
implementing this sensitive and dangerous protocol -- as if
this perilous protocol somehow innately offered a direct way
to shove fingers up unix' sockets. Or something.


 No.877394>>877396 >>877398

Was rTorrent not free software or something? Transmission and qBittorrent have always worked fine for me. Transmission has a webui and can be controlled with SSH as well


 No.877396>>877424

>>877394

rtorrent is free. I think the retards had the RPC listening on the external IP instead of on localhost, they had it coming and the hackers did nothing wrong.


 No.877398>>877424

>>877394

I done read the article and I guess RPC is to blame here.


 No.877424>>877434 >>877438

>>877398

>>877396

Is there anyway to check if RPC is showing my actual IP and how to turn it off?


 No.877434>>877440

>>877424

Just compile it without support for rpc. Its disabled by default on gentoo. Even if its built with support it has to be explicitly enabled in the config. And on top of that the recommended configuration on the rtorrent wiki page on github has always been to use a unix socket.

sage because we don't need anymore low effort threads.


 No.877438>>877442

>>877424

netstat or try to connect to it from another machine.


 No.877440

File (hide): 296c00467703e73⋯.jpg (10.39 KB, 238x211, 238:211, manga-girl-thumbs-up-min.jpg) (h) (u)

>>877434

Thank You My Nigger


 No.877442

>>877438

You Too


 No.877632

>to install unix coin miner

Joke's on them I mine CPU coins already so they won't get anything.

Or if they do I'll notice it because my hashrate will go down.


 No.877653>>877666

deluge?


 No.877666

>>877653

Slowest and less scalable client. No, thanks. Transmission is already good, and synapses is getting here.


 No.877692

>>877260

works on my machine




[Return][Go to top][Catalog][Screencap][Nerve Center][Cancer][Update] ( Scroll to new posts) ( Auto) 5
49 replies | 6 images | Page ???
[Post a Reply]
[ / / / / / / / / / / / / / ] [ dir / agatha / ausneets / cafechan / gayshame / hikki / leftpol / strek ][ watchlist ]