Dropbear Makefile enhancements
Rail Aliev
2007/3/15, Rail Aliev <rail...@gmail.com>:
cyberstorm
On 15 Mar, 11:57, "Rail Aliev" <railal...@gmail.com> wrote:
> > Attached is a patch for dropbear which:
> > 1) adds dopbearkey in make targets (which segfaults unfotunately now :( )
Hi,
I did not explain you what I've done in the last days.
Before, the dropbear private key was generated during compile, using
the statc linked x86 binary dropbearkey located in router/misc. In
this way, the key could not be changed, and was the same for all
builds.
Now instead I have made some changes you can see in Management.asp
(update to the last revision). Using that page you can create a rw
partition to store the private key, and also make the router generate
the key. The "bad" thing is that after every upgrade the partition is
erased. ATM interaction with web interface is VERY simple, that is
button is not used for submitting, but simply to redirect to another
page.
So, in this case, dropbearkey is compiled as a mipsel executable.
> > 2) uses symlinks instead of file copy of dropbearmulty for dropbear,
> > dbclient, ssh and scp
yes, this is ok.
cyberstorm
On 15 Mar, 19:47, "cyberstorm" <marco....@gmail.com> wrote:
> > > 2) uses symlinks instead of file copy of dropbearmulty for dropbear,
> > > dbclient, ssh and scp
>
> yes, this is ok.
no, I think it should be:
ln -sf $(INSTALLDIR)/dropbear/usr/bin/dropbearmulti $(INSTALLDIR)/
dropbear/usr/bin/dropbear
....
thank you for your efforts
regards
marco
Rail Aliev
> no, I think it should be:
>
> ln -sf $(INSTALLDIR)/dropbear/usr/bin/dropbearmulti $(INSTALLDIR)/
> dropbear/usr/bin/dropbear
In this case you get absolute symlink containing $(INSTALLDIR) which
doesn't work after image assemble.
The latest patch I sent is working one ans I use it during 1 day. :p
Rail Aliev
>
>
>
> On 15 Mar, 11:57, "Rail Aliev" <railal...@gmail.com> wrote:
>
> > > Attached is a patch for dropbear which:
> > > 1) adds dopbearkey in make targets (which segfaults unfotunately now :( )
>
> Hi,
> I did not explain you what I've done in the last days.
> Before, the dropbear private key was generated during compile, using
> the statc linked x86 binary dropbearkey located in router/misc. In
> this way, the key could not be changed, and was the same for all
> builds.
Already at latest version of trunk. ;) I saw all your improvements and
after it I added dropbearkey to dropbearmulti.
[...]
> The "bad" thing is that after every upgrade the partition is
> erased. ATM interaction with web interface is VERY simple, that is
> button is not used for submitting, but simply to redirect to another
> page.
I don't think it is a big problem for dropbear. But if we will extend
neptune and have a lot of programs which need r/w partition (openvpn
for example) it may be a problem.
cyberstorm
repository, so you apply those changes.
marco
On 16 Mar, 07:13, "Rail Aliev" <railal...@gmail.com> wrote:
> 2007/3/15, cyberstorm <marco....@gmail.com>:
Rail Aliev
>
> ok, if you are sure it works Im giving you the rights to write in the
> repository, so you apply those changes.
I prefer to send patches for your review at this stage. I am newbie to
embedded linux and build/packaging system used in neptune.