I'm finding OpenVMS V9.2-1 password policy rather obnoxious as this is
strictly a hobbyist system and it is making me change passwords.

I'd like for it not to ask me to change passwords regularly and I'd
like to able to set the minimum length. How can I do that?

Thanks,
Alex
--
Tactical Nuclear Kittens

On 7/21/2023 4:40 PM, Single Stage to Orbit wrote:
> I'm finding OpenVMS V9.2-1 password policy rather obnoxious as this is
> strictly a hobbyist system and it is making me change passwords.
>
> I'd like for it not to ask me to change passwords regularly and I'd
> like to able to set the minimum length. How can I do that?

$ SET DEF SYS$SYSTEM
$ RUN AUTHORIZE
UAF> MOD username/PASSW=hemmeligt/PWDLIFE=0/NOPWDEXP
UAF> EXIT

Arne

On Fri, 2023-07-21 at 16:57 -0400, Arne Vajhøj wrote:
> > I'd like for it not to ask me to change passwords regularly and I'd
> > like to able to set the minimum length. How can I do that?
>
> $ SET DEF SYS$SYSTEM
> $ RUN AUTHORIZE
> UAF> MOD username/PASSW=hemmelig

Fkn' brilliant, that solved the issue most admirably.
I also figured out how to move the default directory to the correct
drive too.

Wunderbar. Now I can fling the old disk into the bitbucket.

Now I must get the compilers installed.

Cheers and thanks once again.
--
Tactical Nuclear Kittens

On 7/21/2023 4:57 PM, Arne Vajhøj wrote:
> On 7/21/2023 4:40 PM, Single Stage to Orbit wrote:
>> I'm finding OpenVMS V9.2-1 password policy rather obnoxious as this is
>> strictly a hobbyist system and it is making me change passwords.
>>
>> I'd like for it not to ask me to change passwords regularly and I'd
>> like to able to set the minimum length. How can I do that?
>
> $ SET DEF SYS$SYSTEM
> $ RUN AUTHORIZE
> UAF> MOD username/PASSW=hemmeligt/PWDLIFE=0/NOPWDEXP
> UAF> EXIT
>
> Arne
>
>

Arne must monitor c.o.v every 5 minutes, or so ...

Maybe 7 minutes :-)

--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486

On Fri, 2023-07-21 at 18:53 -0400, Dave Froble wrote:
>
> Arne must monitor c.o.v every 5 minutes, or so ...
>
> Maybe 7 minutes  :-)

Dear me. :-D It was a good thing though.

Now I have installed all the major compilers. Pascal, Fortran, C work
fine but for some mysterious reason, the C++ compiler refuses to
compile code moaning about permission denied trying to open C++
headers.

For exmaple:
Alex (KAKAPO) > cxx quick2.cpp
In file included from DKA0:[USERS.ALEX.CPROGS]QUICK2.CPP;1:1:
In file included from
/SYS$COMMON/VSICXX$LIB/INCLUDE/LIB_CXX/INCLUDE/iostream:42:
/SYS$COMMON/VSICXX$LIB/INCLUDE/LIB_CXX/INCLUDE/__config:1132:46: fatal
error: cannot open file '/SYS$COMMON/VSICXX$LIB/INCLUDE/SYS$S
TARLET_C/pthread.h': permission denied
(defined(__MINGW32__) && __has_include(<pthread.h>))
^
1 error generated.

This C++ compiler is VSI-X86VMS-CXX-A1000-230616-1.ZIP, taken right off
the VSI website.

I've checked and I can see the hesders in the directories from my tst
account.

But the pthread.h thing makes me suspicious as the code I'm compiling
just outputs "Hello, world" and uses nothing else!
--
Tactical Nuclear Kittens

