similar to: Why are the arguments supplied for the command run through ssh interpreted by shell before they are passed to the command on the server side?

On Sun, 12 Jan 2020, Yuri wrote: > This was English, not German, BTW. For some values of English, perhaps. > You would lose the ability to redirect I/O in an immediate way, but you would > always be able to run a shell command like "/bin/sh" "-c" "any-command | tee > cmd.log | process-further" which would regain the ability to do everything > that a

On Sun, 12 Jan 2020, Yuri wrote: > dedicated argument, for example -z. The specification can be like this: The wording could need some translation by a native speaker, but the idea of this feature request is certainly sound. Of course you?d lose the ability to run multiple commands, redirect I/O, etc. when using your proposed flag. bye, //mirabilos -- tarent solutions GmbH Rochusstra?e

On 2020-01-11 08:57, Thorsten Glaser wrote: > If you wish for no local expansion, quote locally, such as: > > ssh -l luser remotehost ' > command1 > command2 > ? > ' This didn't work for me because single quotes only prevent local expansion. The string is expanded on the remote host. Yuri

On 2020-01-11 01:38, Darren Tucker wrote: > The command you give is always handled on the server by your shell in some > fashion. It has to be, because SSH only specifies an opaque string for the > remote command, so without doing so you would not be able to specify > arguments at all. It's not obvious why does it have to be this way. ssh sends the command as an array of

I do think it's a problem that, as far as I can see, the exact behaviour of ssh command interpretation isn't explained anywhere in its man pages, even though it seems like the only possibility if you understand the protocol. ssh(1) just says "If command is specified, it is executed on the remote host instead of a login shell", but that doesn't provide any hint about what

On Tue, 2 Dec 2014, H. Peter Anvin wrote: > This is the default unless the "quiet" option is set. Hmm. tglaser at luna:/srv/tftp $ fgrep -ri quiet . Binary file ./hdt.c32 matches Binary file ./ldlinux.c32 matches Binary file ./vmlinuz matches Binary file ./linux.c32 matches Binary file ./debian-installer/jessie/amd64/linux matches Binary file ./debian-installer/jessie/i386/linux

I conjecture that only few of the existing use cases rely on remote expansion. In any case (no pun intended), IMHO it would be better to break a few of the current use cases but leave the majority functional - than kill scp for all. Regards, Uri > On Aug 3, 2020, at 02:50, Jakub Jelen <jjelen at redhat.com> wrote: > > ?On Sat, 2020-08-01 at 00:17 +0000, Blumenthal, Uri - 0553

Hi, I still have the question: when I have an environment that uses vesamenu, for example on PXE, how do I configure it so that, for some of the menu entries, it switches back to the text mode (03h) before handing off to the next bootloader / kernel? Thanks, //mirabilos -- tarent solutions GmbH Rochusstra?e 2-4, D-53123 Bonn ? http://www.tarent.de/ Tel: +49 228 54881-393 ? Fax: +49 228

Ah, depends on the image type. We spoke reset for an NBP though. On December 3, 2014 12:50:24 AM PST, Thorsten Glaser <t.glaser at tarent.de> wrote: >On Tue, 2 Dec 2014, H. Peter Anvin wrote: > >> This is the default unless the "quiet" option is set. > >Hmm. > >tglaser at luna:/srv/tftp $ fgrep -ri quiet . >Binary file ./hdt.c32 matches >Binary file

On Wed, 21 Jan 2015, Andreas Gruenbacher wrote: > Not really. As a security requirement, if this even really is anyone's > security requirement, this is pointless -- the ErrCode is set to 0 ("Not Still, requirements like this d?o? exist in the real world, dismissing them is a, I quote, stupid idea. I?d suggest to please wake up. bye, //mirabilos (not speaking for his employer

On Dec 3, 2014 3:54 AM, "Thorsten Glaser" <t.glaser at tarent.de> wrote: > > On Tue, 2 Dec 2014, H. Peter Anvin wrote: > > > This is the default unless the "quiet" option is set. > > Hmm. > It does not switch back to text mode when chaining to > https://www.mirbsd.org/MirOS/current/i386/boot renamed > to "pxebsd.0" (used to be

On 12/02/2014 06:48 AM, Thorsten Glaser wrote: > Hi, > > I still have the question: when I have an environment that uses > vesamenu, for example on PXE, how do I configure it so that, for > some of the menu entries, it switches back to the text mode (03h) > before handing off to the next bootloader / kernel? > This is the default unless the "quiet" option is set.

On Thu, Dec 4, 2014 at 8:45 AM, Ady <ady-sf at hotmail.com> wrote: > >> On Thu, 4 Dec 2014, Ady wrote: >> >> > Perhaps there should be a new MENU-type directive, so to force the >> > screen to text mode (as opposed to leaving it in graphics mode for as >> > long as it can be)? Perhaps this could also be useful when exiting a >> > vesamenu to

On Thu, Dec 4, 2014 at 11:40 PM, Jeffrey Hutzelman <jhutz at cmu.edu> wrote: > On Thu, 2014-12-04 at 21:26 -0500, Gene Cumm wrote: > >> > Thanks, that works! How do I use that in the generic case? >> > The ?pxebsd.0? file can be called as? >> > >> > ? PXE loader >> > ? COMBOOT (16-bit) >> > ? DOS .COM >> > ? Multiboot

> On Fri, 5 Dec 2014, Gene Cumm wrote: > > > >> mostly in C and be BIOS-only) or making the MirOS kernel act like > > >> either an MBOOT kernel or a Linux kernel (for their boot protocols), > > The MirBSD _bootloader_ (not kernel) can act as a Multiboot kernel. > It can then use disc access (not PXE), or you can pass it the "real" > kernel, but

On Thu, 2014-12-04 at 21:26 -0500, Gene Cumm wrote: > > Thanks, that works! How do I use that in the generic case? > > The ?pxebsd.0? file can be called as? > > > > ? PXE loader > > ? COMBOOT (16-bit) > > ? DOS .COM > > ? Multiboot (although it switches back to 16-bit mode immediately) > > ? from its own bootsector, if installed on disc (blocklist)

On Fri, 5 Dec 2014, Ady wrote: > > > If so: http://www.syslinux.org/wiki/index.php/Mboot.c32 > > > > I?m not permitted to edit either that page or its talk page. > > Do I submit the content addition here, then? > > Please do. Okay, MediaWiki syntax docs follow. Note I have tested those only a bit, and not within the vesamenu context, but if mboot.c32 resets to

On 01/20/2015 02:45 PM, Andreas Gruenbacher wrote: > > Sorry, but people with such stupid requirements just shouldn't be > supported. The approach may look alright in a few specific scenarios at > the cost of everyone else. > That is a pretty harsh statement. That is effectively saying "my use case matters more than anyone else's." -hpa

On 01/21/2015 09:56 AM, H. Peter Anvin wrote: > On 01/20/2015 02:45 PM, Andreas Gruenbacher wrote: >> >> Sorry, but people with such stupid requirements just shouldn't be >> supported. The approach may look alright in a few specific scenarios at >> the cost of everyone else. > > That is a pretty harsh statement. That is effectively saying "my use >

I'll play the security advocate.... So most of the people that implement tftp services have almost no idea how they work....and that's o.k. They do however have a few fundamental beliefs that they expect to be true, and it is those beliefs that they use to make decisions when implementing a service and it's data structures. If they are not true, then they are likely vulnerable to an