Entering a file/folder path in a cmd window

I read a tip that looked like just what I've been wanting but it does
not seem to work. It is alleged that you can left click, hold and drag a
folder or file name into the cmd window will copy it there. Neat! Except
that it doesn't do anything. Any ideas?

On 07/30/2018 12:21 PM, Jason wrote:
I read a tip that looked like just what I've been wanting but it does
not seem to work. It is alleged that you can left click, hold and drag a
folder or file name into the cmd window will copy it there. Neat! Except
that it doesn't do anything. Any ideas?


Yes, it works in a command prompt, But *not* in a command prompt (admin).

Rene

Rene Lamontagne wrote:
On 07/30/2018 12:21 PM, Jason wrote:
I read a tip that looked like just what I've been wanting but it does
not seem to work. It is alleged that you can left click, hold and drag a
folder or file name into the cmd window will copy it there. Neat! Except
that it doesn't do anything. Any ideas?


Yes, it works in a command prompt, But *not* in a command prompt (admin).

Rene




Same here. Strange! Especially strange since it works with both under
Windows 7.

Ed

On Mon, 30 Jul 2018 12:33:34 -0500, Rene Lamontagne
wrote:

On 07/30/2018 12:21 PM, Jason wrote:
I read a tip that looked like just what I've been wanting but it does
not seem to work. It is alleged that you can left click, hold and drag a
folder or file name into the cmd window will copy it there. Neat! Except
that it doesn't do anything. Any ideas?


Yes, it works in a command prompt, But *not* in a command prompt (admin).


Having read what you wrote and having a hard time believing it, I just
tried it both ways. To my great surprise, you're absolutely right!

It's clearly a bug, but a very strange bug.

Ken Blake wrote:
On Mon, 30 Jul 2018 12:33:34 -0500, Rene Lamontagne
wrote:

On 07/30/2018 12:21 PM, Jason wrote:
I read a tip that looked like just what I've been wanting but it does
not seem to work. It is alleged that you can left click, hold and drag a
folder or file name into the cmd window will copy it there. Neat! Except
that it doesn't do anything. Any ideas?


Yes, it works in a command prompt, But *not* in a command prompt (admin).


Having read what you wrote and having a hard time believing it, I just
tried it both ways. To my great surprise, you're absolutely right!

It's clearly a bug, but a very strange bug.

Or by design?
--
Quote of the Week: "The ants are a people not strong, yet they prepare their meat in the summer." --Proverbs 30:25 (Bible)
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\Ant(Dude) @ http://antfarm.home.dhs.org / http://antfarm.ma.cx
/ /\ /\ \ Please nuke ANT if replying by e-mail privately. If credit-
| |o o| | ing, then please kindly use Ant nickname and URL/link.
\ _ /
( )

On Mon, 30 Jul 2018 15:37:06 -0500, (Ant) wrote:

Ken Blake wrote:
On Mon, 30 Jul 2018 12:33:34 -0500, Rene Lamontagne
wrote:

On 07/30/2018 12:21 PM, Jason wrote:
I read a tip that looked like just what I've been wanting but it does
not seem to work. It is alleged that you can left click, hold and drag a
folder or file name into the cmd window will copy it there. Neat! Except
that it doesn't do anything. Any ideas?


Yes, it works in a command prompt, But *not* in a command prompt (admin).


Having read what you wrote and having a hard time believing it, I just
tried it both ways. To my great surprise, you're absolutely right!

It's clearly a bug, but a very strange bug.

Or by design?



Nah! It's hard to believe that such a thing could be by design, and
*especially* hard to believe that something is designed to work for
non-administrators but not administrators.

Ken Blake wrote:
On Mon, 30 Jul 2018 15:37:06 -0500, (Ant) wrote:

Ken Blake wrote:
On Mon, 30 Jul 2018 12:33:34 -0500, Rene Lamontagne
wrote:
On 07/30/2018 12:21 PM, Jason wrote:
I read a tip that looked like just what I've been wanting but it does
not seem to work. It is alleged that you can left click, hold and drag a
folder or file name into the cmd window will copy it there. Neat! Except
that it doesn't do anything. Any ideas?

Yes, it works in a command prompt, But *not* in a command prompt (admin).

Having read what you wrote and having a hard time believing it, I just
tried it both ways. To my great surprise, you're absolutely right!
It's clearly a bug, but a very strange bug.
Or by design?



Nah! It's hard to believe that such a thing could be by design, and
*especially* hard to believe that something is designed to work for
non-administrators but not administrators.

In Task Manager, I turned on the SessionID column, and
both Command Prompt windows belong to Session 1. So it's
not like the windows themselves are different.

Pasting a command (perhaps complete with carriage return)
into an Administrator prompt, is a bad idea from a security
perspective. This could be a by-design decision, but
if so, there are some other means of doing the same
thing that should also be blocked, for consistency.

Maybe it's the ease of doing it that is a problem.
Like, maybe there is a *command* that can do the
same thing as the gesture is doing.

Paul

In article ,
says...

On 07/30/2018 12:21 PM, Jason wrote:
I read a tip that looked like just what I've been wanting but it does
not seem to work. It is alleged that you can left click, hold and drag a
folder or file name into the cmd window will copy it there. Neat! Except
that it doesn't do anything. Any ideas?


Yes, it works in a command prompt, But *not* in a command prompt (admin).

Rene

Bingo! Thanks, Rene.

On 2018-07-31 10:04, Ken Blake wrote:

Yes, it works in a command prompt, But *not* in a command prompt (admin).

Having read what you wrote and having a hard time believing it, I just
tried it both ways. To my great surprise, you're absolutely right!
It's clearly a bug, but a very strange bug.
Or by design?


Nah! It's hard to believe that such a thing could be by design, and
*especially* hard to believe that something is designed to work for
non-administrators but not administrators.


Sadly, it is by design.

It is called UIPI (User Interface Privilege Isolation) and it prevents
processes running at a lower privilege level from sending messages to
processes running at a higher privilege level. Microsoft did this to
block privilege escalation vulnerabilities like the Shatter attack. It
also means that File Explorer, which is not running elevated and is
therefore at a lower privilege level, cannot send the file name to
Command Prompt (Admin), which is running elevated and is therefore at a
higher privilege level.

Microsoft's original idea before UIPI was that users should run higher
privilege level processes on a different desktop. (Of course we know
users won't actually do this.)

I think Microsoft should follow its original idea and not use UIPI. My
blasterswarm program would behave nicely until someone opened a Command
prompt (Admin) window on the same desktop. Then my blasterswarm program
would send commands to Command prompt (Admin) to pwn the user's system.
That is fair game; if you haven't paid for my program then you are not
the customer, you are the product being sold.

Sadly, Microsoft changed its position from requiring users to be
responsible for their own security to being a nanny with UIPI. It is
exactly like selling only lukewarm coffee because someone might put a
hot cup of coffee between his or her legs and then sue the company who
sold the coffee.