On 7/21/2023 7:41 PM, Single Stage to Orbit wrote:
> On Fri, 2023-07-21 at 18:53 -0400, Dave Froble wrote:
>>
>> Arne must monitor c.o.v every 5 minutes, or so ...
>>
>> Maybe 7 minutes :-)
>
> Dear me. :-D It was a good thing though.
>
> Now I have installed all the major compilers. Pascal, Fortran, C work
> fine but for some mysterious reason, the C++ compiler refuses to
> compile code moaning about permission denied trying to open C++
> headers.
>
> For exmaple:
> Alex (KAKAPO) > cxx quick2.cpp
> In file included from DKA0:[USERS.ALEX.CPROGS]QUICK2.CPP;1:1:
> In file included from
> /SYS$COMMON/VSICXX$LIB/INCLUDE/LIB_CXX/INCLUDE/iostream:42:
> /SYS$COMMON/VSICXX$LIB/INCLUDE/LIB_CXX/INCLUDE/__config:1132:46: fatal
> error: cannot open file '/SYS$COMMON/VSICXX$LIB/INCLUDE/SYS$S
> TARLET_C/pthread.h': permission denied
> (defined(__MINGW32__) && __has_include(<pthread.h>))
> ^
> 1 error generated.
>
> This C++ compiler is VSI-X86VMS-CXX-A1000-230616-1.ZIP, taken right off
> the VSI website.
>
> I've checked and I can see the hesders in the directories from my tst
> account.
>
> But the pthread.h thing makes me suspicious as the code I'm compiling
> just outputs "Hello, world" and uses nothing else!
>

Do you have read access to the file(s)? A protection violation is usually
because of access not allowed.

Anything that gets used by everybody should have protection:

(RWED,RWED,RE,RE)

That should be Owner, System, Group, and World, if I remember correctly.

Look at HELP SET PROT

--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef@tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486

On 22/07/2023 00:41, Single Stage to Orbit wrote:
> On Fri, 2023-07-21 at 18:53 -0400, Dave Froble wrote:
>>
>> Arne must monitor c.o.v every 5 minutes, or so ...
>>
>> Maybe 7 minutes  :-)
>
> Dear me. :-D It was a good thing though.
>
> Now I have installed all the major compilers. Pascal, Fortran, C work
> fine but for some mysterious reason, the C++ compiler refuses to
> compile code moaning about permission denied trying to open C++
> headers.
>
> For exmaple:
> Alex (KAKAPO) > cxx quick2.cpp
> In file included from DKA0:[USERS.ALEX.CPROGS]QUICK2.CPP;1:1:
> In file included from
> /SYS$COMMON/VSICXX$LIB/INCLUDE/LIB_CXX/INCLUDE/iostream:42:
> /SYS$COMMON/VSICXX$LIB/INCLUDE/LIB_CXX/INCLUDE/__config:1132:46: fatal
> error: cannot open file '/SYS$COMMON/VSICXX$LIB/INCLUDE/SYS$S
> TARLET_C/pthread.h': permission denied
> (defined(__MINGW32__) && __has_include(<pthread.h>))
> ^
> 1 error generated.
>
> This C++ compiler is VSI-X86VMS-CXX-A1000-230616-1.ZIP, taken right off
> the VSI website.
>
> I've checked and I can see the hesders in the directories from my tst
> account.
>
> But the pthread.h thing makes me suspicious as the code I'm compiling
> just outputs "Hello, world" and uses nothing else!

I think the header protection issue was raised on the VSI forum, and
reported by jreagan at the end of last month. See:
https://forum.vmssoftware.com/viewtopic.php?f=12&t=8657

--
Chris

