Remote server suggestion

Asked by arvidgibas

Can you guys implement an option to scp nzb files to a remote hellanzb server? With for example remote-hellanzb-gui it is possible. It would be awesome if lottanzb can do it too :)

Question information

Language:
English Edit question
Status:
Answered
For:
LottaNZB Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Severin H (severinh) said :
#1

Hi arvidgibas,

I didn't know that there is a remote-hellanzb-gui project until now. And as it seems, it's even based on LottaNZB code. I guess we'll try to get in touch with the developer of the remove-hellanzb-gui. We're currently working on a plugin system (and it already works damn fine ;-)) and it looks like an SSH plugin, which enables the user to add actually enqueue NZB files over the network, would be awesome. May be we can work together.

Regards,
Severin

Revision history for this message
freddy3980 (freddy3980) said :
#2

It will be great if they decide to join/help to LottaNZB, it will make maybe the best gui for HellaNZB?

Revision history for this message
Charclo (charclo-michael) said :
#3

This is a feature I would really like. Any news about this?

Revision history for this message
Clément Lorteau (northern-lights) said :
#4

Yup, i'm the author of Remote HellaNZB GUI and I happily accepted the invitation to join the team :)

Don't expect it to be released too soon though. But i'll try to write a blue print for it soon.

Revision history for this message
freddy3980 (freddy3980) said :
#5

Great news :)

Revision history for this message
Severin H (severinh) said :
#6

The branch that features plugin support will be merged into main soon, which is the first step towards such SSH support.

@Clément: We don't expect you to finish it by tomorrow. ;-) I'll take a closer look at your application and I may be able to assist you creating a blueprint.

Revision history for this message
Severin H (severinh) said :
#7

Oh my science! I just had a quick look at the HellaNZB XMLRPC code and noticed that the enqueue method has a second (optional) nzb_data argument. Passing open(my_nzb_file, "r").read() to it makes it possible to enqueue an NZB file over the network.

Unbelievable! Why didn't we find out about this earlier?! It's so easy to add this feature that it really hurts. xD I guess it might be important enough to release LottaNZB 0.4.2.

Revision history for this message
Clément Lorteau (northern-lights) said :
#8

Did you actually try or is it an assumption? I tried that before going over all that SSH thing and i came to the conclusion that the second argument is a filename that will be local for the server.

Revision history for this message
Severin H (severinh) said :
#9

I can assure you that I tried it and it worked fine. If the nzb_data argument is set, HellaNZB will use the basename of the filename passed as the first argument, write the nzb_data string to that file and enqueue it. The file transmission takes about one or two seconds (depending on the size of the NZB file), that's why the add dialog would need to be hidden before the file is enqueued so that the UI isn't blocked.

Revision history for this message
Clément Lorteau (northern-lights) said :
#10

*bangs head on the desk thinking about the 3 weeks spent coding the SSH part of remote hellanzb gui*

Well, that's great news. Let's add the 2 lines of code needed and try it!

A SSH plugin becomes really less useful then (not to mention the remote hellanzb gui project which might go to the trashcan very quick). Not totally useless i might say, as it could be an option to add extra security, but that would still be a secondary use option.

Revision history for this message
Clément Lorteau (northern-lights) said :
#11

Just to precise what i mean by "extra security", the way SSH works in remote hellanzb gui and the way i thought of implementing it in lottanzb is that not only nzb files are copied to the server through SSH (which we know is useless now), but also a SSH tunnel is mounted automatically and all communications with the server are directed through it.

This way, instead of having http connections with a possibly weak password and a hardcoded username and exposing to the internet the possibly weak implementation of http used in http rpc implementation, you expose a SSH server, and the client and server mutually authenticate themselves via the use of RSA keys.

Revision history for this message
Sander Tuit (avirulence) said :
#12

This might not be a bad idea at all, since most people that use usenet care
about their privacy.. however, I don't think that this would be possible in
a plug-in.

On Jan 29, 2009 7:26 PM, "Clément Lorteau" <
<email address hidden>> wrote:

Question #58625 on LottaNZB changed:
https://answers.edge.launchpad.net/lottanzb/+question/58625 Cl...
Just to precise what i mean by "extra security", the way SSH works in
remote hellanzb gui and the way i thought of implementing it in lottanzb
is that not only nzb files are copied to the server through SSH (which
we know is useless now), but also a SSH tunnel is mounted automatically
and all communications with the server are directed through it.

This way, instead of having http connections with a possibly weak
password and a hardcoded username and exposing to the internet the
possibly weak implementation of http used in http rpc implementation,
you expose a SSH server, and the client and server mutually authenticate
themselves via the use of RSA keys.

-- You received this question notification because you are an answer contact
for LottaNZB.

Revision history for this message
freddy3980 (freddy3980) said :
#13

Clément Lorteau, why not merge your project with LottaNZB since you said: "A SSH plugin becomes really less useful then (not to mention the remote hellanzb gui project which might go to the trashcan very quick)."? Also, that way it will become a stronger gui for HellaNZB... just an idea :)

Revision history for this message
Severin H (severinh) said :
#14

@Clément: I'm not an expert when it comes to SSH. Could you tell us more about how such an SSH feature would look like on the whole. Would one need to make changes in the HellaNZB source code or would it be neccessary to run an additional programm/LottaNZB on the remote machine HellaNZB is running on or would it be enough to run the (SSH powered) LottaNZB on the observer machine that can take care of everything?

Revision history for this message
Clément Lorteau (northern-lights) said :
#15

Hello, sorry for the late answer. Too much work lately.

@Severin: i'm answering your question in a new blueprint: https://blueprints.edge.launchpad.net/lottanzb/+spec/ssh-tunnel

@Freddy: i'm not sure yet what i'll do with remote hellanzb gui. At least i'll get it into Debian and Ubuntu, then i'll see.

Can you help with this problem?

Provide an answer of your own, or ask arvidgibas for more information if necessary.

To post a message you must log in.