Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-24 Thread Scott Ford
Too bad you can't use the LDAP to signon to TSO.. I understand what your saying Timothy. The big trick as we have found is design.. Plan seems to be a bad 4 letter word Scott ford www.identityforge.com On Jul 24, 2012, at 8:06 PM, Timothy Sipples timothy.sipp...@us.ibm.com wrote: Shmuel Metz

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-22 Thread Timothy Sipples
Shmuel Metz asks: There is support for mapping long user ids into short user ids. Does that support work if the access validation is in a third party LDAP server? Base z/OS includes LDAP client support, provided in the Tivoli Directory Server for z/OS. I already answered yes, so I'll vote yes

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-22 Thread Scott Ford
Sorry we are competitors I won't say more Scott ford www.identityforge.com On Jul 22, 2012, at 8:38 PM, Timothy Sipples timothy.sipp...@us.ibm.com wrote: Shmuel Metz asks: There is support for mapping long user ids into short user ids. Does that support work if the access validation

Re: Passwords and user-ids was Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-21 Thread Paul Gilmartin
On Fri, 20 Jul 2012 23:22:38 -0300, Clark Morris wrote: If you believe that user-ids should be larger than 7 characters or even 8, then what are the implications for SMF records and various control blocks in z/OS? Many modern products use XML to avoid such hard limits. -- gil

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-20 Thread Timothy Sipples
Shmuel Metz asks: Can you log on to TSO foreground with an 8-character userid using the LDAP client, or do you need TDS for that? I'm not sure I understand the question, but I'll attempt an answer. 1. Unaided, TSO/E supports up to 7 character user IDs. 2. Note that you are not required to use

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-20 Thread Tony Harminc
On 20 July 2012 05:06, Timothy Sipples timothy.sipp...@us.ibm.com wrote: 3. TSO/E is a part of z/OS, but most people who use z/OS these days probably aren't using TSO/E. Well, it depends what you measure... When I use my bank's ATM, I am using z/OS, and the bank has several million customers,

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-20 Thread Shmuel Metz (Seymour J.)
In ofbece3590.44f08adb-on48257a41.002f9ff5-48257a41.00320...@us.ibm.com, on 07/20/2012 at 05:06 PM, Timothy Sipples timothy.sipp...@us.ibm.com said: I'm not sure I understand the question, There is support for mapping long user ids into short user ids. Does that support work if the access

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-20 Thread Don Leahy
On Fri, Jul 20, 2012 at 12:08 PM, Tony Harminc t...@harminc.net wrote: On 20 July 2012 05:06, Timothy Sipples timothy.sipp...@us.ibm.com wrote: 3. TSO/E is a part of z/OS, but most people who use z/OS these days probably aren't using TSO/E. Are you saying that that is what has changed?

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-20 Thread Scott Ford
Sales pitch, sorry guys...I will bet there are thousands and thousands of users using either TSO or CMS ..of course CICS and IMS and DB2 ...we also sell software ...LDAP ...but I won't go there unless its offline. This isn't the place to try to hustle ppl Scott ford www.identityforge.com

Passwords and user-ids was Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-20 Thread Clark Morris
On 16 Jul 2012 09:00:40 -0700, in bit.listserv.ibm-main you wrote: The acceptability of length limitations depends upon their values. Passwords or userids that may be at most 8 characters in length are unacceptable today. Has IBM changed that limitation for standard TSO and CICS login. I also

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-19 Thread Timothy Sipples
The total value (market capitalization) of Yahoo has steadily declined over the past several years. Maybe they could try something different, like protecting their users' mailboxes and address books (while they deliver ads to them). Yahoo's fundamental business problem is that they've been losing

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-19 Thread Shmuel Metz (Seymour J.)
In 886132E644ECAE808EED6EEFA317@graham, on 07/17/2012 at 11:15 AM, Graham Hobbs gho...@cdpwise.net said: When someone uses the underscores between some words .. what does that mean? Underscore. ITYM when somebody uses underscore *around* a word. In that case it means the same as

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-19 Thread Shmuel Metz (Seymour J.)
In ofae475794.d0761284-on48257a3e.001cb9f7-48257a3e.001fa...@us.ibm.com, on 07/17/2012 at 01:45 PM, Timothy Sipples timothy.sipp...@us.ibm.com said: Most coffee shops, hotels, etc. still don't use encrypted wi-fi. Bletch! I'd better check what my local library uses, if anything. 3. The

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-19 Thread McKown, John
] On Behalf Of Shmuel Metz (Seymour J.) Sent: Thursday, July 19, 2012 8:15 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek In OFAE475794.D0761284-ON48257A3E.001CB9F7-48257A3E.001FA9B9@us. ibm.com, on 07/17/2012

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-18 Thread John Gilmore
The arguments that Timothy Sipples makes against Paul Gilmartin's begin extract Of course, turn on implies commiting the CPU (micro)cycles to peform the encryption /end extract are, in their way, persuasive; but there is another, non-economic argument that is even more persuasive to some IT

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-18 Thread Elardus Engelbrecht
Graham Hobbs wrote: When someone uses the underscores between some words .. what does that mean? EMPHASIS. It is one way to put reader's attention to that word(s) without using advanced formatting gizmos. As others have noted, it is a way of [manual] formatting only usable by your tired eyes,