On 7/21/2023 9:15 PM, Chris Townley wrote:
> On 22/07/2023 00:41, Single Stage to Orbit wrote:
>> Now I have installed all the major compilers. Pascal, Fortran, C work
>> fine but for some mysterious reason, the C++ compiler refuses to
>> compile code moaning about permission denied trying to open C++
>> headers.
>>
>> For exmaple:
>> Alex (KAKAPO) > cxx quick2.cpp
>> In file included from DKA0:[USERS.ALEX.CPROGS]QUICK2.CPP;1:1:
>> In file included from
>> /SYS$COMMON/VSICXX$LIB/INCLUDE/LIB_CXX/INCLUDE/iostream:42:
>> /SYS$COMMON/VSICXX$LIB/INCLUDE/LIB_CXX/INCLUDE/__config:1132:46: fatal
>> error: cannot open file '/SYS$COMMON/VSICXX$LIB/INCLUDE/SYS$S
>> TARLET_C/pthread.h': permission denied
>>        (defined(__MINGW32__) && __has_include(<pthread.h>))
>>                                               ^
>> 1 error generated.
>>
>> This C++ compiler is VSI-X86VMS-CXX-A1000-230616-1.ZIP, taken right off
>> the VSI website.
>>
>> I've checked and I can see the hesders in the directories from my tst
>> account.
>>
>> But the pthread.h thing makes me suspicious as the code I'm compiling
>> just outputs "Hello, world" and uses nothing else!
>
> I think the header protection issue was raised on the VSI forum, and
> reported by jreagan at the end of last month. See:
> https://forum.vmssoftware.com/viewtopic.php?f=12&t=8657

Besides a list of some stuff ported to VMS x86-64 then:

https://www.vajhoej.dk/arne/vms/x64.html

also list a few known issues including this one.

Arne

On Sat, 2023-07-22 at 02:15 +0100, Chris Townley wrote:
> > But the pthread.h thing makes me suspicious as the code I'm
> > compiling
> > just outputs "Hello, world" and uses nothing else!
>
> I think the header protection issue was raised on the VSI forum, and
> reported by jreagan at the end of last month. See:
> https://forum.vmssoftware.com/viewtopic.php?f=12&t=8657

OK, on further examination, it looks as if the pthread.h file is
MISSINNG from the directory in question. I can see the the other
include files in the directory and view the file contents, so not a
permission issue.
--
Tactical Nuclear Kittens

On 7/22/2023 4:36 AM, Single Stage to Orbit wrote:
> On Sat, 2023-07-22 at 02:15 +0100, Chris Townley wrote:
>>> But the pthread.h thing makes me suspicious as the code I'm
>>> compiling
>>> just outputs "Hello, world" and uses nothing else!
>>
>> I think the header protection issue was raised on the VSI forum, and
>> reported by jreagan at the end of last month. See:
>> https://forum.vmssoftware.com/viewtopic.php?f=12&t=8657
>
> OK, on further examination, it looks as if the pthread.h file is
> MISSINNG from the directory in question. I can see the the other
> include files in the directory and view the file contents, so not a
> permission issue.

That is weird.

$ dir sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h

Directory SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]

PTHREAD.H;1

Total of 1 file.

What version of C++ did you install?

Arne

> > OK, on further examination, it looks as if the pthread.h file is
> > MISSINNG from the directory in question. I can see the the other
> > include files in the directory and view the file contents, so not a
> > permission issue.
>
> That is weird.
>
> $ dir sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h
>
> Directory SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]
>
> PTHREAD.H;1
>
> Total of 1 file.
>
> What version of C++ did you install?

Thought I mentioned the version earlier in the thread but it's this
one: VSI-X86VMS-CXX-A1000-230616-1.ZIP right off VSI Portal.
--
Tactical Nuclear Kittens

On 7/22/2023 10:00 AM, Single Stage to Orbit wrote:
>>> OK, on further examination, it looks as if the pthread.h file is
>>> MISSINNG from the directory in question. I can see the the other
>>> include files in the directory and view the file contents, so not a
>>> permission issue.
>>
>> That is weird.
>>
>> $ dir sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h
>>
>> Directory SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]
>>
>> PTHREAD.H;1
>>
>> Total of 1 file.
>>
>> What version of C++ did you install?
>
> Thought I mentioned the version earlier in the thread but it's this
> one: VSI-X86VMS-CXX-A1000-230616-1.ZIP right off VSI Portal.

Even more weird.

It is the same I have.

Maybe time for the "windows solution" aka remove and install
again??

Arne

On Sat, 2023-07-22 at 10:08 -0400, Arne Vajhøj wrote:
> > Thought I mentioned the version earlier in the thread but it's this
> > one: VSI-X86VMS-CXX-A1000-230616-1.ZIP right off VSI Portal.
>
> Even more weird.
>
> It is the same I have.
>
> Maybe time for the "windows solution" aka remove and install
> again??

