Sponsored Content
Full Discussion: Sandboxes for developers
Operating Systems Linux Debian Sandboxes for developers Post 302504410 by mark54g on Monday 14th of March 2011 01:43:44 PM
Old 03-14-2011
I'm in a similar boat, but I'm actually hoping for a budget for this.

My goal is to use VMware, Hyperic for monitoring, and Spacewalk (redhat shop, no RHN satellite).
 

3 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Honk if you love Solaris Developers!

Are you a developer for Solaris products? If so, check this out: http://sdc.sun.com/solaris8/ The media kit that comes includes the entire media pack (Solaris 8) for both Intel and Sparc architectures, and a cool spill-proof coffe mug (for those all-nighters you're going to pull playing with... (1 Reply)
Discussion started by: LivinFree
1 Replies

2. Android

Any Android Developers in the Forums?

I'm about to make the switch over to Android OS for my mobile phone. I'm thinking my first Android phone might be something like a Samsung Galaxy S or an HTC Desire HD, or I might wait for one of the new Android tablets coming out later this year (like the Samsung 7" tablet on Android). Was... (10 Replies)
Discussion started by: Neo
10 Replies

3. What is on Your Mind?

Dear Debian-Developers

As strolling along this thread, what is on my mind I am still quite upset about the security guidelines set by the developers of Debian or any distro based upon Debian. For a while I have been really blissed using squeeze. No trouble at all with almost nothing, but using wheezy trouble came up with... (9 Replies)
Discussion started by: 1in10
9 Replies
SANDBOX_INIT(3) 					   BSD Library Functions Manual 					   SANDBOX_INIT(3)

NAME
sandbox_init, sandbox_free_error -- set process sandbox (DEPRECATED) SYNOPSIS
#include <sandbox.h> int sandbox_init(const char *profile, uint64_t flags, char **errorbuf); void sandbox_free_error(char *errorbuf); DESCRIPTION
The sandbox_init() and sandbox_free_error() functions are DEPRECATED. Developers who wish to sandbox an app should instead adopt the App Sandbox feature described in the App Sandbox Design Guide. The sandbox_init() function places the current process into a sandbox(7). The NUL-terminated string profile specifies the profile to be used to configure the sandbox. The flags specified are formed by or'ing the following values: SANDBOX_NAMED The profile argument specifies a sandbox profile named by one of the constants given in the AVAILABLE PROFILES sec- tion below. The out parameter *errorbuf will be set according to the error status. RETURN VALUES
Upon successful completion of sandbox_init(), a value of 0 is returned and *errorbuf is set to NULL. In the event of an error, a value of -1 is returned and *errorbuf is set to a pointer to a NUL-terminated string describing the error. This string may contain embedded newlines. This error information is suitable for developers and is not intended for end users. This pointer should be passed to sandbox_free_error(3) to release the allocated storage when it is no longer needed. AVAILABLE PROFILES
The following are brief descriptions of each available profile. Keep in mind that sandbox(7) restrictions are typically enforced at resource acquisition time. kSBXProfileNoInternet TCP/IP networking is prohibited. kSBXProfileNoNetwork All sockets-based networking is prohibited. kSBXProfileNoWrite File system writes are prohibited. kSBXProfileNoWriteExceptTemporary File system writes are restricted to the temporary folder /var/tmp and the folder specified by the confstr(3) configuration variable _CS_DARWIN_USER_TEMP_DIR. kSBXProfilePureComputation All operating system services are prohibited. SEE ALSO
sandbox-exec(1), sandbox(7), sandboxd(8) Mac OS X November 15, 2011 Mac OS X
All times are GMT -4. The time now is 08:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy