lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <94939205.20040121100158@SECURITY.NNOV.RU>
From: 3APA3A at SECURITY.NNOV.RU (3APA3A)
Subject: local SYSTEM on Windows vs. local root on Unix

Dear KF,

For  standalone  box  things  are  same.  One can think it's possible to
protect  file  system  against  Local  System  under  Windows,  but this
protection  can  be  bypassed.  One  may  think  it's  possible to limit
syscalls for root under Unix - but Windows can be protected in same way.

For  network  (if  can  you get access to network having access to local
superuser  account) everything depends on network infrastructure, not on
host  OS,  but  NFS  is usually less secure against this kind of attacks
comparing to CIFS.

--Tuesday, January 20, 2004, 12:20:58 AM, you wrote to full-disclosure@...ts.netsys.com:

K> I am currious to know what you folks think the differences are between
K> obtaining local SYSTEM on a win32 box and obtaining root on a Unix machine.

K> Same thing?
K> Different?
K> One is worse than the other? Which one? Why?

K> *flame on*
K> -KF

K> _______________________________________________
K> Full-Disclosure - We believe in it.
K> Charter: http://lists.netsys.com/full-disclosure-charter.html


-- 
~/ZARAZA
?? ? ? ?????, ??????, ??????? ?????? - ????? ??????
??? ????? ??????? ????????, ?????? ???????. (????)


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