Greg Chaplin wrote:
I've been racking my brains trying to figure out a way of putting
certain groups in our development account off-limits. I'm trying to
set up source control procedures, such that the original files are
kept in the "secure" groups. [snip]
All our programmers have AM capability, we have the Vesoft trilogy
(MPEX, Security & Veaudit) and are on MPE/iX 5.5.
Anyone got any hints or ideas? I don't think we need to buy a
full-blown source control package.
----------
Greg,
What I would recommend is:
1.) Place the files in a different account. This way you don't have
to worry about whether or not the developers have AM capability.
2.) Worry about whether or not the developers have AM capability.
I'm going through a similar process. I've inherited some
purchased/home grown software for which I'm attempting to locate and
control the source code and executables. I too have developers with AM
capability. As a short-term method of control, I'm moving source and
executables to another account (to which the developers don't have
direct write capability.) In our situation, the development personnel
also function as "consultants". If I immediately remove AM capability,
I limit their ability to support end-users, and become the bad guy. By
moving the source code to a read-only account, they still have access to
read/develop, but even with AM capability, they can't modify. To remove
AM capability, give the developers access to a common logon with AM, but
remove AM from their normal logon. This will hopefully give them some
incentive to stop doing things which need AM. It also gives you a
method of logging their requirements for AM capability.
Others may have more information, but I believe there is some source
control software on the INTEREX CSL tape.
David N. Lukenbill
--------------------------------------------------------------------
David N. Lukenbill
Hughes Missile Systems Company, Louisville
[log in to unmask]
.......................................................................
Item Subject: WINMAIL.DAT
Could not convert Microsoft Mail Message Data item to text.
Will attempt to 'shar' item as file '01992aq' at end of msg.
# This is a shell archive. Remove anything before this line,
# then unpack it by saving it in a file and typing "sh file".
#
# Wrapped by OpenMail System <openmail@ciwsux> on Thu Jun 5 08:59:55 1997
#
# This archive contains:
# 01992aq
#
# Error checking via wc(1) will be performed.
LANG=""; export LANG
PATH=/bin:/usr/bin:$PATH; export PATH
rm -f /tmp/uud$$
(echo "begin 666 /tmp/uud$$\n#;VL*n#6%@x\n \nend" | uudecode) >/dev/null 2>&1
if [ X"`cat /tmp/uud$$ 2>&1`" = Xok ]
then
unpacker=uudecode
else
echo Compiling unpacker for non-ascii files
pwd=`pwd`; cd /tmp
cat >unpack$$.c <<'EOF'
#include <stdio.h>
#define C (*p++ - ' ' & 077)
main()
{
int n;
char buf[128], *p, a,b;
scanf("begin %o ", &n);
gets(buf);
if (freopen(buf, "w", stdout) == NULL) {
perror(buf);
exit(1);
}
while (gets(p=buf) && (n=C)) {
while (n>0) {
a = C;
if (n-- > 0) putchar(a << 2 | (b=C) >> 4);
if (n-- > 0) putchar(b << 4 | (a=C) >> 2);
if (n-- > 0) putchar(a << 6 | C);
}
}
exit(0);
}
EOF
cc -o unpack$$ unpack$$.c
rm unpack$$.c
cd $pwd
unpacker=/tmp/unpack$$
fi
rm -f /tmp/uud$$
echo x - 01992aq '[non-ascii]'
$unpacker <<'@eof'
begin 660 01992aq
M>)\^(ETY 0:0" $ ! $ 0>0!@ ( Y 0 #H $(@ < X
M& $E032Y-:6-R;W-O9G0@36%I;"Y.;W1E #$( 0V ! " @ " $$X
M@ $ (@ %)%.B!297-T<FEC=&EN9R!A8V-E<W,@=&\@82!G<F]U< #B"P$%X
M@ , #@ ,T'!@ % D - 0 ^0 ! ( $( $ $( $@ @ $QU:V5NX
M8FEL;"P@1&%V:60 $]014Y-04E,.D1A=FED($QU:V5N8FEL;" O2$U30TP X
M !-$ $@@ , #@ ,T'!@ % @ +@ J 0 0P$!"8 ! "$ UX
M039%,C P,#DX1$1$,#$Q.4,T,$-%1#A%,3 P,# P, #\!@$#D 8 = $ !( X
M + ", , )@ "P I # "X , -@ 0 YX
M %!?.FBP<;P!'@!" $ 1 3'5K96YB:6QL+"!$879I9 ! $@ X
ML#\-:;!QO $> ' 0 "( !213H@4F5S=')I8W1I;F<@86-C97-S('1OX
M(&$@9W)O=7 " 7$ 0 !8 !O'&P: P (&Y;W9@1T)Q SMCA X
M > !H, 0 !$ !,=6ME;F)I;&PL($1A=FED (!'0P! ( X
M $]014Y-04E,.D1A=FED($QU:V5N8FEL;" O2$U30TP '@ ># $ ) X
M3U!%3DU!24P '@ ?# $ 7 1&%V:60@3'5K96YB:6QL("](35-#X
M3 0 ',&#GKX2N<;P!0 (,&#GKX2N<;P!'@ ] $ % 4D4Z( X
, # TT_3< "E, X
X
end
@eof
set `wc -lwc <01992aq`
if test $1$2$3 != 029687
then
echo ERROR: wc results of 01992aq are $* should be 0 29 687
fi
chmod 660 01992aq
rm -f /tmp/unpack$$
exit 0
|
