* [Buildroot] Manual password entry for DOWNLOAD_SCP scheme
@ 2012-07-31 10:24 Steve Goldberg
2012-07-31 10:34 ` Thomas De Schampheleire
0 siblings, 1 reply; 6+ messages in thread
From: Steve Goldberg @ 2012-07-31 10:24 UTC (permalink / raw)
To: buildroot
I'm putting together a TI toolchain package but as some of the required packages are export controlled I need to host them on my institutional machine to control access. I think scp is the best choice for this but the scp scheme does not prompt for passwords and users who haven't setup public-key ssh access are unable to download the packages. Why does the DOWNLOAD_SCP scheme not prompt the user for a password?
Thanks.
Steve Goldberg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120731/db4dea5e/attachment.html>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Manual password entry for DOWNLOAD_SCP scheme
2012-07-31 10:24 [Buildroot] Manual password entry for DOWNLOAD_SCP scheme Steve Goldberg
@ 2012-07-31 10:34 ` Thomas De Schampheleire
[not found] ` <BLU145-W160B8971C18907119E0961D6C50@phx.gbl>
0 siblings, 1 reply; 6+ messages in thread
From: Thomas De Schampheleire @ 2012-07-31 10:34 UTC (permalink / raw)
To: buildroot
Hi,
On Tue, Jul 31, 2012 at 12:24 PM, Steve Goldberg
<indeliblesteve@hotmail.com> wrote:
> I'm putting together a TI toolchain package but as some of the required
> packages are export controlled I need to host them on my institutional
> machine to control access. I think scp is the best choice for this but the
> scp scheme does not prompt for passwords and users who haven't setup
> public-key ssh access are unable to download the packages. Why does the
> DOWNLOAD_SCP scheme not prompt the user for a password?
In my test, using scp as primary site, it does ask for a password if
one is required.
How have you configured the package? Have you specified a user?
Have you tried running scp manually? Is a password requested there? Is
the same command used as Buildroot does?
Best regards,
Thomas
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Manual password entry for DOWNLOAD_SCP scheme
[not found] ` <BLU145-W4DD32AE633EE92CAAD36DD6C50@phx.gbl>
@ 2012-07-31 14:55 ` Thomas De Schampheleire
2012-07-31 15:05 ` Arnout Vandecappelle
2012-07-31 16:47 ` Steve Goldberg
0 siblings, 2 replies; 6+ messages in thread
From: Thomas De Schampheleire @ 2012-07-31 14:55 UTC (permalink / raw)
To: buildroot
Please keep the buildroot mailing list in copy of all mails.
On Tue, Jul 31, 2012 at 1:18 PM, Steve Goldberg
<indeliblesteve@hotmail.com> wrote:
> Thomas,
>
> Problem solved. The DOWNLOAD_SCP requires two arguments, full path with
> filename and filename.
>
> Reading package/pkg-download.mk shows
>
> DOWNLOAD $(FOO_SITE),$(FOO_SOURCE)
>
> but scp seems to need
>
> DOWNLOAD $(FOO_SITE)/$(FOO_SOURCE), $(FOO_SOURCE)
>
[...]
> This is a summary of the ti-tools.mk.
>
> XDC_VERSION=3_16_01_27
> XDC_SITE=scp://host:/home/steve/TI_Tools
> XDC_SOURCE=xdctools_setuplinux_$(XDC_VERSION).bin
>
> $(DL_DIR)/$(XDC_SOURCE) :
> $(call DOWNLOAD_SCP,$(XDC_SITE)/$(XDC_SOURCE))
Note that you should call DOWNLOAD instead of DOWNLOAD_SCP directly.
This will make sure to respect the primary site and other mechanisms
that are in place.
Best regards,
Thomas
> From: indeliblesteve at hotmail.com
> To: patrickdepinguin+buildroot at gmail.com
> Subject: RE: [Buildroot] Manual password entry for DOWNLOAD_SCP scheme
> Date: Tue, 31 Jul 2012 04:07:15 -0700
>
>
> Thomas,
>
>> <indeliblesteve@hotmail.com> wrote:
>> > I'm putting together a TI toolchain package but as some of the required
>> > packages are export controlled I need to host them on my institutional
>> > machine to control access. I think scp is the best choice for this but
>> > the
>> > scp scheme does not prompt for passwords and users who haven't setup
>> > public-key ssh access are unable to download the packages. Why does the
>> > DOWNLOAD_SCP scheme not prompt the user for a password?
>>
>> In my test, using scp as primary site, it does ask for a password if
>> one is required.
>> How have you configured the package? Have you specified a user?
>
> This is a summary of the ti-tools.mk.
>
> XDC_VERSION=3_16_01_27
> XDC_SITE=scp://host:/home/steve/TI_Tools
> XDC_SOURCE=xdctools_setuplinux_$(XDC_VERSION).bin
>
> $(DL_DIR)/$(XDC_SOURCE) :
> $(call DOWNLOAD_SCP,$(XDC_SITE)/$(XDC_SOURCE))
>
>> Have you tried running scp manually? Is a password requested there? Is
>> the same command used as Buildroot does?
>
> Yes, I've manually run the scp command that is generated and it does prompt
> for a password.
>
> This is what buildroot generates.
>
> make -C /home/steve/plat/overo/src/buildroot O=/home/steve/plat/overo/.
> mkdir -p /home/steve/plat/overo/host/ti/tools
> test -e /home/isteve/plat/overo/download/ || scp
> 'host:/home/steve/TI_Tools/xdctools_setuplinux_3_16_01_27.bin'
> /home/isteve/plat/overo/download/
>
> manually running scp
> 'host:/home/steve/TI_Tools/xdctools_setuplinux_3_16_01_27.bin'
> /home/isteve/plat/overo/download/
> prompts me for password. I do not specify username as scp assumes the
> username of the current user which is okay for my purposes.
>
> Thanks.
>
> Steve
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Manual password entry for DOWNLOAD_SCP scheme
2012-07-31 14:55 ` Thomas De Schampheleire
@ 2012-07-31 15:05 ` Arnout Vandecappelle
2012-07-31 16:47 ` Steve Goldberg
1 sibling, 0 replies; 6+ messages in thread
From: Arnout Vandecappelle @ 2012-07-31 15:05 UTC (permalink / raw)
To: buildroot
On 07/31/12 16:55, Thomas De Schampheleire wrote:
> Please keep the buildroot mailing list in copy of all mails.
>
> On Tue, Jul 31, 2012 at 1:18 PM, Steve Goldberg
> <indeliblesteve@hotmail.com> wrote:
>> Thomas,
>>
>> Problem solved. The DOWNLOAD_SCP requires two arguments, full path with
>> filename and filename.
>>
>> Reading package/pkg-download.mk shows
>>
>> DOWNLOAD $(FOO_SITE),$(FOO_SOURCE)
>>
>> but scp seems to need
>>
>> DOWNLOAD $(FOO_SITE)/$(FOO_SOURCE), $(FOO_SOURCE)
>>
> [...]
>> This is a summary of the ti-tools.mk.
>>
>> XDC_VERSION=3_16_01_27
>> XDC_SITE=scp://host:/home/steve/TI_Tools
>> XDC_SOURCE=xdctools_setuplinux_$(XDC_VERSION).bin
>>
>> $(DL_DIR)/$(XDC_SOURCE) :
>> $(call DOWNLOAD_SCP,$(XDC_SITE)/$(XDC_SOURCE))
>
> Note that you should call DOWNLOAD instead of DOWNLOAD_SCP directly.
> This will make sure to respect the primary site and other mechanisms
> that are in place.
Moreover, you should use $(eval $(generic-package)) rather than manual
targets. If necessary, you can define XDC_EXTRACT_COMMANDS to use a
custom extraction mechanism (i.e., running the .bin file). But if you're
anyway keeping a local copy of the xdctools, you're better off extracting
it once and repacking it into a tar.bz2. Saves you a lot of pain figuring
out how to run the self-extractor non-interactively in a way that doesn't
mess up your home directory.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Manual password entry for DOWNLOAD_SCP scheme
2012-07-31 14:55 ` Thomas De Schampheleire
2012-07-31 15:05 ` Arnout Vandecappelle
@ 2012-07-31 16:47 ` Steve Goldberg
2012-08-01 6:42 ` Thomas De Schampheleire
1 sibling, 1 reply; 6+ messages in thread
From: Steve Goldberg @ 2012-07-31 16:47 UTC (permalink / raw)
To: buildroot
> Please keep the buildroot mailing list in copy of all mails.
Sorry. Will try and remember, reply all.
> > This is a summary of the ti-tools.mk.
> >
> > XDC_VERSION=3_16_01_27
> > XDC_SITE=scp://host:/home/steve/TI_Tools
> > XDC_SOURCE=xdctools_setuplinux_$(XDC_VERSION).bin
> >
> > $(DL_DIR)/$(XDC_SOURCE) :
> > $(call DOWNLOAD_SCP,$(XDC_SITE)/$(XDC_SOURCE))
>
> Note that you should call DOWNLOAD instead of DOWNLOAD_SCP directly.
> This will make sure to respect the primary site and other mechanisms
> that are in place.
I tried this initially but I got "Unsupported scheme `scp'." When I use DOWNLOAD_SCP directly, it worked. I think it's because I've placed the package in 'toolchain' not in the 'package' directory as it is technically a toolchain not a target package.
Steve Goldberg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120731/905f1dd7/attachment.html>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] Manual password entry for DOWNLOAD_SCP scheme
2012-07-31 16:47 ` Steve Goldberg
@ 2012-08-01 6:42 ` Thomas De Schampheleire
0 siblings, 0 replies; 6+ messages in thread
From: Thomas De Schampheleire @ 2012-08-01 6:42 UTC (permalink / raw)
To: buildroot
Hi,
On Tue, Jul 31, 2012 at 6:47 PM, Steve Goldberg
<indeliblesteve@hotmail.com> wrote:
>> Please keep the buildroot mailing list in copy of all mails.
>
> Sorry. Will try and remember, reply all.
>
>> > This is a summary of the ti-tools.mk.
>> >
>> > XDC_VERSION=3_16_01_27
>> > XDC_SITE=scp://host:/home/steve/TI_Tools
>> > XDC_SOURCE=xdctools_setuplinux_$(XDC_VERSION).bin
>> >
>> > $(DL_DIR)/$(XDC_SOURCE) :
>> > $(call DOWNLOAD_SCP,$(XDC_SITE)/$(XDC_SOURCE))
>>
>> Note that you should call DOWNLOAD instead of DOWNLOAD_SCP directly.
>> This will make sure to respect the primary site and other mechanisms
>> that are in place.
>
> I tried this initially but I got "Unsupported scheme `scp'." When I use
> DOWNLOAD_SCP directly, it worked. I think it's because I've placed the
> package in 'toolchain' not in the 'package' directory as it is technically a
> toolchain not a target package.
The message "Unsupported scheme" comes from wget. This indicates that
the scp download command was not tried. With a recent buildroot, the
scheme is auto-detected.
See commit http://git.buildroot.org/buildroot/commit/?id=77e26972187b9cda1a8f22ca74da154687c9ab1a
If you have an older buildroot installation, you have to set
<PKG>_SITE_METHOD=scp explicitly.
Whether the package is placed in toolchain/ or package/ does not
matter for this.
Best regards,
Thomas
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-08-01 6:42 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-07-31 10:24 [Buildroot] Manual password entry for DOWNLOAD_SCP scheme Steve Goldberg
2012-07-31 10:34 ` Thomas De Schampheleire
[not found] ` <BLU145-W160B8971C18907119E0961D6C50@phx.gbl>
[not found] ` <BLU145-W4DD32AE633EE92CAAD36DD6C50@phx.gbl>
2012-07-31 14:55 ` Thomas De Schampheleire
2012-07-31 15:05 ` Arnout Vandecappelle
2012-07-31 16:47 ` Steve Goldberg
2012-08-01 6:42 ` Thomas De Schampheleire
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox