Gents,
Someone can comment on it, I received an email from an Open System college
arguing that mainframe is very weak...please help me to answer it:
oclHashcat v1.20 support added to crack RACF (IBM mainframe) hashes with 1
Billion (Giga) Hashes/second on a single stock clocked hd6990 graphics
On Tue, 18 Mar 2014 09:19:25 +0300, Jose Munoz wrote:
Someone can comment on it, I received an email from an Open System college
arguing that mainframe is very weak...please help me to answer it:
Well, first you need to access the encrypted password file, and/or bypass the
prevalent
In 2445830881854866.wa.paulgboulderaim@listserv.ua.edu, on
03/17/2014
at 11:03 AM, Paul Gilmartin paulgboul...@aim.com said:
No, and no. LINKMVS prefixes the programmer-supplied parameter
with a halfword length field and passes the result as a single
parameter to the called program.
In ec61ef1aa63c694b8a23a9e1350cca220109732...@dr000s060.sfr.net, on
03/17/2014
at 05:07 PM, Helio Jose Da Silva helio.si...@rural.com.br said:
Someone can tell me the relevant differences between the MVS and
z / OS systems?
MVS is anything in the OS/360 family from OS/VS2 Release 2 on; z/OS
In cf4cb1b7.c0106%gary.shimin...@doit.nh.gov, on 03/17/2014
at 06:13 PM, Shiminsky, Gary gary.shimin...@doit.nh.gov said:
If my memory serves me right, back in the 1970s there was OS/MFT,
OS/MVT, OS/VS1, and OS/VS2.
Not quite; MFT and MVT were options of OS/360 once things stabilized.
You
In
caarmm9rnkkjpcko0svtk2saizgpl9ssj-epej2b8xilazdh...@mail.gmail.com,
on 03/17/2014
at 03:08 PM, Tony Harminc t...@harminc.net said:
It took a long time for the names MVS (and
SVS, for that matter) to appear in official publications;
I see MVSxxx volsers in a 1975 manual; I see MVS in the
In 53270ed5.6080...@charter.net, on 03/17/2014
at 11:03 AM, Gerhard Postpischil gerha...@charter.net said:
Local terminals do not need VTAM, if you're willing to do the work to
mimic normal SNA packets with EXCP
For local non-SNA you don't even need to do that. In fact, I wan't
aware that
In 532707fc.9000...@bremultibank.com.pl, on 03/17/2014
at 03:34 PM, R.S. r.skoru...@bremultibank.com.pl said:
SNA terminal is network terminal
Not even close; a network terminal need not be SNA.
Each local terminal is defined in IODF as device,
Also wrong; a local non-SNA terminal is
W dniu 2014-03-18 07:19, Jose Munoz pisze:
Gents,
Someone can comment on it, I received an email from an Open System college
arguing that mainframe is very weak...please help me to answer it:
oclHashcat v1.20 support added to crack RACF (IBM mainframe) hashes with 1
Billion (Giga)
On Mon, 17 Mar 2014 18:49:15 -0400, Shmuel Metz (Seymour J.) wrote:
on 03/17/2014 at 11:03 AM, Paul Gilmartin said:
No, and no. LINKMVS prefixes the programmer-supplied parameter
with a halfword length field and passes the result as a single
parameter to the called program.
Still not right;
Jose Munoz wrote:
Someone can comment on it, I received an email from an Open System college
arguing that mainframe is very weak...please help me to answer it:
I'm not surprised. As a RACF person, I sometimes receive e-mails from spammers
and wannabe crackers trying to 'advise me' on a lot of
list, thanks for the tips of the difference between MVS and z / OS
Helio Jose da Silva -
-Mensagem original-
De: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] Em nome de
Helio Jose Da Silva
Enviada em: segunda-feira, 17 de março de 2014 14:07
Para:
In 20140318023541.6004883.11714.4...@yahoo.ca, on 03/17/2014
at 10:35 PM, Ted MacNEIL eamacn...@yahoo.ca said:
I think your dates are wrong.
Yes, but still more accurate than what you wrote.
VM was CP67
In the sense that OS/390 was OS/360. VM was a rewrite of CP67.
SVS was OS/VS1 and MVS
In
cakspfostlizlcvvj1v1hzcxow3n8slsm8gfdu+u4buwawhl...@mail.gmail.com,
on 03/18/2014
at 09:19 AM, Jose Munoz jmunoz6...@gmail.com said:
Someone can comment on it, I received an email from an Open System
college arguing that mainframe is very weak...please help me to
answer it:
The Devil is in
In 20140317203437.6004883.35398.4...@yahoo.ca, on 03/17/2014
at 04:34 PM, Ted MacNEIL eamacn...@yahoo.ca said:
VM was around in 1967. Iirc.
No. However, VM was a rewrite of code that was around earlier, and
1967 sounds right for CP-40 or CP-67.
--
Shmuel (Seymour J.) Metz, SysProg and
OS/MFT became OS/VS1
OS/MVT became SVS and then (later MVS)
snip
I think your dates are wrong.
VM was CP67 released in guess what year?
MVS was first released in 1974.
SVS was OS/VS1 and MVS was OS/VS2, IIRC.
I'm sure, if I'm wrong, somebody'll correct me.
-
-teD
-/snip
My dates are approximate, which is why I said 1975 (I think) instead of
1975. Your date of 1974 is equal to my 1975 (I think).
My date of 1974 for SVS is more accurate, because that is when I worked with
it, and I began doing so very shortly after it was first available.
VM was not called
I also wonder if they truly mean password hashes, as in the ancient RACF
password hash methods, or the more commonly used encryption method of
securing passwords or to be more technically correct, user ids.
--
Artificial Intelligence is no match for Natural Stupidity
- Unknown
On Tue, Mar 18,
Shmuel Metz wrote:
VM was CP67
In the sense that OS/390 was OS/360. VM was a rewrite of CP67.
VM wasn't a rewrite of CP67, any more than z/OS is a rewrite of OS/360.
It's a linear descendant; plenty of code remained.
As a VMer for 40+ years, the truth has been in here, but:
- CP-40
Have a look at :
http://www.demorton.com/Tech/$OSTL.pdf
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Phil Smith
Sent: Tuesday, March 18, 2014 9:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Difference between MVS and z / OS
shmuel+ibm-m...@patriot.net (Shmuel Metz , Seymour J.) writes:
In the sense that OS/390 was OS/360. VM was a rewrite of CP67.
re:
http://www.garlic.com/~lynn/2014d.html#54 Difference between MVS and z / OS
systems
http://www.garlic.com/~lynn/2014d.html#55 Difference between MVS and z / OS
W dniu 2014-03-18 12:56, Elardus Engelbrecht pisze:
I'm not surprised. As a RACF person, I sometimes receive e-mails from
spammers and wannabe crackers trying to 'advise me' on a lot of
things. ;-)
Well, in my case the statndard is nobody even heard about RACF. So I
receive no comments or
Sounds like a homework question.Compare and contrast
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems
On Tue, 18 Mar 2014 13:26:58 +, DASDBILL2 wrote:
VM's predecessor system was called CP67. Both of these systems supported
virtual storage and paging, but they had different names.
And they ran on processors with somewhat different architectures. The s/360
model 67 supported 32-bit
Radoslaw Skorupka wrote:
How did they tested it? Obtained a real copy of RACF DB and do your cracking?
I bet, yes. Do you want real copy of RACF db? I'll create it for you.
Tell me the usernames and passwords you want to have.
I'm too lazy to do that, I'll have rather mow my lawn. ;-D
If you
p...@voltage.com (Phil Smith) writes:
I'm assuming from having never seen a reference to such on IBM-MAIN
that no such community resource exists for z/OS-correct?
note that ibm-main mailing list originated on (univ) bitnet
mostly on vm370 systems
http://en.wikipedia.org/wiki/BITNET
and some
Greg –
Thanks for your reply, it’s a great overview.
My concern is not with master keys, only with the data keys (we have tested
documented master key recovery procedures). The last half of your answer is a
big help. We currently encrypt/decrypt data using one ‘data’ key for all prod
m42tom-ibmm...@yahoo.com (Tom Marchant) writes:
And they ran on processors with somewhat different architectures. The s/360
model 67 supported 32-bit addressing, while s/370 was limited to 24-bit
addressing
until XA in 1982 or 1983 began to support 31-bit addressing, not 32-bit like
the
On Tue, 2014-03-18 at 09:56 -0500, Tom Marchant wrote:
while s/370 was limited to 24-bit addressing
until XA in 1982 or 1983 began to support 31-bit addressing, not 32-bit like
the
model 67.
I vaguely remember the dual-address-space-facility that began life just
before XA came around.
On Tue, 18 Mar 2014 09:56:17 -0500, Tom Marchant wrote:
On Tue, 18 Mar 2014 13:26:58 +, DASDBILL2 wrote:
... The s/360
model 67 supported 32-bit addressing, while s/370 was limited to 24-bit
addressing
until XA in 1982 or 1983 began to support 31-bit addressing, not 32-bit like
the
On 18 March 2014 12:00, Paul Gilmartin paulgboul...@aim.com wrote:
How did the 67 deal with legacy code's use of the sign bit to terminate
parameter lists?
I doubt that much legacy code ran on such a machine in 32-bit mode.
There would surely be other reasons to run such code only in 24-bit
Hi Ed,
We use the '++' parameter in LOADxx so it will use the IODF at IPL time
whose token matches the current switched to IOCDS.Dynamic changes are
really no different then doing an actual POR in that regard.DR is not
an issue.
Thanks.
Dick
On Sat, Mar 15, 2014 at 12:29 PM, Ed
d...@lists.duda.com (David Andrews) writes:
I vaguely remember the dual-address-space-facility that began life just
before XA came around. There was some exploitation of it in - I think -
MVS/SE2 (or was it SP1?).
in the wake of the failure of FS
paulgboul...@aim.com (Paul Gilmartin) writes:
How did the 67 deal with legacy code's use of the sign bit to terminate
parameter lists? Did it also have a 31-bit mode? But I suppose most
such code was written for 24-bit addressing.
as mentioned here ... science center had expected to get the
On Tue, 18 Mar 2014 11:00:14 -0500, Paul Gilmartin wrote:
On Tue, 18 Mar 2014 09:56:17 -0500, Tom Marchant wrote:
... The s/360
model 67 supported 32-bit addressing, while s/370 was limited to 24-bit
addressing
until XA in 1982 or 1983 began to support 31-bit addressing, not 32-bit like
the
As long as it's covered, we got a plan.
In a message dated 3/18/2014 1:25:19 P.M. Central Daylight Time,
dickbond...@gmail.com writes:
whose token matches the current switched to IOCDS.Dynamic changes
are
really no different then doing an actual POR in that regard
Hi,
MVS is Big Mac, z/OS is Number 3 (Big Mac+Fries+Coke)
Atenciosamente / Regards / Saludos
Ituriel do Nascimento Neto
BANCO BRADESCO S.A.
4250 / DPCD Engenharia de Software
Sistemas Operacionais Mainframes
Tel: +55 11 3684-2177 R: 42177 3-1402
Fax: +55 11 3684-4427
Agora é BRA. BRA de
Actually I think MVS would be more akin to one of the 2 all beef patties.
:-) Would JES or DFP be the second patty?
Rex
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of ITURIEL DO NASCIMENTO NETO
Sent: Tuesday, March 18, 2014
In
b870629719727b4ba82a6c06a31c29124c5fcad...@hqmailsvr01.voltage.com,
on 03/18/2014
at 06:58 AM, Phil Smith p...@voltage.com said:
I'm assuming from having never seen a reference to such on IBM-MAIN
that no such community resource exists for z/OS-correct?
I'm not aware of one. I'd dearly
In
10e09aae7c8c0e4e9f40585c270c2795d863f...@e14mbx20n.enterprise.emory.net,
on 03/18/2014
at 02:21 PM, Skellen, Frank frank.skel...@emoryhealthcare.org
said:
Have a look at :
http://www.demorton.com/Tech/$OSTL.pdf
BTDT,GTTS. Incomplete and has significant errors.
--
Shmuel (Seymour
Jeez. Misread my own notes. VM/370 was announced August 2, 1972, per
http://www.sinenomine.net/publications/history/vm370-announcement
From: Phil Smith
Sent: Tuesday, March 18, 2014 9:59 AM
To: ibm-m...@bama.ua.edu
Subject: Re: Difference between MVS and z / OS systems
Shmuel Metz wrote:
VM was
_IBM - Archives - Documents - United States_
(http://www-03.ibm.com/ibm/history/documents/index.html)
I use this on occasion to cross check.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
Love the 'Quintessential Quotes'
Watson Sr. has one liners, everyone else is paragraphs.
CIT | Ken Porowski | VP Mainframe Engineering | Information Technology | +1 973
740 5459 (tel) | ken.porow...@cit.com
This email message and any accompanying materials may contain proprietary,
What was it he got in trouble for? Wanted to tattoo serial numbers on the
populace, guess that was
pre RFID's.
In a message dated 3/18/2014 3:19:15 P.M. Central Daylight Time,
ken.porow...@cit.com writes:
Watson Sr. has one liners, everyone else is paragraphs.
One of my co-workers is trying to improve the performance of an Enterprise 4.1
program that decomposes an input XML file into record fields for processing by
later programs. The volume of the XML input has increased quite a bit and the
performance may soon impact SLA's.
This program is
On 19/03/2014 0:51, Lou Losee wrote:
I also wonder if they truly mean password hashes, as in the ancient RACF
password hash methods, or the more commonly used encryption method of
securing passwords or to be more technically correct, user ids.
I'm sure it is using the encryption method. The
and...@blackhillsoftware.com (Andrew Rowley) writes:
I'm sure it is using the encryption method. The speed of password
cracking on GPUs is fast enough that most hashes are vulnerable using
traditional length passwords. RACF might be worse than some because
the algorithm might not be
On 3/17/2014 10:07 AM, Helio Jose Da Silva wrote:
Someone can tell me the relevant differences between the MVS and z / OS systems?
40 years.
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/
On 19/03/2014 9:30, Anne Lynn Wheeler wrote:
also
http://en.wikipedia.org/wiki/Password_cracking
things were speeded up some when repositories of tens of thousand
of the most common passwords were published.
some countermeasure
http://en.wikipedia.org/wiki/Salt_%28cryptography%29
The GPU
On Mar 18, 2014, at 5:57 PM, Andrew Rowley wrote:
On 19/03/2014 9:30, Anne Lynn Wheeler wrote:
also
http://en.wikipedia.org/wiki/Password_cracking
things were speeded up some when repositories of tens of thousand
of the most common passwords were published.
some countermeasure
On 19/03/2014 10:21, Ed Gould wrote:
I thought IBM would have spoken up before this. From what little I have
heard is that even with the raw data (ie the RACF DB) the password is
unable to be broken.
You can't calculate the password from the stored value - as far as I
know that is still the
I seem to recall Tom Ross saying that XMLSS is, in fact, generally slower than
COMPAT. I believe the only advantage to XMLSS is that it can be offloaded to a
specialty engine. So it will be slower but cost less (??). Or slower and cost
more if you don't have a specialty engine!
Crazy, no?
The biggest problem with this is if I recall correctly, the user id is
encrypted with the password with a variant of DES that has a slight twist
from the published DES algorithm. That is why there are two types of DES
encrypt calls in the RACROUTE REQUEST=EXTRACT macro; ENCRYPT=(data
addr,DES)
In m3iorbsfz2.fsf@lhwserver.localdomain, on 03/18/2014
at 11:07 AM, Anne Lynn Wheeler l...@garlic.com said:
360/67 multiprocessor support also allowed all processors to address
all channels ... the 360/65 multiprocessor support just shared memory
but had dedicated channels for each processor
In 5298812145489891.wa.paulgboulderaim@listserv.ua.edu, on
03/18/2014
at 11:00 AM, Paul Gilmartin paulgboul...@aim.com said:
How did the 67 deal with legacy code's use of the sign bit to
terminate parameter lists?
24-bit mode.
Did it also have a 31-bit mode?
No.
--
Shmuel
In 1395156127.1979.21.camel@localhost, on 03/18/2014
at 11:22 AM, David Andrews d...@lists.duda.com said:
I vaguely remember the dual-address-space-facility that began life
just before XA came around. There was some exploitation of it in - I
think - MVS/SE2 (or was it SP1?).
MVS/SP 1.2,
l...@garlic.com (Anne Lynn Wheeler) writes:
for a time I used to report to the same executive as the guy responsible
for APPN ... when it came time to announce, the communication group
non-concurred and objected to the announcement ... after several weeks,
the APPN announcement letter was
57 matches
Mail list logo