The plot thickens even more.

Booted up OpenVMS and found this:

dir sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h

Directory SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]

PTHREAD.H;2 PTHREAD.H;1

Total of 2 files.

TWO?!

My gods, are they .. BREEDING?!

A quick purge later and then:

Alex (KAKAPO) > dir
sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h

Directory SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]

PTHREAD.H;2

Total of 1 file.
Alex (KAKAPO) > type/page
sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h
%TYPE-W-OPENIN, error opening
SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]PTHREAD.H;2 as input
-RMS-E-PRV, insufficient privilege or file protection violation

Alex (KAKAPO) > cxx quick2.cpp
In file included from DKA0:[USERS.ALEX.CPROGS]QUICK2.CPP;1:1:
In file included from
/SYS$COMMON/VSICXX$LIB/INCLUDE/LIB_CXX/INCLUDE/iostream:42:
/SYS$COMMON/VSICXX$LIB/INCLUDE/LIB_CXX/INCLUDE/__config:1132:46: fatal
error: cannot open file '/SYS$COMMON/VSICXX$LIB/INCLUDE/SYS$S
TARLET_C/pthread.h': permission denied
(defined(__MINGW32__) && __has_include(<pthread.h>))
^
1 error generated.

I guess we're exactly the same now. I wonder what security is set on
that header ...

Alex (KAKAPO) > show sec
_Object name: sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h
%SHOW-F-READERR, error reading
SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]PTHREAD.H;2
-SYSTEM-F-NOPRIV, insufficient privilege or object protection violation

Hmm, locked me out it has. Ok let's try as SYSTEM.

$ sh sec sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h

SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]PTHREAD.H;2 object of
class FILE
Owner: [SYSTEM]
Protection: (System: RWED, Owner: RWED, Group: RE, World)
Access Control List: <empty>

Wunderbar. The installer for the CXX isn't setting the appropriate
security on headers. Something for VSI to fix. :-D
--
Tactical Nuclear Kittens

On 7/22/2023 10:23 AM, Single Stage to Orbit wrote:
> On Sat, 2023-07-22 at 10:08 -0400, Arne Vajhøj wrote:
>>> Thought I mentioned the version earlier in the thread but it's this
>>> one: VSI-X86VMS-CXX-A1000-230616-1.ZIP right off VSI Portal.
>>
>> Even more weird.
>>
>> It is the same I have.
>>
>> Maybe time for the "windows solution" aka remove and install
>> again??
>
> The plot thickens even more.
>
> Booted up OpenVMS and found this:
>
> dir sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h
>
> Directory SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]
>
> PTHREAD.H;2 PTHREAD.H;1
>
> Total of 2 files.
>
> TWO?!
>
> My gods, are they .. BREEDING?!
>
> A quick purge later and then:
>
> Alex (KAKAPO) > dir
> sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h
>
> Directory SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]
>
> PTHREAD.H;2
>
> Total of 1 file.
> Alex (KAKAPO) > type/page
> sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h
> %TYPE-W-OPENIN, error opening
> SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]PTHREAD.H;2 as input
> -RMS-E-PRV, insufficient privilege or file protection violation
>
>
> Alex (KAKAPO) > cxx quick2.cpp
> In file included from DKA0:[USERS.ALEX.CPROGS]QUICK2.CPP;1:1:
> In file included from
> /SYS$COMMON/VSICXX$LIB/INCLUDE/LIB_CXX/INCLUDE/iostream:42:
> /SYS$COMMON/VSICXX$LIB/INCLUDE/LIB_CXX/INCLUDE/__config:1132:46: fatal
> error: cannot open file '/SYS$COMMON/VSICXX$LIB/INCLUDE/SYS$S
> TARLET_C/pthread.h': permission denied
> (defined(__MINGW32__) && __has_include(<pthread.h>))
> ^
> 1 error generated.
>
>
> I guess we're exactly the same now. I wonder what security is set on
> that header ...
>
> Alex (KAKAPO) > show sec
> _Object name: sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h
> %SHOW-F-READERR, error reading
> SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]PTHREAD.H;2
> -SYSTEM-F-NOPRIV, insufficient privilege or object protection violation
>
> Hmm, locked me out it has. Ok let's try as SYSTEM.
>
> $ sh sec sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h
>
> SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]PTHREAD.H;2 object of
> class FILE
> Owner: [SYSTEM]
> Protection: (System: RWED, Owner: RWED, Group: RE, World)
> Access Control List: <empty>
>
> Wunderbar. The installer for the CXX isn't setting the appropriate
> security on headers. Something for VSI to fix. :-D