SV: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-17 Thread Thomas Berg
juli 2012 19:18 Till: IBM-MAIN@LISTSERV.UA.EDU Ämne: Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek scott_j_f...@yahoo.com (Scott Ford) writes: Very true..but still I think Yahoo has a responsibility to their customers We were tangentially

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-17 Thread Paul Gilmartin
On Tue, 17 Jul 2012 13:45:51 +0800, Timothy Sipples wrote: 4. It's a big problem when practically everybody in the security community criticizes Yahoo! for their intransigence in fixing the problem. It's an even bigger problem when my own mother suffered from Yahoo's decade plus long failure to

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-17 Thread Paul Gilmartin
On Tue, 17 Jul 2012 13:13:03 +0800, Timothy Sipples wrote: You're referring to TSO/E only, which has a 7 character user ID limitation. Yes, if you're shopping for TSO/E, maybe that's a strike against TSO/E. Also (consequently?) if you're shopping for a Lockheed Martin F-22 Raptor military fighter

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-17 Thread McKown, John
-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Timothy Sipples Sent: Tuesday, July 17, 2012 12:13 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-17 Thread Paul Gilmartin
On Tue, 17 Jul 2012 07:36:49 -0500, McKown, John wrote: -Original Message- [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Timothy Sipples Sent: Tuesday, July 17, 2012 12:13 AM snip Fact: Every z/OS licensee receives Tivoli Directory Server for z/OS with LDAP. There's no such

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-17 Thread McKown, John
, 2012 10:15 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek When someone uses the underscores between some words .. what does that mean? Thanks Graham Hobbs - Original Message - From: McKown

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-17 Thread Steve Comstock
On 7/17/2012 9:21 AM, McKown, John wrote: For me (and I think that I'm the only one who does it), it is just for EMPHASIS, instead of capitalizing or doing a emBOLD/em. It is not any kind of real or defacto standard. Just an oddity on my part. Due mainly to my hatred of using HTML formatted

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-17 Thread Timothy Sipples
Paul Gilmartin writes: Of course, turn on implies commiting the CPU (micro)cycles to peform the encryption. Yes it does. Google and Microsoft (to pick two examples) made the resource commitment years ago, when computing power cost a lot more, and their customers are far more secure. Training

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread Timothy Sipples
Yahoo! Mail -- the Web version -- *still* does not use HTTPS for most communications AFAIK. For example, if you're using a free wi-fi hotspot at a coffee shop, and you access Yahoo! Mail via their Web interface, practically everything except your login credentials flows in the clear. A fairly

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread John Mattson
Back to basics: My pet peeve(s) (serious security concerns) are: 1) sites which do not allow use of the full set of special characters. My banks, Google and Facebook do, so it is not that hard. The more posibilities for each character, the more secure the password. 2) sites which limit

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread John Gilmore
The acceptability of length limitations depends upon their values. Passwords or userids that may be at most 8 characters in length are unacceptable today. A limitation to at most 2^15 - 1 = 32767 characters is, in my view at least, unobjectionable. Larger limitations like this one are often

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread Shmuel Metz (Seymour J.)
In of481ed85f.720f607e-on48257a3d.00242269-48257a3d.0026c...@us.ibm.com, on 07/16/2012 at 03:03 PM, Timothy Sipples timothy.sipp...@us.ibm.com said: Yahoo! Mail -- the Web version -- *still* does not use HTTPS for most communications AFAIK. For example, if you're using a free wi-fi hotspot

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread Anne Lynn Wheeler
, the more secure the password. 2) sites which limit length of userid and/or password. That's just plain dumb. re: http://www.garlic.com/~lynn/2012j.html#47 Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek http://www.garlic.com/~lynn/2012j.html#53 Yahoo

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread zMan
On Mon, Jul 16, 2012 at 12:00 PM, John Gilmore jwgli...@gmail.com wrote: The acceptability of length limitations depends upon their values. Passwords or userids that may be at most 8 characters in length are unacceptable today. Passwords, yes; userids, meh -- I don't consider a userid to

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread Finch, Steve (ES - Mainframe)
@LISTSERV.UA.EDU Subject: Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek On Mon, 16 Jul 2012 12:00:33 -0400, John Gilmore wrote: Passwords or userids that may be at most 8 characters in length are unacceptable today

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread John Gilmore
The 32 kib bound has two rationales: 1) It is enough/overkill for passwords used by people and 2) larger values are problematic, produce control-block overflows, in some contexts. The first of these two is the more important. The practice of Increasing the supported length of something from 8

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread Scott Ford
Finch -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Monday, July 16, 2012 1:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread zMan
On Mon, Jul 16, 2012 at 4:15 PM, John Gilmore jwgli...@gmail.com wrote: We have begun to see fallout. Fortunately, it's amateurish so far. This moring my wife received an email, a long litany of woe and injuries, allegedly from an old friend and college classmate. She wanted us to send

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread Anne Lynn Wheeler
that the much-vaunted browser spoofing isn't nearly as easy as folks make it sound... re: http://www.garlic.com/~lynn/2012j.html#47 Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek http://www.garlic.com/~lynn/2012j.html#53 Yahoo Password Breach: 7 Lessons Learned

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread Paul Gilmartin
On Mon, 16 Jul 2012 13:31:07 -0400, zMan wrote: On Mon, Jul 16, 2012 at 12:00 PM, John Gilmore wrote: Passwords or userids that may be at most 8 characters in length are unacceptable today. Passwords, yes; userids, meh -- I don't consider a userid to be a secure data point. It's not a

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread Timothy Sipples
Paul Gilmartin writes: It's not a matter of security; rather that many IT departments nowadays have a standard of 8-character userids. IBM is a tail that can no longer wag that dog; the CIO can cite refusal to comply with corporate standards as one more strike against z/OS in a purchase decision.

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-16 Thread Timothy Sipples
Shmuel Metz asks: Are you still using Wired Equivalent Privacy (WEP) or something more modern, e.g., Wi-Fi Protected Access (WPA)? Of course I use the latter, but a few points: 1. Wi-fi encryption only handles the hop between your wireless device and the wireless router/access point. Beyond that

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-15 Thread zMan
On Sun, Jul 15, 2012 at 12:18 AM, Ed Gould edgould1...@comcast.net wrote: http://www.informationweek.**com/news/security/attacks/** 240003692?cid=nl_IW_daily_**2012-07-13_htmlelq=**

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-15 Thread Scott Ford
Hey zMan, Very true..but still I think Yahoo has a responsibility to their customers Scott ford www.identityforge.com On Jul 15, 2012, at 10:43 AM, zMan zedgarhoo...@gmail.com wrote: On Sun, Jul 15, 2012 at 12:18 AM, Ed Gould edgould1...@comcast.net wrote:

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-15 Thread zMan
On Sun, Jul 15, 2012 at 12:12 PM, Scott Ford scott_j_f...@yahoo.com wrote: Hey zMan, Very true..but still I think Yahoo has a responsibility to their customers Absolutely. Though this gets into a related issue: what do free services owe their customers? I'm not satisfied with the current

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-15 Thread Anne Lynn Wheeler
scott_j_f...@yahoo.com (Scott Ford) writes: Very true..but still I think Yahoo has a responsibility to their customers We were tangentially involved in the cal. data breach notification act (the original notification act) having been brought in to help wordsmith the cal. electornic signature

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-15 Thread Scott Ford
ZMan, Very true. Scott ford www.identityforge.com On Jul 15, 2012, at 12:53 PM, zMan zedgarhoo...@gmail.com wrote: On Sun, Jul 15, 2012 at 12:12 PM, Scott Ford scott_j_f...@yahoo.com wrote: Hey zMan, Very true..but still I think Yahoo has a responsibility to their customers

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-15 Thread Ed Gould
I agree whether its YAHOO or whoever stole the passwords it was bad form. I am trying to remember if at one time (its not that way now) RACF didn't do the same (passwords in display form). My memory only goes back just so far and it doesn't reveal anything. Does anyone remember when RACF was

Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-14 Thread Ed Gould
http://www.informationweek.com/news/security/attacks/240003692? cid=nl_IW_daily_2012-07-13_htmlelq=ce8b95a547134f1eb898ba0413ba0b0c -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: Yahoo Password Breach: 7 Lessons Learned - Security - Attacks/breaches - Informationweek

2012-07-14 Thread Scott Ford
Ed, I skimmed the below article. I agree with what they say, we are in the security business. I think the punishment of the perps should be severe enough to deter hacking like that. Maybe I am too old school. They should be held accountable for their actions. Scott ford www.identityforge.com