How to know if a authenticate box is real or fake?
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
28
down vote
favorite
For example, someone creates a fake Authenticate dialog to get my root password. How to know if it is real or fake?
password security authentication policykit
add a comment |Â
up vote
28
down vote
favorite
For example, someone creates a fake Authenticate dialog to get my root password. How to know if it is real or fake?
password security authentication policykit
add a comment |Â
up vote
28
down vote
favorite
up vote
28
down vote
favorite
For example, someone creates a fake Authenticate dialog to get my root password. How to know if it is real or fake?
password security authentication policykit
For example, someone creates a fake Authenticate dialog to get my root password. How to know if it is real or fake?
password security authentication policykit
password security authentication policykit
edited Aug 12 '14 at 3:38
Eliah Kagan
79.7k20222359
79.7k20222359
asked Jul 16 '14 at 8:48
user3683331
14113
14113
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
23
down vote
So you're [probably] looking at a PolicyKit escalation prompt there. Anybody without one of those who wants to play along can just run run pkexec echo
(or something like that) and they'll get something similar.
How can we check it's really PolicyKit, not some custom-made phishing window?
Well you can get information about a Window with xprop
and you can get command information with ps
so let's combine them! Before we steam on, because we're being super-paranoid here, I'm using full paths just in case somebody has added a local hacked copy of any of these commands. Here's me running it on my pkexec echo
box:
$ /bin/ps $(/usr/bin/xprop _NET_WM_PID | /usr/bin/awk 'print $NF')
PID TTY STAT TIME COMMAND
3989 ? Sl 0:00 /usr/lib/kde4/libexec/polkit-kde-authentication-agent-1
So as far as we can tell (note that I'm a KDE user) this is a legitimate prompt. It's not running off some local script so as long as something evil hasn't already rooted the system (but hey, why would they need our password again?), we're probably safe.
How can we tell what it's going to do?
In the case of gksu
, kdesu
and pkexec
the prompts are fairly explicit about what they're going to run. In the case of the first two the command above will tell you what they're planning on running:
$ /bin/ps $(/usr/bin/xprop _NET_WM_PID | /usr/bin/awk 'print $NF')
PID TTY STAT TIME COMMAND
10395 ? Sl 0:00 /usr/lib/kde4/libexec/kdesu -u root -c /usr/sbin/synaptic
In the case of PolicyKit, you can click that details tab and you'll see which permission it wants to execute. In KDE you'll also see the caller PID which can be looked up (ps <PID>
). Here's what it looks like in KDE:
You can hover over the action and get the PolicyKit policy it wants to execute. In Ubuntu the policy is shown by default. These policies can be looked up. The one above comes from /usr/share/polkit-1/actions/org.kubuntu.qaptworker2.policy
and a service specified in /usr/share/dbus-1/system-services/org.kubuntu.qaptworker2.service
. You can see what's being run and by whom. And these services can only be added by root so again, unless you've already been rooted, you can probably trust these.
But don't blindly trust PolicyKit!
PolicyKit has these rules and services so select actions can be performed as root without having to run the entire process like that. You need to be vigilant though. Obviously if you're running gnome-calculator
and a org.freedesktop.policykit.exec
prompt pops up, something's dodgy.
It might be nothing but investigate before you stick your password in. After is too late.
And even if it's all legit, who's to say you don't have a keylogger stealing all your passwords anyway? Or something overriding $PATH
or that has dumped something horrible in your ~/.bashrc
that's making it look like you haven't been hacked? I'm fairly sure with enough concentration you could circumvent all the detection procedures above.
Sleep well.
Softwares liketripwire
can help to check authenticity of a file, but they should installed very early.
â Registered User
Jul 16 '14 at 13:04
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
23
down vote
So you're [probably] looking at a PolicyKit escalation prompt there. Anybody without one of those who wants to play along can just run run pkexec echo
(or something like that) and they'll get something similar.
How can we check it's really PolicyKit, not some custom-made phishing window?
Well you can get information about a Window with xprop
and you can get command information with ps
so let's combine them! Before we steam on, because we're being super-paranoid here, I'm using full paths just in case somebody has added a local hacked copy of any of these commands. Here's me running it on my pkexec echo
box:
$ /bin/ps $(/usr/bin/xprop _NET_WM_PID | /usr/bin/awk 'print $NF')
PID TTY STAT TIME COMMAND
3989 ? Sl 0:00 /usr/lib/kde4/libexec/polkit-kde-authentication-agent-1
So as far as we can tell (note that I'm a KDE user) this is a legitimate prompt. It's not running off some local script so as long as something evil hasn't already rooted the system (but hey, why would they need our password again?), we're probably safe.
How can we tell what it's going to do?
In the case of gksu
, kdesu
and pkexec
the prompts are fairly explicit about what they're going to run. In the case of the first two the command above will tell you what they're planning on running:
$ /bin/ps $(/usr/bin/xprop _NET_WM_PID | /usr/bin/awk 'print $NF')
PID TTY STAT TIME COMMAND
10395 ? Sl 0:00 /usr/lib/kde4/libexec/kdesu -u root -c /usr/sbin/synaptic
In the case of PolicyKit, you can click that details tab and you'll see which permission it wants to execute. In KDE you'll also see the caller PID which can be looked up (ps <PID>
). Here's what it looks like in KDE:
You can hover over the action and get the PolicyKit policy it wants to execute. In Ubuntu the policy is shown by default. These policies can be looked up. The one above comes from /usr/share/polkit-1/actions/org.kubuntu.qaptworker2.policy
and a service specified in /usr/share/dbus-1/system-services/org.kubuntu.qaptworker2.service
. You can see what's being run and by whom. And these services can only be added by root so again, unless you've already been rooted, you can probably trust these.
But don't blindly trust PolicyKit!
PolicyKit has these rules and services so select actions can be performed as root without having to run the entire process like that. You need to be vigilant though. Obviously if you're running gnome-calculator
and a org.freedesktop.policykit.exec
prompt pops up, something's dodgy.
It might be nothing but investigate before you stick your password in. After is too late.
And even if it's all legit, who's to say you don't have a keylogger stealing all your passwords anyway? Or something overriding $PATH
or that has dumped something horrible in your ~/.bashrc
that's making it look like you haven't been hacked? I'm fairly sure with enough concentration you could circumvent all the detection procedures above.
Sleep well.
Softwares liketripwire
can help to check authenticity of a file, but they should installed very early.
â Registered User
Jul 16 '14 at 13:04
add a comment |Â
up vote
23
down vote
So you're [probably] looking at a PolicyKit escalation prompt there. Anybody without one of those who wants to play along can just run run pkexec echo
(or something like that) and they'll get something similar.
How can we check it's really PolicyKit, not some custom-made phishing window?
Well you can get information about a Window with xprop
and you can get command information with ps
so let's combine them! Before we steam on, because we're being super-paranoid here, I'm using full paths just in case somebody has added a local hacked copy of any of these commands. Here's me running it on my pkexec echo
box:
$ /bin/ps $(/usr/bin/xprop _NET_WM_PID | /usr/bin/awk 'print $NF')
PID TTY STAT TIME COMMAND
3989 ? Sl 0:00 /usr/lib/kde4/libexec/polkit-kde-authentication-agent-1
So as far as we can tell (note that I'm a KDE user) this is a legitimate prompt. It's not running off some local script so as long as something evil hasn't already rooted the system (but hey, why would they need our password again?), we're probably safe.
How can we tell what it's going to do?
In the case of gksu
, kdesu
and pkexec
the prompts are fairly explicit about what they're going to run. In the case of the first two the command above will tell you what they're planning on running:
$ /bin/ps $(/usr/bin/xprop _NET_WM_PID | /usr/bin/awk 'print $NF')
PID TTY STAT TIME COMMAND
10395 ? Sl 0:00 /usr/lib/kde4/libexec/kdesu -u root -c /usr/sbin/synaptic
In the case of PolicyKit, you can click that details tab and you'll see which permission it wants to execute. In KDE you'll also see the caller PID which can be looked up (ps <PID>
). Here's what it looks like in KDE:
You can hover over the action and get the PolicyKit policy it wants to execute. In Ubuntu the policy is shown by default. These policies can be looked up. The one above comes from /usr/share/polkit-1/actions/org.kubuntu.qaptworker2.policy
and a service specified in /usr/share/dbus-1/system-services/org.kubuntu.qaptworker2.service
. You can see what's being run and by whom. And these services can only be added by root so again, unless you've already been rooted, you can probably trust these.
But don't blindly trust PolicyKit!
PolicyKit has these rules and services so select actions can be performed as root without having to run the entire process like that. You need to be vigilant though. Obviously if you're running gnome-calculator
and a org.freedesktop.policykit.exec
prompt pops up, something's dodgy.
It might be nothing but investigate before you stick your password in. After is too late.
And even if it's all legit, who's to say you don't have a keylogger stealing all your passwords anyway? Or something overriding $PATH
or that has dumped something horrible in your ~/.bashrc
that's making it look like you haven't been hacked? I'm fairly sure with enough concentration you could circumvent all the detection procedures above.
Sleep well.
Softwares liketripwire
can help to check authenticity of a file, but they should installed very early.
â Registered User
Jul 16 '14 at 13:04
add a comment |Â
up vote
23
down vote
up vote
23
down vote
So you're [probably] looking at a PolicyKit escalation prompt there. Anybody without one of those who wants to play along can just run run pkexec echo
(or something like that) and they'll get something similar.
How can we check it's really PolicyKit, not some custom-made phishing window?
Well you can get information about a Window with xprop
and you can get command information with ps
so let's combine them! Before we steam on, because we're being super-paranoid here, I'm using full paths just in case somebody has added a local hacked copy of any of these commands. Here's me running it on my pkexec echo
box:
$ /bin/ps $(/usr/bin/xprop _NET_WM_PID | /usr/bin/awk 'print $NF')
PID TTY STAT TIME COMMAND
3989 ? Sl 0:00 /usr/lib/kde4/libexec/polkit-kde-authentication-agent-1
So as far as we can tell (note that I'm a KDE user) this is a legitimate prompt. It's not running off some local script so as long as something evil hasn't already rooted the system (but hey, why would they need our password again?), we're probably safe.
How can we tell what it's going to do?
In the case of gksu
, kdesu
and pkexec
the prompts are fairly explicit about what they're going to run. In the case of the first two the command above will tell you what they're planning on running:
$ /bin/ps $(/usr/bin/xprop _NET_WM_PID | /usr/bin/awk 'print $NF')
PID TTY STAT TIME COMMAND
10395 ? Sl 0:00 /usr/lib/kde4/libexec/kdesu -u root -c /usr/sbin/synaptic
In the case of PolicyKit, you can click that details tab and you'll see which permission it wants to execute. In KDE you'll also see the caller PID which can be looked up (ps <PID>
). Here's what it looks like in KDE:
You can hover over the action and get the PolicyKit policy it wants to execute. In Ubuntu the policy is shown by default. These policies can be looked up. The one above comes from /usr/share/polkit-1/actions/org.kubuntu.qaptworker2.policy
and a service specified in /usr/share/dbus-1/system-services/org.kubuntu.qaptworker2.service
. You can see what's being run and by whom. And these services can only be added by root so again, unless you've already been rooted, you can probably trust these.
But don't blindly trust PolicyKit!
PolicyKit has these rules and services so select actions can be performed as root without having to run the entire process like that. You need to be vigilant though. Obviously if you're running gnome-calculator
and a org.freedesktop.policykit.exec
prompt pops up, something's dodgy.
It might be nothing but investigate before you stick your password in. After is too late.
And even if it's all legit, who's to say you don't have a keylogger stealing all your passwords anyway? Or something overriding $PATH
or that has dumped something horrible in your ~/.bashrc
that's making it look like you haven't been hacked? I'm fairly sure with enough concentration you could circumvent all the detection procedures above.
Sleep well.
So you're [probably] looking at a PolicyKit escalation prompt there. Anybody without one of those who wants to play along can just run run pkexec echo
(or something like that) and they'll get something similar.
How can we check it's really PolicyKit, not some custom-made phishing window?
Well you can get information about a Window with xprop
and you can get command information with ps
so let's combine them! Before we steam on, because we're being super-paranoid here, I'm using full paths just in case somebody has added a local hacked copy of any of these commands. Here's me running it on my pkexec echo
box:
$ /bin/ps $(/usr/bin/xprop _NET_WM_PID | /usr/bin/awk 'print $NF')
PID TTY STAT TIME COMMAND
3989 ? Sl 0:00 /usr/lib/kde4/libexec/polkit-kde-authentication-agent-1
So as far as we can tell (note that I'm a KDE user) this is a legitimate prompt. It's not running off some local script so as long as something evil hasn't already rooted the system (but hey, why would they need our password again?), we're probably safe.
How can we tell what it's going to do?
In the case of gksu
, kdesu
and pkexec
the prompts are fairly explicit about what they're going to run. In the case of the first two the command above will tell you what they're planning on running:
$ /bin/ps $(/usr/bin/xprop _NET_WM_PID | /usr/bin/awk 'print $NF')
PID TTY STAT TIME COMMAND
10395 ? Sl 0:00 /usr/lib/kde4/libexec/kdesu -u root -c /usr/sbin/synaptic
In the case of PolicyKit, you can click that details tab and you'll see which permission it wants to execute. In KDE you'll also see the caller PID which can be looked up (ps <PID>
). Here's what it looks like in KDE:
You can hover over the action and get the PolicyKit policy it wants to execute. In Ubuntu the policy is shown by default. These policies can be looked up. The one above comes from /usr/share/polkit-1/actions/org.kubuntu.qaptworker2.policy
and a service specified in /usr/share/dbus-1/system-services/org.kubuntu.qaptworker2.service
. You can see what's being run and by whom. And these services can only be added by root so again, unless you've already been rooted, you can probably trust these.
But don't blindly trust PolicyKit!
PolicyKit has these rules and services so select actions can be performed as root without having to run the entire process like that. You need to be vigilant though. Obviously if you're running gnome-calculator
and a org.freedesktop.policykit.exec
prompt pops up, something's dodgy.
It might be nothing but investigate before you stick your password in. After is too late.
And even if it's all legit, who's to say you don't have a keylogger stealing all your passwords anyway? Or something overriding $PATH
or that has dumped something horrible in your ~/.bashrc
that's making it look like you haven't been hacked? I'm fairly sure with enough concentration you could circumvent all the detection procedures above.
Sleep well.
edited Jul 16 '14 at 10:12
answered Jul 16 '14 at 9:44
Oliâ¦
215k85544752
215k85544752
Softwares liketripwire
can help to check authenticity of a file, but they should installed very early.
â Registered User
Jul 16 '14 at 13:04
add a comment |Â
Softwares liketripwire
can help to check authenticity of a file, but they should installed very early.
â Registered User
Jul 16 '14 at 13:04
Softwares like
tripwire
can help to check authenticity of a file, but they should installed very early.â Registered User
Jul 16 '14 at 13:04
Softwares like
tripwire
can help to check authenticity of a file, but they should installed very early.â Registered User
Jul 16 '14 at 13:04
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f498449%2fhow-to-know-if-a-authenticate-box-is-real-or-fake%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password