Re: [Hamlib-developer] Re: gnuradio and Hamlib

[Stephane F. <f4...@fr...>]

Quoting Matt Ettus <ma...@et...>:
> I checked out from cvs, but configure is missing.  I tried ./autogen.sh,
> but I get:
> 
> [matt@localhost hamlib]$ ./autogen.sh 
> I am going to run ./configure with no arguments - if you wish 
> to pass any to it, please specify them on the ./autogen.sh command
> line.
> /usr/bin/m4: configure.in: No such file or directory
               ^^^^^^^^^^^^
> kylix/Makefile.am:1: invalid variable `dist_sharedstate_DATA'
> autoconf: configure.in: No such file or directory
> ./autogen.sh: ./configure: No such file or directory

hmm, it seems like you have an old autoconf (like 2.13).
You can check it with "autoconf --version" and "automake --version".
autoconf must be at least 2.50 or higher, and automake at least 1.5.


> 1> It's been about 10 years since I did any RPC stuff...  How is security
> handled?  I wouldn't want to put a rig or rotator on the net only to
> have it hacked.

AFAIN, RPC security has been left in the state it was 10 years ago.
There are some session oriented management in RPC, but Hamlib does
not support it yet. This can change in the future.
Another cheap way to protect your rpc daemon is to use a tcp/udp wrapper,
that restricts acces based on client IP address.

Anyone knows how to secure RPC?

> 2> Has there been any thought/work on alternate pathways for audio/signals?  I
> guess I mean that while with my FT-1000 I might want all audio to go through 
the
> standard speaker/mike,  what happens if I want to pass rig audio through the 
PC
> soundcard for processing?  Or what if I wanted to send the audio from my  
remote
> rig over ethernet back to the point where I am operating grig over rpc?

I guess we'll be making some configuration (rig_set_conf) or "extra" parameter 
(rig_set_ext_parm) in the gnuradio backend, to tell it what the output
should be, provided it has support for it.
The difference between rig_set_conf and rig_set_ext_parm is that set_conf
can only be done before rig_open, whereas set_ext_parm can be done any time 
afterwards.
IOW, do you want to change the ouput sink dynamically while gnuradio is running?


Cheers,
Stephane

PS: I'll add support for the FT-1000 next month, after my vacation 
    in 5U (sri, not qrv).