Sponsored Content
Top Forums Shell Programming and Scripting Script protection against changes Post 302732335 by dover07 on Saturday 17th of November 2012 08:19:59 AM
Old 11-17-2012
Script protection against changes

Hi everyone,

I´m trying to protect the scripts I have made from changes.

At my office I´m the one who research improvements on daily tasks, and I´ve done many scripts, that I share with my partners.I´m tired because they take my scripts and make their owns with new features that don´t share or keep secret... so I need to prevent them to open my scripts and modify it.

The use os user permissions is not possible because I have to share my scripts also with operators, and they need permission to Read and eXecute, so anyone can open my script to see the code.

Is there any way to encode it?

I´m just a beginner on scripting and I don´t know anything about compilation. Please give me a hand!!!

Before asking here I´ve been searching on internet... but I haven´t find anything useful.

Thanks!
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Override protection.....

I am having this problem......when I run this script: print -n "Enter file name to be deleted: " read answer if then rm $name else echo "No such file with the name: $name exists" fi I was trying to test my script for errors, and basically when the user had files with the rights: 400,... (1 Reply)
Discussion started by: Makaveli.2003
1 Replies

2. Filesystems, Disks and Memory

protection schemes

Consider a system that supports 5,000 users. Suppose you want 4,990 of these users to be able to access one file How would you specify this protection scheme in UNIX (4 Replies)
Discussion started by: mattyboy
4 Replies

3. Cybersecurity

spam and protection?

Hello, Long time ago we used to suffer from relay and users using your own mailservers to spam but thanks god for auth-before-pop. But now i'm facing small problem with someone which us he is spaning using whatever mailserver with your@email.address.com and when these emails go to unknown... (10 Replies)
Discussion started by: Bashar
10 Replies

4. Shell Programming and Scripting

override protection 644 (yes/no)?

Hi pls help me out to short out this problem rm PAB113_011.out rm: PAB113_011.out: override protection 644 (yes/no)? n If i give y it remove the file. But i added the rm command as a part of ksh file and i tried to remove the file. Its not removing and the the file prompting as... (9 Replies)
Discussion started by: sri_aue
9 Replies

5. Linux

file security/protection

Hi All I am working on a site to help newbie to learn linux for free. demo.freelinuxconsole.info there is only one file index.php its been able to rename or deleted. Kindly let me know what permissions should i give to secure this file from editing or deleting by others. (8 Replies)
Discussion started by: smithjack
8 Replies

6. Shell Programming and Scripting

Password protection in unix

How to create a file in UNIX which is password protected ? Thanks and Regards, Neeraj (5 Replies)
Discussion started by: neeraj617
5 Replies

7. IP Networking

Protection against arp spoofing

Hi, I'm trying to find a way to protect my network against arp spoofing. What it is: An attacker sends fake arp packets in the network, identifying himself as the router. All network traffic is then redirected to this attacker. How to protect myself: In my opinion, the best possible... (2 Replies)
Discussion started by: chrisperry
2 Replies

8. Homework & Coursework Questions

Protection and special characters

I am learning from the class how to protect the special characters and the script that I wrote here does not work when I am trying to pick up a single quote. It would complaint about parentheses problem. Please, someone could enlighten me. Thanks in advance, Scopiop Input file Hi, * ?... (2 Replies)
Discussion started by: scopiop
2 Replies
DEVSCRIPTS.CONF(5)						File Formats Manual						DEVSCRIPTS.CONF(5)

NAME
devscripts.conf - configuration file for the devscripts package DESCRIPTION
The devscripts package provides a collection of scripts which may be of use to Debian developers and others wishing to build Debian pack- ages. Many of these have options which can be configured on a system-wide and per-user basis. Every script in the devscripts package which makes use of values from these configuration files describes the specific settings recognised in its own manpage. (For a list of the scripts, either see /usr/share/doc/devscripts/README.gz or look at the output of dpkg -L devscripts | grep /usr/bin.) The two configuration files are /etc/devscripts.conf for system-wide defaults and ~/.devscripts for per-user settings. They are written with bash(1) syntax, but should only have comments and simple variable assignments in them; they are both sourced (if present) by many of the devscripts scripts. Variables corresponding to simple switches should have one of the values yes and no; any other setting is regarded as equivalent to the default setting. All variable names are written in uppercase, and begin with the script name. Package-wide variables begin with "DEVSCRIPTS", and are listed below, as well as in the relevant manpages. For a list of all of the available options variables, along with their default settings, see the example configuration file /usr/share/doc/devscripts/devscripts.conf.ex. This is copied to /etc/devscripts.conf when the devscripts package is first installed. Information about configuration options introduced in newer versions of the package will be appended to /etc/devscripts.conf when the pack- age is upgraded. Every script which reads the configuration files can be forced to ignore them by using --no-conf as the first command-line option. PACKAGE-WIDE VARIABLES The currently recognised package-wide variables are: DEVSCRIPTS_CHECK_DIRNAME_LEVEL, DEVSCRIPTS_CHECK_DIRNAME_REGEX These variables control scripts which change directory to find a debian/changelog file or suchlike, and some other miscellaneous cases. In order to prevent unwanted, even possibly dangerous, behaviour, these variables control when actions will be performed. The scripts which currently make use of these variables are: debc, debchange/dch, debclean, debi, debrelease, debuild and uscan, but this list may change with time (and I may not remember to update this manpage). Please see the manpages of individual scripts for details of the specific behaviour for each script. SEE ALSO
devscripts(1) and /usr/share/doc/devscripts/README.gz. AUTHOR
This manpage was written for the devscripts package by the package maintainer Julian Gilbey <jdg@debian.org>. DEBIAN
Debian Utilities DEVSCRIPTS.CONF(5)
All times are GMT -4. The time now is 02:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy