Johnny Billquist <bqt at softjar.se> writes:
>On 2016-06-20 19:30, Brian Schenkenberger, VAXman- wrote:
>> Johnny Billquist <bqt at softjar.se> writes:
>>
>>> On 2016-06-20 18:19, Brian Schenkenberger, VAXman- wrote:
>>>> ___ _ _ _ __ __ _ _ _ _ ___ _____
>>>> / __| /_\ | \| | \ \ / / /_\ | | | \| | | __| |_ _|
>>>> \__ \ / _ \ | .` | \ V / / _ \ | |__ | .` | | _| | |
>>>> |___/ /_/_\_\_|_|\_| |_| /_/ \_\ |____| |_|\_| |___|_ |_|
>>>>
>>>> You've allowed this node on HECnet, so I assume somebody on this list knows
>>>> who runs it.
>>>
>>> Who runs it can always easily be found by http://mim.update.uu.se/nodedb
>>>
>>>> Please have it secured! It has been used in the past several
>>>> days to try and break into my system(s). It is highly irresponsible to put
>>>> access credentials into its SYS$ANNOUNCE allowing ANYBODY access to DCL and
>>>> other utilities that can affect systems on the internet. A reasonable way
>>>> to allow access would be to have a guest account (restricted/captive) that
>>>> can be used to create other login accounts. Validate such accounts with a
>>>> valid email address and other schemes that will insure that whomever is on
>>>> this system can be vetted in some fashion.
>>>>
>>>> THANK YOU!
>>>
>>> I'm curious about what kind of intrusions we're talking about, and over
>>> which network.
>>>
>>> In general, I want to keep HECnet more open than what you are suggesting
>>> above, but this also requires that people act responsibly. If there is
>>> abuse, I'd like to know.
>>
>> Well, since I have not yet put any of my systems on HECnet, it should have
>> been obvious that it's via the internet.
>
>Ah. Sorry for being dense. Thanks.
>
>So what kind of intrusion attempts are we talking about? Essentially
>your issue is that someone have a machine on the internet. Getting
>access on the machine is easy, and something/someone on that machine is
>trying to do something to your machine?
Well, for one, trying brute force attacks agains services. Here are some of
the FTP attempts from 108.31.82.9.
admin
support
guest
vizxv
123
1234
12345
123456
cisco
admin
service
1234
root
support
vizxv
123
12345
123456
xc3511
7ujMko0admin
root
root
support
123
12345
123456
xc3511
smcadmin
1234
xc3511
meinsm
vizxv
admin
admin
service
service
root
root
xc3511
12345
meinsm
dreambox
user
changeme
12345
pass
vizxv
user
changeme
root
I'm guessing that, due to the repeated nature of the usernames attempted, the
system has been logged into by a great many different twits.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> writes:
>
>> El 20 juny 2016, a les 20:14, Brian Schenkenberger, VAXman- =
><system at TMESIS.COM> va escriure:
>>=20
>> 108.31.82.9.
>
>Uh, I=E2=80=99d bet the simulated 3900 is not the real origin of the =
>attack you are getting. It is probably behind a home DSL/cable router, =
>whith port 23 redirected to the 3900=E2=80=99, which has probably a =
>private IP address masqueraded using NAT=E2=80=A6 So probably the node =
>owner has been hacked and zombified, regadrless of he having a pet 3900 =
>open to the net.
That may very well be true too. I have found many attack vectors over the years that
have originated from home routers. Several home routers have known/identified/easily
exploitable weaknesses. Regardless, I will check to see if this IP address continues
to aggrieve me now that it's been reported that FTP is no longer possible from the VMS
instance.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
Hello,
Does anyone have that thing? The ALPHA one is in vaxhaven (where there is also a HALF of a TK50 kit), but I?ve not been able to find the VAX one.
Thanks in advance.
Johnny Billquist <bqt at softjar.se> writes:
>On 2016-06-20 18:19, Brian Schenkenberger, VAXman- wrote:
>> ___ _ _ _ __ __ _ _ _ _ ___ _____
>> / __| /_\ | \| | \ \ / / /_\ | | | \| | | __| |_ _|
>> \__ \ / _ \ | .` | \ V / / _ \ | |__ | .` | | _| | |
>> |___/ /_/_\_\_|_|\_| |_| /_/ \_\ |____| |_|\_| |___|_ |_|
>>
>> You've allowed this node on HECnet, so I assume somebody on this list knows
>> who runs it.
>
>Who runs it can always easily be found by http://mim.update.uu.se/nodedb
>
>> Please have it secured! It has been used in the past several
>> days to try and break into my system(s). It is highly irresponsible to put
>> access credentials into its SYS$ANNOUNCE allowing ANYBODY access to DCL and
>> other utilities that can affect systems on the internet. A reasonable way
>> to allow access would be to have a guest account (restricted/captive) that
>> can be used to create other login accounts. Validate such accounts with a
>> valid email address and other schemes that will insure that whomever is on
>> this system can be vetted in some fashion.
>>
>> THANK YOU!
>
>I'm curious about what kind of intrusions we're talking about, and over
>which network.
>
>In general, I want to keep HECnet more open than what you are suggesting
>above, but this also requires that people act responsibly. If there is
>abuse, I'd like to know.
Well, since I have not yet put any of my systems on HECnet, it should have
been obvious that it's via the internet.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
___ _ _ _ __ __ _ _ _ _ ___ _____
/ __| /_\ | \| | \ \ / / /_\ | | | \| | | __| |_ _|
\__ \ / _ \ | .` | \ V / / _ \ | |__ | .` | | _| | |
|___/ /_/_\_\_|_|\_| |_| /_/ \_\ |____| |_|\_| |___|_ |_|
You've allowed this node on HECnet, so I assume somebody on this list knows
who runs it. Please have it secured! It has been used in the past several
days to try and break into my system(s). It is highly irresponsible to put
access credentials into its SYS$ANNOUNCE allowing ANYBODY access to DCL and
other utilities that can affect systems on the internet. A reasonable way
to allow access would be to have a guest account (restricted/captive) that
can be used to create other login accounts. Validate such accounts with a
valid email address and other schemes that will insure that whomever is on
this system can be vetted in some fashion.
THANK YOU!
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
Hello,
I'm looking for Vaxima, if someone has preserved a copy of it, it is
best described as such (if you don't know Vaxima):
MACSYMA (Project MAC's SYmbolic MAnipulation System) is a large
computer algebra system for symbolic and numerical computations.
Originally MACSYMA was developed by the MATH lab group at M.I.T. The
descendants of MACSYMA (circa 1982) fall into two camps, viz., the
commercialized Symbolics MACSYMA and its successor from Macsyma, Inc.,
and the versions released to National Energy Software Center at
Argonne, Illinois, which are based on the "public" MIT source code for
the DEC PDP-10 MACLisp system. The latter ones do not have the
Symbolics enhancements, but they have been modified from time to time
by several individuals or groups. One of these modifications is known
as VAXIMA. It is an implementation around 1980 on DEC-Vaxes by R.
Fateman at the University of California at Berkeley. It uses VAX/UNIX
Franz Lisp and runs on some Franz-Lisp hosts.
Thanks,
Jerome
Hi all,
My name is Lex van Roon, and for quite some time I've been lurking on
this list as a DEC/VMS enthusiast and today I got my link to HECnet
working with the help of Johnny.
Somewhere during the 90s, a high-school classmate of mine gave me a couple of
copies of Hacktic(*). In there I read about these operating systems with
weird names like VMS and UNIX, and since I only knew MS based OS's back
then, I was intrigued. I soon got my first Linux box running under x86,
and not long thereafter I got my first whitelabel Alpha mainboard, on
which I happily ran BSD and Linux. After dropping out of school, I went
to work as a sysadmin in the UNIX world during the end of the dotcom boom,
and nowadays I'm a DevOps engineer working for a large dutch .com.
As a hobby, I've been running various Alpha's (and other RISC iron) over
the years:
- Whitelabel AXPCI133
- AS1000 (lots of them)
- PWS 466au
- DS10/DS20/DS25
- ES47
and since a couple of years, I finally wiped UNIX off my Alpha's and
installed VMS, and have used them for various things. Mostly replicating
services I'd normally run under UNIX (dns, ntp, http), but also for
software development in C and Python(**). In this time, I've discovered
that it's very helpful to know people who know VMS very well (thnx
Steven Hoffman), and I am confident enough about my VMS skills
that I decided to join, since being in a DECnet with my own systems is
not such an interesting learning experience as working with 'the real
thing' :)
For now I'm online with the following two Alpha's:
REI / 1.540 / AlphaServer DS10 / 466MHz / 1GB ram / 2 x 18GB u2w 10k
PAI / 1.541 / AlphaServer DS25E / 1GHz / 1GB ram / 6 x 73GB u320 15k
In the future, I plan/hope to get my VAX 4000/200 connected, but that
system still needs some TLC before it will operate. Most likely I will
also spin up some emulated instances of various other DEC operating
systems in the future, for learning/discovery purposes.
The systems are connected to a 100mbit FttH uplink, located in Amersfoort,
The Netherlands and are available 24/7. I have not yet configured any guest
accounts, but I intend to do this.
Kind Regards,
Lex van Roon
*) https://en.wikipedia.org/wiki/Hack-Tic
**) https://github.com/r3boot/pki
--
LRO-RIPE | 570DE0BE | 9BF5 922E AF87 8584 E9CA C3AD C508 39A9 570D E0BE
Not sure if anyone really cares, but I figure it don't hurt to tell
anyway...
I have for many years used a very old version of MicroEMACS for RSX. I
eventually started searching around for alternatives, but realized
during that search that most Emacs clones are horribly huge (including
MicroEMACS), not portable at all (even if they claim to be), and
generally also expects to just allocate gobs of memory to keep all data
in ram.
Now, RSX, being a PDP-11 OS, have a 16-bit address space limitation. So
just allocating memory is never going to be a solution. There is a C
compiler, which is pretty much ANSI C. But it is not Unix, and gives you
the C standard IO library, but not low level Unix calls.
On the plus side, most of the library can sit in supervisor space, and
not consume any memory in your process space.
Clones I've looked at:
MicroEMACS - Huge and difficult to port. Use lots of memory.
JOVE - Small (runs on 2.11BSD), but horribly difficult to port.
mg - Huge and difficult. Use lots of memory.
AMIS - Huge, and written in Pascal. Not necessarily bad, but adapting
the code to a new system requires mucking around some, made worse by the
small differences in different Pascal compilers, and the lack of any
preprocessor, as well as the bonehead type system in Pascal. Also use
lots of memory, but it has been made to run on small machines (including
PDP-11 with RSTS/E) in the past, so it is a solveable problem.
Atto - Hard to port.
JED - Huge.
I looked at dozens more, which were not even worth looking deeper into,
or to list here.
The long and short of it was that, even though there are numerous
implementations out there, they all suck, from my point of view.
With all that in mind, I decided to write my own Emacs clone instead
(yes, I got horribly upset with the lousy quality of most code I looked
at, if someone wants to hear some rants, contact me privately).
I started about a month ago, and at this point, it's working, and quite
useful. And I guess if other people are in a similar situation, they
might be interested in looking into this, and possibly make use of it.
Quick run through:
. ANSI C sources.
. Mostly uses the C standard IO library. Exception is terminal I/O,
which requires some small pieces reimplemented if you want to port it.
So, if you have an ANSI C compiler, porting should be very low effort.
. Only works on ANSI terminals today. It would be doable to extend with
other terminal support, but I don't have any need, and since I do not
have, nor want to depend on curses, it will require coding to either
have a module to uses curses, if that is wanted, or handling of specific
terminals.
. The compiled code, using PDP-11 C, ends (at the moment) up at around
36 Kbytes of binary. The C library and RMS sits mostly in supervisor
mode, and is not accounted for in this.
. Data usage is about 8K for various storage and strings.
. Code dependecies are very much in a tree, so overlaying is easy, if
wanted/needed, and that capability exists on the host.
. Since I compile with split I/D space, this means than about 56K of
dataspace can be used for buffering of various sorts.
. File buffers are kept in a temporary file, and read/written to memory
as needed (pretty much a demand-paging virtual memory implementation in
the application).
. The virtual, paged memory is about 4G, which is an absolute limit on
memory usage. Practical file limit is (I would guesstimate) around 1G.
. Most basic EMACS editing functions are implemented, including split
windows, multiple buffers, kill buffer, moving around in various ways,
and some semi-stupid automatic indentation handling for C code. Also
incremental searching in a proper fashion.
. Speed, tested on a real PDP-11/93 is pretty acceptable. Testing on a
file about 1000 lines takes a couple of second to open, and a couple of
seconds if you try to search from the start to the end. Most other
things move faster.
. The program is not suitable for editing binary data. The C standard
I/O library don't really lend itself to binary I/O, and this code have
to live within those constraints.
There are still lots of functionality that I'm working on adding, such
as repeats (almost done) and macros (only started thinking about it).
If people have functions they consider extra important, let me know, and
I'll see if I can add them. If people want to contribute code, I'll be
happy to incorporate changes as well, as long as they make sense.
The sources, as well as a compiled RSX-11M-PLUS binary for PDP-11 C
V1.2, can be found at HECnet: MIM::DU:[NEMA], or
ftp:://nema at mim.update.uu.se/.
This editor is now installed as ...EMA on MIM::, so if you type "EMA
filename", you can see how it works there.
It is now my tool for doing further development. I have ditched
MicroEMACS. So I'm constantly testing the thing, as I am developing
it... :-)
Maybe someone will find it useful...
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Hi,
I wonder if someone has been succesful repairing the corrupted tpc images of several PDP-11 layered products that are (not)available in some sites (bitsavers and trailing-edge come to memory). IIRC there was a kind of effort to fix whatever could be fixed (the BRU format ones, specifically) reordering the mangled tape blocks in the image.
More specifically, I?m looking for an usable COBOL-81 compiler. The one which is not corrupted (cobol_v4_4) is COBOL/C11, not COBOL 81, and even for hobbyist stuff, handling COBOL-74 is a PITA?
Best regards to all.
Jordi Guillaumes
Hello,
I've got an RSX-11M+ VM up (real hardware whenever I get my boards
shipped...) and I've got a question:
Is the FMS-11 tape on trailing-edge ftp corrupted? Can it be used to
pe4rform an install?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
