Well, the original meaning was sloppy, inept work. The Tech Model Railroad Club at MIT introduced a new usage, and the media conflated that with "cracker". Some hackers are also crackers, but by no means all.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Mike Hochee <mike.hoc...@aspg.com> Sent: Sunday, October 11, 2020 7:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IBM splitting into two companies Charles, you must've found my creds! Please dispose of them in a secure manner. :-) You make a good point. And to muddy things further, the AWS user community seems to use the term 'hack' when referring to techniques to accomplish things that are completely acceptable and above-board. Mike -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Charles Mills Sent: Sunday, October 11, 2020 6:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IBM splitting into two companies Caution! This message was sent from outside your organization. I would think one needs to distinguish between AWS infrastructure flaws -- what IBM would call violations of the statement of integrity -- versus dumb user errors. The pop press is going to call it "an AWS hack" even if it was because someone left their userid and password behind on a Post-It note on a table in Denny's. Of course the two cases can blur somewhat if there are infrastructure characteristics that make it particularly easy for a user to screw it up. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mike Hochee Sent: Sunday, October 11, 2020 3:34 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IBM splitting into two companies I do not have an accurate big picture nor a decent set of data to work with, but here are a few google hits that do not inspire confidence, just anecdotal stuff of course.... https://secure-web.cisco.com/1j6Pmcn-zpu8-VCRrm93BntNiLdC9vN3f0cfokG9gGodxLq2d072S7OG4w9A5VyN0m3JQRMUi4xF6m24QGATISW0hCY2Dw74TTaFif3t4kZpeXwbz5VWIlwBOU1SQB2nf93EBq4jR7bCqt7_cfa3XoMeWvgxcns-FsdTv4yAhm91dgcJlDOTnCUNwDMQGPKcadw_d_HrO4FdtJrTyF1JMUri1jndb2-V9XCjvhulk2wnhqfIlshQw_MlX4tUc15z71Dt8CVNuBxiIOTBJ8zZvJ00rc6dDPuXTG7PvNDIX2ijKKdxEj1cQ01fhmXRW1Bq0RInveLYKzu9w2ZJAbd_PuwmlEi7kLlRas7oXPnN4IHYkCTxUf_3jIeMqAG3FJOC3dF3-aOU46Jh810VAW9WC3vxJdv3pvKblaccSf4b27KaWtXFK_iSDkkj8K8VENIph/https%3A%2F%2Fwww.cbronline.com%2Fnews%2Faws-servers-hacked-rootkit-in-the-cloud https://secure-web.cisco.com/1CgwsJgIqqCZXbxItYxP3s2Epo6V3vEfvcj0_pvICPBFnqbmYOmQq2f-rs30lMWgyxJPk2jpGJRJu4yonlAQ9cqPBX4hyVlsFEifw0yFXkIzav0_6Mzu2idX7h_c6zKrFNKNNmxGI7H-A4j8G25PdC3WIGLchm-cFeBoiu3KnBAlMY3-nc7CByrHo2Lb7qtAmUNJFqEOGCih5GVaSjr4W4SB8wrmILQ5O8wAMvzbgc7sQbdeePy0gshp1RQgEQsJXkuaABYRFUh04E4091iHsK3cXSxIl9DpH0mFp0Y6E_1UL7xUaumQJMY8u_TbUpbow8cBKjd-4UZFgBg1DbH3mpvac9hXNDbXIO1HZTVJpWu5bdlKK4hGbeaO7L0IBIjtQLOnLgRm-vlF6jlzyT7fKwvVmpKpNaAUO5KPLdsaVH0l3GaxyWVlxB8VyiNahYBQb/https%3A%2F%2Ftamebay.com%2F2020%2F05%2Famazon-warn-of-hacked-amazon-accounts-issue-acco unt-recovery-advice.html https://secure-web.cisco.com/18R72FOi1BZLnZXuX6yxlpEJ52VkBsovO7AWkEO-aQujUd3IbIgqku4E9QKj27rKmu7mJYsnu9iy505NANzmwhZ6HmKFKI7GWc5sLdRMjvH2BehjZE6tX_TAURdlLeK_7XRZfN9DjAcG_xBzarmbEY-EuzrpHfUWAJTVgj8csJDXzo4qv4ecWJgTz_GkySaeWfZxCKX_6wKWD8V9lFRTnsRb3p0CnkszZHXegO9Pn_UkCYybBOLxX0sUt6dZkqdQJ_xPa_w9WXIPk9C47AoKPBknbu_aGSr4imDsmcMKtCJ0qM6cOl2h-VndyZoV40yaDffDeUpZ0Pl7-8F7f1gepHPv-w8jklXvaFsXePXQb_6QkYFC6TfJGAxVd8Mb_OIDA-RzvD0DBEm43NGLAh574xbJuw9Z7zf0ui0PiHKVexv4tzhLVRWSyWzHsVOzI6e8Z/https%3A%2F%2Fwww.thesun.co.uk%2Fmoney%2F10519079%2Famazon-accounts-hacked-fraudsters%2F Does AWS have any security components on par with ICSF and RACF on the security front that you're aware of? Here's a link to their identity and access management UG... https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys. html?icmpid=docs_iam_console Browsing through it briefly makes me wonder what an AWS secure key repository and management tools might look like. Having been the victim of a minor identity theft myself in recent years, probably adds to my skepticism about cloud service provider security claims. Mike -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Clark Morris Sent: Sunday, October 11, 2020 3:55 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IBM splitting into two companies Caution! This message was sent from outside your organization. [Default] On Sat, 10 Oct 2020 10:40:07 -0700 (PDT), in bit.listserv.ibm-main computer chyck <rpanz...@gmail.com> wrote: >> snip much > >Cloud computing is alot like teenage sex - everybody is doing it (or >wants to do it) but nobody has a flippin' clue how to do it correctly!!! What I fear is that Amazon and Microsoft both have a far better idea of what cloud computing is and how to do it than does IBM. I also suspect that Amazon has all of their computing on their cloud and is very well aware of the need for high security and has worked very hard to achieve it. Microsoft based on my experience with their Knowledge Center (repository for fixes and the equivalent of PTF cover letters) seems to understand high availability better than IBM based on postings here on ibm-main. Clark Morris ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
