Ros-dev

ros-dev@reactos.org

5790 discussions

Re: [ros-dev] Security policy for FAT partition driver?

by Steven Edwards

Hi, --- Phillip Susi <psusi(a)cfl.rr.com> wrote: > How would you reconcile the two different sets of owner and access > information associated with the file? For instance, if someone creates > a file on the partition from Linux, then you mount it with ROS, who owns > the file? Who has access to it? Linux would only place some > meaningless uid and chmod mask in the inode, so how would ROS come up > with a sensible security descriptor for the file when one does not > already exist? Windows would have this same problem with NTFS on Linux. If I am under Linux and make changes to files and create files how does linux-NTFS assign the proper SID and such to the files? This has been a long time problem that NTFS has with taking a drive from one Windows box to another. Its the same situation and mostly pointless. 99% of new ReactOS are not going to care and the resources we get from having a better filesystem now can be put in to developing a NTFS replacement. > These are the kinds of problems that make attempts for ReactOS to share > a unix filesystem ( and vice versa ) kludgey at best. If the ext2fsd supported ext3 journals there would be nothing wrong with using it. I mean hell right now ReactOS does not have a security subsystem so this whole discussion is a moot point. Unless you feel like implementing lsass =) Thanks Steven Discover Yahoo! Find restaurants, movies, travel and more fun for the weekend. Check it out! http://discover.yahoo.com/weekend.html

20 years, 5 months

Re: [ros-svn] [weiden] 15241:

by Thomas Weidenmueller

weiden(a)svn.reactos.com wrote: > Updated files: > trunk/reactos/lib/cpl/intl/locale.c Sorry, I forgot the commit message. the NULL termination character of the string should be saved as well, so calculate the buffer size correctly.

20 years, 5 months

Networking

by James Tabor

