I can’t get gtk-gnutella to run. I haven’t put custom settings into the program to use a certain IP or ports because I think I need virtual DNS settings, and once again, I can’t see those now in the latest 4.1, I just see some of the numbers, and it looks like there are 4 sets of virtual DNS numbers. Without modifying program settings, won’t work with whonix, sys-firewall or sys-net as net provider
anyone know how to get this working?
Anyone?
I don’t know what to do here. Can someone else install it and just do a search for “classical” and see if anything shows up. I can’t get any search results to show and I don’t think I’m even connected. You can download it from the Software Repository of Fedora-34. Anyone? I’ve tried to change the settings but I am not smart enough to figure out how to get it to work on my own.
I won’t install it, but I can hazard a guess: gnutella is a file sharing
program – right? As such it likely requires incoming connections, which
are blocked by default (and for good reason) in Qubes OS.
If you wanted to run gnutella in a qube you should:
This is one of those instances where just giving you the solution would
be a disservice to you and anyone else reading the answer and applying
it without understanding.
Sven, you’re smarter than I am. I am trying to get more knowledgeable and have been reading the documentation. Can you at least give me a hint about where in the documentation I look?
I can’t even get anything even when I am connecting to system-net. I realize the security risks of connecting in this way. Would I need to actually use commands or can I do this with a gui? I am still learning linux and qubes and suck at commands.
@qubesn00b wrote:
Can you at least give me a hint about where in the documentation I
look?
You have been warned!
How file sharing works:
Gnutella port:
Gnutella risks:
http://alumni.cs.ucr.edu/~csyiazti/courses/cs260-2/project/gnutella.pdf
Port forwarding to a qube from the outside world:
Look @qubesn00b the problem is that by enabling gnutella to work in your
qube, you are making that qube an actual server on the internet. That is
a dangerous thing to do and maintain for the most skilled techies.
Of course on the one hand Qubes OS will likely limit any compromise to
that qube, on the other hand that qube being compromised is
astronomically more likely.
You should know that and weight the risks. If you use Qubes OS because
you are seriously at risk or have secrets worth protecting, maybe don’t
run P2P services.
I know that using P2P is a lot like walking through the streets of Marakesh with only my hijab on, but I could just clone that Qube and delete the used one afterward.
I wasn’t able to get it working. I had given the Qube access to sys-firewall and didn’t put any limitations on the ports. It should have worked. Maybe someone like me shouldn’t be trying to learn Qubes. I heard Windows 11 will be coming out soon and it has a lot of privacy upgrades. Maybe I can get ready to use that, update my Facebook account with better photos showing me cooking, and hope my family can provide a good husband for me.
@qubesn00b wrote:
I had given the Qube access to sys-firewall and didn’t put any
limitations on the ports. It should have worked.
No it shouldn’t. I gave you all the hints you need. The firewall GUI
will let you only configure outgoing connections. For gnutella to work
you need to allow “port forwarding to a qube from the outside world”.
The Qubes OS documentation I linked gives you step by step instructions
on how to do so.
Windows 11
Knock yourself out.
Maybe I can get ready to use that, update my Facebook account with
better photos showing me cooking, and hope my family can provide a
good husband for me.
I don’t think there is any forum member unaware of your personal
situation at this point. Maybe, if that really is what’s going on you
should stop broadcasting it. You’ll get the same help here independent
of your situation / gender / location / age etc.