If you look at the VSI forum thread then VSI has promised to fix it.

But until then:

$ set prot=(w:re) sys$common:[vsicxx$lib.include.sys$starlet_c]*.h

Arne

On 7/22/2023 10:56 AM, Arne Vajhøj wrote:
> On 7/22/2023 10:23 AM, Single Stage to Orbit wrote:
>> I guess we're exactly the same now. I wonder what security is set on
>> that header ...
>>
>> Alex (KAKAPO) > show sec
>> _Object name: sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h
>> %SHOW-F-READERR, error reading
>> SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]PTHREAD.H;2
>> -SYSTEM-F-NOPRIV, insufficient privilege or object protection violation
>>
>> Hmm, locked me out it has. Ok let's try as SYSTEM.
>>
>> $ sh sec sys$common:[vsicxx$lib.include.sys$starlet_c]pthread.h
>>
>> SYS$COMMON:[VSICXX$LIB.INCLUDE.SYS$STARLET_C]PTHREAD.H;2 object of
>> class FILE
>>       Owner: [SYSTEM]
>>       Protection: (System: RWED, Owner: RWED, Group: RE, World)
>>       Access Control List: <empty>
>>
>> Wunderbar. The installer for the CXX isn't setting the appropriate
>> security on headers. Something for VSI to fix. :-D
>
> If you look at the VSI forum thread then VSI has promised to fix it.
>
> But until then:
>
> $ set prot=(w:re) sys$common:[vsicxx$lib.include.sys$starlet_c]*.h

BTW, I suspect that my age shows since I prefer:

$ dir/prot
$ set prot=... or $ set file/prot=...

over:

$ show sec
$ set sec/prot=...

:-(

Arne

On Sat, 2023-07-22 at 10:56 -0400, Arne Vajhøj wrote:
> > Wunderbar. The installer for the CXX isn't setting the appropriate
> > security on headers. Something for VSI to fix. :-D
>
> If you look at the VSI forum thread then VSI has promised to fix it.
>
> But until then:
>
> $ set prot=(w:re) sys$common:[vsicxx$lib.include.sys$starlet_c]*.h

Yep, I missed that bit, all good now. C++ programs now compile happily.

Thank you.
--
Tactical Nuclear Kittens

On Sat, 2023-07-22 at 11:01 -0400, Arne Vajhøj wrote:
> BTW, I suspect that my age shows since I prefer:
>
> $ dir/prot
> $ set prot=... or $ set file/prot=...
>
> over:
>
> $ show sec
> $ set sec/prot=...

Well, sh sec or set sec seems more logical. Show and set.
--
Tactical Nuclear Kittens

On Saturday, July 22, 2023 at 11:14:00 AM UTC-4, Single Stage to Orbit wrote:
> On Sat, 2023-07-22 at 10:56 -0400, Arne Vajhøj wrote:
> > > Wunderbar. The installer for the CXX isn't setting the appropriate
> > > security on headers. Something for VSI to fix. :-D
> >
> > If you look at the VSI forum thread then VSI has promised to fix it.
> >
> > But until then:
> >
> > $ set prot=(w:re) sys$common:[vsicxx$lib.include.sys$starlet_c]*.h
> Yep, I missed that bit, all good now. C++ programs now compile happily.
>
> Thank you.
> --
> Tactical Nuclear Kittens
The next C++ kit "fixes" that protection issue by finally supporting reading headers
directly from the SYS$STARLET_C.TLB file.

And the next C++ will require V9.2-1 if people are still running V9.2 systems.