Hi, Here is some networking dumps, I have a rtl8029 with io D000 and irq B, (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 ne2000!NICIndicatePacket: Indicating (64) bytes. (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (io/irp.c:877) Thread with dead IRPs!Assertion FALSE failed at io/irp.c:878 Entered debugger on embedded INT3 at 0x0008:0x800058e3. kdb:> bt Eip: <ntoskrnl.exe:58e4 (ke/i386/brkpoint.c:31 (DbgBreakPoint))> Frames: <ntoskrnl.exe:4c63e (io/irp.c:881 (IoCancelThreadIo))> <ntoskrnl.exe:7f603 (ps/kill.c:308 (PspExitThread))> <ntoskrnl.exe:7f9ca (ps/kill.c:500 (NtTerminateProcess))> <ntoskrnl.exe:36d2 (/tmp/cctdxNWF.s:180 (KiSystemService))> <kernel32.dll:27e20 (process/proc.c:593 (ExitProcess))> <ping.EXE:11f6> <ping.EXE:1238> <kernel32.dll:289b1 (process/create.c:331 (BaseProcessStart))> <deadbeef> kdb:> cont ne2000!NICIndicatePacket: Indicating (142) bytes. ne2000!NICIndicatePacket: Indicating (142) bytes. LAN WORKER BUSY 9e3e0390 80e10c18 ne2000!NICIndicatePacket: Indicating (142) bytes. LAN WORKER BUSY 9e3e0390 80e12738 ne2000!NICIndicatePacket: Indicating (142) bytes. LAN WORKER BUSY 9e3e0390 80e187f8 ne2000!NICIndicatePacket: Indicating (64) bytes. LAN WORKER BUSY 9e3e0390 80e1ecb8 ne2000!NICIndicatePacket: Indicating (64) bytes. LAN WORKER BUSY 9e3e0390 80e2cd28 ne2000!NICIndicatePacket: Indicating (142) bytes. LAN WORKER BUSY 9e3e0390 80e73c80 ne2000!NICIndicatePacket: Indicating (142) bytes. LAN WORKER BUSY 9e3e0390 80ef4b30 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0 (io/irp.c:877) Thread with dead IRPs!Assertion FALSE failed at io/irp.c:878 Entered debugger on embedded INT3 at 0x0008:0x800058e3. kdb:> bt Eip: <ntoskrnl.exe:58e4 (ke/i386/brkpoint.c:31 (DbgBreakPoint))> Frames: <ntoskrnl.exe:4c63e (io/irp.c:881 (IoCancelThreadIo))> <ntoskrnl.exe:7f603 (ps/kill.c:308 (PspExitThread))> <ntoskrnl.exe:7f9ca (ps/kill.c:500 (NtTerminateProcess))> <ntoskrnl.exe:36d2 (/tmp/cctdxNWF.s:180 (KiSystemService))> <kernel32.dll:27e20 (process/proc.c:593 (ExitProcess))> <ping.EXE:11f6> <ping.EXE:1238> <kernel32.dll:289b1 (process/create.c:331 (BaseProcessStart))> <deadbeef> kdb:> cont ne2000!NICIndicatePacket: Indicating (64) bytes. (dispatch.c:166)(dispatch) Select: 0 ne2000!NICIndicatePacket: Indicating (142) bytes. ne2000!NICIndicatePacket: Indicating (142) bytes. LAN WORKER BUSY 9e3e0390 812618f8 (dispatch.c:166)(dispatch) Select: 0 (dispatch.c:166)(dispatch) Select: 0

20 years, 5 months

RE: [ros-diffs] [greatlrd] 15238: Fix two spelling error

by Casper Hornstrup

You might as well spell stopwach as stopwatch while you are there.

20 years, 5 months

Re: [ros-dev] Security policy for FAT partition driver?

by Steven Edwards

Hi Rob, --- Robert Shearman <rob(a)codeweavers.com> wrote: > You can do it the same way Samba does it by using xattrs. It's a shame > that so few ReactOS developers turned up to WineConf as the Samba team > did a presentation on this. Yes that has been my suggestion. In my mind most people wont upgrade from Windows to ReactOS as they already have a Windows license so ReactOS like Linux wont have much need for NTFS. Right now there is a ext2fsd that mostly works with ReactOS but currently it has some problems with ext3. I am aware that you can do xattr support with ext2 and have suggested this to the ReactOS team. Thanks Steven __________________________________ Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone. http://mobile.yahoo.com/learn/mail

20 years, 5 months

Re: [ros-dev] Security policy for FAT partition driver?

by Steven Edwards

Hi Mike, --- Mike Nordell <tamlin(a)algonet.se> wrote: > Reparse points is a feature of NTFS I've myself used since over half a > decade now. As I know I'm not alone using both junction points and volume > mount points, I'd think scraping the barrel might be "somewhat" misleading. I think Robs point is the same as mine. Right now 99% of the world does not care about those features where they do care about the other 50% of the features ReactOS does not currently implement. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250

20 years, 5 months

RE: [ros-dev] Security policy for FAT partition driver?

by Waldo Alvarez Cañizares

Hi: Remember the another filesystem driver could be installed in WinNT as part of the ReactOS setup in those dual boot scenarios. Maybe WinNT could boot from that X filesystem too. You won't be using an NTFS partition or creating it and you won't need to create a different driver for NT since ROS driver should run ok on NT. Regards Waldo ________________________________ From: ros-dev-bounces(a)reactos.com on behalf of Murphy, Ged (Bolton) Sent: Wed 5/11/2005 10:22 AM To: 'ReactOS Development List' Subject: RE: [ros-dev] Security policy for FAT partition driver? Jonathan Wilson wrote: > Basicly, there are 2 kinds of users. > There are those who have windows and and NTFS partition and want to access > it from ROS. (perhaps dual boot ROS and win from the one NTFS partition > ambie if that is something ROS can be made to do). These people can use > ntfs.sys from MS since they have windows. > > Then there are those who dont have windows, dont have an existing NTFS > partion and dont have a copy of ntfs.sys. > Those people can use whatever other solution we come up with (ReactOS > implementation of NTFS, some unix FS like ext/reiser etc or whatever else > we come up with). That seems to make perfect sense. Why would anyone need/want to use NTFS if they don't need to access existing NTFS drives? If they do have existing NTFS drives, then as Jonathan says, they should also have the driver from MS to access it. Ged. ************************************************************************ The information contained in this message or any of its attachments is confidential and is intended for the exclusive use of the addressee. The information may also be legally privileged. The views expressed may not be company policy, but the personal views of the originator. If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited. If you have received this message in error, please contact postmaster(a)exideuk.co.uk <mailto:postmaster@exideuk.co.uk> and then delete this message. Exide Technologies is an industrial and transportation battery producer and recycler with operations in 89 countries. Further information can be found at www.exide.com _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev

20 years, 5 months

RE: [ros-dev] Security policy for FAT partition driver?

by Waldo Alvarez Cañizares

Hi: Well that's right until you try to access an encrypted file system. regards Waldo ________________________________ From: ros-dev-bounces(a)reactos.com on behalf of Mike Swanson Sent: Tue 5/10/2005 6:30 PM To: ReactOS Development List Subject: Re: [ros-dev] Security policy for FAT partition driver? Philip: Any filesystem is plenty insecure if you are accessing it via a bootable CD-ROM or other such measures. Also, ext2 already has a journal, it's called ext3. -- Mike _______________________________________________ Ros-dev mailing list Ros-dev(a)reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev

20 years, 5 months

CIDHandles bug ?

by open.proyects＠gmail.com

Hello, I am playing with DebugView from SysInternals and i noticed that ROS KeBugChecks in NtOpenProccess (line 878): if (ClientId->UniqueThread) { /* Get the Process */ if (ClientId->UniqueThread == (HANDLE)-1) KEBUGCHECK(0); <===== HERE DPRINT("Opening by Thread ID: %x\n", ClientId->UniqueThread); Status = PsLookupProcessThreadByCid(ClientId, &Process, &Thread); DPRINT("Found: %x\n", Process); It looks like that UniqueThread holds value -1. I look in NtCreateThread and it has CID handle creation implemented (PsCreateCidHandle and friends ...) I only get KeBugCheck with DebugView (another exes run properly). If you force a false evaluation (for example: if ((ClientId->UniqueThread)&&(0))) NtOpenProcess does a LookUp by proccess cid and DebugView run fine Any idea?

20 years, 5 months

Re: Ros-dev Digest, Vol 9, Issue 21

by David Eckert

It'd be interesting to see one develop a filesystem for ReactOS, but AS a filesystem designed explicitly for the OS itself. It could be called "ROSfs" or something similar.

20 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev