Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #126635
| From | Les Cargill <lcargill99@comcast.com> |
|---|---|
| Newsgroups | comp.lang.c |
| Subject | Re: System V Shared Memory Security |
| Date | 2018-02-12 21:00 -0600 |
| Organization | A noiseless patient Spider |
| Message-ID | <p5tk34$65u$1@dont-email.me> (permalink) |
| References | <c0a908ed-66cc-40c1-8ed5-2d34f42a280f@googlegroups.com> <p5lojv$i4r$1@dont-email.me> <e__fC.9688$yv1.116@fx07.iad> <p5q0j8$unb$1@dont-email.me> <HKlgC.10148$eZ5.9513@fx19.iad> |
Scott Lurndal wrote: > Les Cargill <lcargill99@comcast.com> writes: >> Scott Lurndal wrote: >>> Les Cargill <lcargill99@comcast.com> writes: >>>> hwding wrote: >>>>> Is it possible to attach to an existing SHM owned >>>>> by other process group and alter its content? >>>>> >>>>> For example: >>>>> # ipcs >>>>> ------ Shared Memory Segments -------- >>>>> key shmid owner perms bytes nattch status >>>>> 0x01050404 196608 abcd 777 4096 2 >>>>> >>>>> Then we attched to this segment using id 196608: >>>>> shmat(196608, NULL, 0); >>>>> Read then alter its data to attack these processes. >>>>> >>>>> Is there a necessity to protect the sensitive content >>>>> when two processes are using a shared memory? >>>> >>>> Yes. >>>> >>>>> By what >>>>> means? >>>>> >>>> >>>> Sempahores. Specifically, mutexes: >>>> >>> >>> man 3 pthread_mutex_lock >>> man 3 pthread_mutexattr_setpshared >>> >> >> I don't think you can identify posix objects across full processes. > > That's the entire point of "pthread_mutexattr_setpshared". > Ooooohhh! Nice. I did not know that. Thanks! -- Les Cargill
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
System V Shared Memory Security hwding <m@amastigote.com> - 2018-02-05 17:26 -0800
Re: System V Shared Memory Security Ian Collins <ian-news@hotmail.com> - 2018-02-06 14:30 +1300
Re: System V Shared Memory Security hwding <m@amastigote.com> - 2018-02-05 17:33 -0800
Re: System V Shared Memory Security Keith Thompson <kst-u@mib.org> - 2018-02-05 18:14 -0800
Re: System V Shared Memory Security Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2018-02-05 20:32 -0500
Re: System V Shared Memory Security Les Cargill <lcargill99@comcast.com> - 2018-02-09 21:28 -0600
Re: System V Shared Memory Security scott@slp53.sl.home (Scott Lurndal) - 2018-02-11 17:23 +0000
Re: System V Shared Memory Security Les Cargill <lcargill99@comcast.com> - 2018-02-11 12:09 -0600
Re: System V Shared Memory Security scott@slp53.sl.home (Scott Lurndal) - 2018-02-12 19:16 +0000
Re: System V Shared Memory Security "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2018-02-12 12:10 -0800
Re: System V Shared Memory Security Les Cargill <lcargill99@comcast.com> - 2018-02-12 21:00 -0600
Re: System V Shared Memory Security "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2018-02-14 00:49 +0800
csiph-web