Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.system > #56833 > unrolled thread
| Started by | Ted Lee <tmplee@gmail.com> |
|---|---|
| First post | 2014-02-22 12:56 -0600 |
| Last post | 2014-03-01 21:53 +0000 |
| Articles | 17 on this page of 197 — 21 participants |
Back to article view | Back to comp.sys.mac.system
Latest IOS/OS X SSL security flaw Ted Lee <tmplee@gmail.com> - 2014-02-22 12:56 -0600
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-02-22 14:15 -0500
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-22 14:47 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-22 21:30 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-22 19:04 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-23 00:36 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 09:48 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-23 16:41 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 12:05 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-23 17:22 +0000
Re: Latest IOS/OS X SSL security flaw billy@MIX.COM - 2014-02-24 02:15 +0000
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-24 03:57 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 18:25 -0500
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-25 08:16 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-25 19:50 -0500
Re: Latest IOS/OS X SSL security flaw Don Bruder <dakidd@sonic.net> - 2014-02-23 07:51 -0800
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 11:23 -0500
Re: Latest IOS/OS X SSL security flaw Don Bruder <dakidd@sonic.net> - 2014-02-23 15:05 -0800
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 20:01 -0500
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-24 04:21 +0000
Re: Latest IOS/OS X SSL security flaw Bill Findlay <yaldnif.w@blueyonder.co.uk> - 2014-02-24 04:35 +0000
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-24 06:00 +0000
Re: Latest IOS/OS X SSL security flaw JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-24 16:52 -0500
Re: Latest IOS/OS X SSL security flaw Bill Findlay <yaldnif.w@blueyonder.co.uk> - 2014-02-24 21:54 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 17:44 -0500
Re: Latest IOS/OS X SSL security flaw Bill Findlay <yaldnif.w@blueyonder.co.uk> - 2014-02-25 00:19 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 19:26 -0500
Re: Latest IOS/OS X SSL security flaw Bill Findlay <yaldnif.w@blueyonder.co.uk> - 2014-02-25 00:40 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 19:46 -0500
Re: Latest IOS/OS X SSL security flaw Bill Findlay <yaldnif.w@blueyonder.co.uk> - 2014-02-25 00:57 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 17:43 -0500
Re: Latest IOS/OS X SSL security flaw Bill Findlay <yaldnif.w@blueyonder.co.uk> - 2014-02-25 00:19 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 19:29 -0500
Re: Latest IOS/OS X SSL security flaw Bill Findlay <yaldnif.w@blueyonder.co.uk> - 2014-02-25 00:40 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 19:45 -0500
Re: Latest IOS/OS X SSL security flaw Bill Findlay <yaldnif.w@blueyonder.co.uk> - 2014-02-25 00:57 +0000
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-24 05:04 +0000
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-24 06:00 +0000
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-24 16:10 +0000
Re: Latest IOS/OS X SSL security flaw Kurt Ullman <kurtullman@yahoo.com> - 2014-02-24 12:15 -0500
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-24 22:33 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 17:47 -0500
Re: Latest IOS/OS X SSL security flaw Richard Kettlewell <rjk@greenend.org.uk> - 2014-02-25 13:41 +0000
Re: Latest IOS/OS X SSL security flaw Kurt Ullman <kurtullman@yahoo.com> - 2014-02-25 09:06 -0500
Re: Latest IOS/OS X SSL security flaw billy@MIX.COM - 2014-02-25 17:34 +0000
Re: Latest IOS/OS X SSL security flaw billy@MIX.COM - 2014-02-25 19:14 +0000
Re: Latest IOS/OS X SSL security flaw Paul Sture <nospam@sture.ch> - 2014-02-25 20:42 +0100
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-25 21:32 +0000
Re: Latest IOS/OS X SSL security flaw Ted Lee <tmplee@gmail.com> - 2014-02-25 17:12 -0600
Re: Latest IOS/OS X SSL security flaw Ted Lee <tmplee@gmail.com> - 2014-02-25 17:24 -0600
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-26 02:38 +0000
Re: Latest IOS/OS X SSL security flaw Ted Lee <tmplee@gmail.com> - 2014-02-25 21:03 -0600
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-26 04:19 +0000
Re: Latest IOS/OS X SSL security flaw "M. John Matlaw" <nouser@invalid.com> - 2014-02-28 11:29 -0500
Re: Latest IOS/OS X SSL security flaw Ted Lee <tmplee@gmail.com> - 2014-02-28 12:48 -0600
Re: Latest IOS/OS X SSL security flaw billy@MIX.COM - 2014-02-26 01:44 +0000
Re: Latest IOS/OS X SSL security flaw billy@MIX.COM - 2014-02-25 21:59 +0000
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-24 22:33 +0000
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-24 23:13 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 17:45 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-24 23:17 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 18:28 -0500
Re: Latest IOS/OS X SSL security flaw JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-24 23:16 -0500
Re: Latest IOS/OS X SSL security flaw Don Bruder <dakidd@sonic.net> - 2014-02-24 21:17 -0800
Re: Latest IOS/OS X SSL security flaw Paul Sture <nospam@sture.ch> - 2014-02-25 21:03 +0100
Re: Latest IOS/OS X SSL security flaw Paul Sture <nospam@sture.ch> - 2014-02-25 21:00 +0100
Re: Latest IOS/OS X SSL security flaw billy@MIX.COM - 2014-02-25 22:02 +0000
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-25 08:11 +0000
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-25 16:47 +0000
Re: Latest IOS/OS X SSL security flaw JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-25 17:03 -0500
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-25 19:45 -0500
Re: Latest IOS/OS X SSL security flaw JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-26 00:05 -0500
Re: Latest IOS/OS X SSL security flaw Paul Sture <nospam@sture.ch> - 2014-02-25 20:57 +0100
Re: Latest IOS/OS X SSL security flaw "M. John Matlaw" <nouser@invalid.com> - 2014-02-26 09:52 -0500
Re: Latest IOS/OS X SSL security flaw Paul Sture <nospam@sture.ch> - 2014-04-06 02:36 +0200
Re: Latest IOS/OS X SSL security flaw Paul Sture <nospam@sture.ch> - 2014-02-24 21:24 +0100
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-24 20:43 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 17:40 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-23 16:47 +0000
Re: Latest IOS/OS X SSL security flaw Don Bruder <dakidd@sonic.net> - 2014-02-23 15:37 -0800
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 20:08 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-24 01:15 +0000
Re: Latest IOS/OS X SSL security flaw Don Bruder <dakidd@sonic.net> - 2014-02-23 18:45 -0800
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-24 02:52 +0000
Re: Latest IOS/OS X SSL security flaw Don Bruder <dakidd@sonic.net> - 2014-02-23 19:01 -0800
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-24 04:23 +0000
Re: Latest IOS/OS X SSL security flaw Paul Sture <nospam@sture.ch> - 2014-02-24 22:10 +0100
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-24 22:21 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 17:27 -0500
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 17:27 -0500
Re: Latest IOS/OS X SSL security flaw Don Bruder <dakidd@sonic.net> - 2014-02-24 21:05 -0800
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-25 19:34 -0500
Re: Latest IOS/OS X SSL security flaw Paul Sture <nospam@sture.ch> - 2014-02-24 21:58 +0100
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 18:04 -0500
Re: Latest IOS/OS X SSL security flaw billy@MIX.COM - 2014-02-25 02:44 +0000
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-24 01:14 +0000
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-24 04:11 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 18:36 -0500
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-25 08:20 +0000
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-25 17:00 +0000
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-25 20:05 +0000
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-25 21:31 +0000
Re: Latest IOS/OS X SSL security flaw Don Bruder <dakidd@sonic.net> - 2014-02-25 19:13 -0800
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-26 04:35 +0000
Re: Latest IOS/OS X SSL security flaw billy@MIX.COM - 2014-02-26 06:42 +0000
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-03-01 21:57 +0000
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-26 23:29 +0000
Re: Latest IOS/OS X SSL security flaw Walter Bushell <proto@panix.com> - 2014-04-13 15:06 -0400
Re: Latest IOS/OS X SSL security flaw Tom Stiller <clusterfux.upmon@gmail.com> - 2014-04-13 21:11 +0000
Re: Latest IOS/OS X SSL security flaw Walter Bushell <proto@panix.com> - 2014-04-15 17:03 -0400
Re: Latest IOS/OS X SSL security flaw Your Name <YourName@YourISP.com> - 2014-04-16 09:29 +1200
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-25 19:29 -0500
Re: Latest IOS/OS X SSL security flaw Bill Findlay <yaldnif.w@blueyonder.co.uk> - 2014-02-26 00:49 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-25 19:59 -0500
Re: Latest IOS/OS X SSL security flaw Bill Findlay <yaldnif.w@blueyonder.co.uk> - 2014-02-26 02:03 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-25 22:13 -0500
Re: Latest IOS/OS X SSL security flaw Bill Findlay <yaldnif.w@blueyonder.co.uk> - 2014-02-26 14:03 +0000
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-26 23:42 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-27 17:03 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-26 02:47 +0000
Re: Latest IOS/OS X SSL security flaw JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-26 00:10 -0500
Re: Latest IOS/OS X SSL security flaw Walter Bushell <proto@panix.com> - 2014-04-13 15:11 -0400
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 15:43 -0400
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-26 02:42 +0000
Re: Latest IOS/OS X SSL security flaw Walter Bushell <proto@panix.com> - 2014-04-13 15:08 -0400
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-04-13 15:41 -0400
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-25 19:18 -0500
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-26 23:39 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-27 17:09 -0500
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 13:03 -0500
Re: Latest IOS/OS X SSL security flaw Bill Findlay <yaldnif.w@blueyonder.co.uk> - 2014-02-23 01:32 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 10:07 -0500
Re: Latest IOS/OS X SSL security flaw Paul Sture <nospam@sture.ch> - 2014-04-06 02:44 +0200
Re: Latest IOS/OS X SSL security flaw JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-22 17:49 -0500
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-22 19:07 -0500
Re: Latest IOS/OS X SSL security flaw JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-22 22:23 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-23 03:49 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 10:12 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-23 16:42 +0000
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-02-23 14:38 -0500
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 10:11 -0500
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-02-23 14:38 -0500
Re: Latest IOS/OS X SSL security flaw Jim Gibson <jimsgibson@gmail.com> - 2014-02-24 10:42 -0800
Re: Latest IOS/OS X SSL security flaw JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-24 17:07 -0500
Re: Latest IOS/OS X SSL security flaw Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-02-22 23:01 -0800
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-02-23 14:38 -0500
Re: Latest IOS/OS X SSL security flaw billy@MIX.COM - 2014-02-24 01:46 +0000
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-03-01 21:52 +0000
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-03-02 00:05 -0500
Re: Latest IOS/OS X SSL security flaw Paul Sture <nospam@sture.ch> - 2014-02-24 22:24 +0100
Re: Latest IOS/OS X SSL security flaw mcarels@xs4all.nl (Maarten Carels) - 2014-02-24 10:43 +0100
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 18:39 -0500
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-24 19:16 -0500
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-22 14:18 -0500
Re: Latest IOS/OS X SSL security flaw Tim McNamara <timmcn@bitstream.net> - 2014-02-22 13:43 -0600
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-22 14:52 -0500
Re: Latest IOS/OS X SSL security flaw Richard Kettlewell <rjk@greenend.org.uk> - 2014-02-22 20:05 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-22 15:16 -0500
Re: Latest IOS/OS X SSL security flaw Richard Kettlewell <rjk@greenend.org.uk> - 2014-02-22 21:10 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-22 16:25 -0500
Re: Latest IOS/OS X SSL security flaw Richard Kettlewell <rjk@greenend.org.uk> - 2014-02-22 22:13 +0000
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-22 22:19 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-22 18:55 -0500
Re: Latest IOS/OS X SSL security flaw Richard Kettlewell <rjk@greenend.org.uk> - 2014-02-23 09:38 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 10:17 -0500
Re: Latest IOS/OS X SSL security flaw Richard Kettlewell <rjk@greenend.org.uk> - 2014-02-23 15:42 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 10:45 -0500
Re: Latest IOS/OS X SSL security flaw Richard Kettlewell <rjk@greenend.org.uk> - 2014-02-23 17:09 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 13:51 -0500
Re: Latest IOS/OS X SSL security flaw Richard Kettlewell <rjk@greenend.org.uk> - 2014-02-23 20:07 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 15:14 -0500
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 15:20 -0500
Re: Latest IOS/OS X SSL security flaw billy@MIX.COM - 2014-02-24 02:18 +0000
Re: Latest IOS/OS X SSL security flaw JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-22 17:51 -0500
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-02-22 17:55 -0500
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-22 21:50 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-22 19:09 -0500
Re: Latest IOS/OS X SSL security flaw Alan Baker <alangbaker@telus.net> - 2014-02-22 12:35 -0800
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-02-22 16:59 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-22 22:14 +0000
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-02-22 17:53 -0500
Re: Latest IOS/OS X SSL security flaw JF Mezei <jfmezei.spamnot@vaxination.ca> - 2014-02-22 18:01 -0500
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-02-22 18:22 -0500
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-02-22 18:29 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-22 23:33 +0000
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-02-23 18:23 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-24 01:08 +0000
Re: Latest IOS/OS X SSL security flaw Lewis <g.kreme@gmail.com.dontsendmecopies> - 2014-02-22 21:49 +0000
Re: Latest IOS/OS X SSL security flaw Kevin McMurtrie <mcmurtrie@pixelmemory.us> - 2014-02-22 22:57 -0800
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-23 16:36 +0000
Re: Latest IOS/OS X SSL security flaw Alan Browne <alan.browne@FreelunchVideotron.ca> - 2014-02-23 11:58 -0500
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-02-23 14:35 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-23 21:03 +0000
Re: Latest IOS/OS X SSL security flaw nospam <nospam@nospam.invalid> - 2014-02-23 18:23 -0500
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-02-24 01:07 +0000
Re: Latest IOS/OS X SSL security flaw billy@MIX.COM - 2014-02-24 01:53 +0000
Re: Latest IOS/OS X SSL security flaw Jolly Roger <jollyroger@pobox.com> - 2014-03-01 21:53 +0000
Page 10 of 10 — ← Prev page 1 … 8 9 [10]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2014-02-22 17:53 -0500 |
| Message-ID | <220220141753376463%nospam@nospam.invalid> |
| In reply to | #56858 |
In article <bmslqmFn3b4U1@mid.individual.net>, Jolly Roger <jollyroger@pobox.com> wrote: > >> <https://www.imperialviolet.org/2014/02/22/applebug.html> > >> > >> It would seem that the bug is a single extra "goto" which is not inside > >> the "if" that precedes it. > > > > the problem is that there is no 'if' that precedes it. > > LOL! mr.know-it-all always knows better than everyone and has to correct > you even when you weren't wrong! Of course for him to be right, we must > re-define the word "precede" to mean "immediately precede" rather than > what the word actually means: to come before. Anyone with half a brain > cell knows you meant "to come before" and there most certainly *is* an > if before the errant goto statement, which is clear to see. what's clear is you're once again wrong (and won't admit it). there are *clearly* two gotos in a row. anyone can see that, and how that is the bug. only one of them can have an if statement preceding it. the second goto has no if statement preceding it, and because of that, it will always be executed. that's the bug. and you call yourself a professional developer? laughable. the link above agrees with me, not you: Note the two goto fail lines in a row. The first one is correctly bound to the if statement but the second, despite the indentation, isn't conditional at all.
[toc] | [prev] | [next] | [standalone]
| From | JF Mezei <jfmezei.spamnot@vaxination.ca> |
|---|---|
| Date | 2014-02-22 18:01 -0500 |
| Message-ID | <53092c34$0$10563$c3e8da3$33881b6a@news.astraweb.com> |
| In reply to | #56863 |
On 14-02-22 17:53, nospam wrote: > the second goto has no if statement preceding it, and because of that, > it will always be executed. that's the bug. Assuming no compiler optimization, the second goto will not ALWAYS execute because the execution may not got to it if any of the 2 preceding conditions are met and their gotos are executed instead of that second goto. When you factor in optimization, this whole block is likely replaced by a single goto fail statement.
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2014-02-22 18:22 -0500 |
| Message-ID | <220220141822159532%nospam@nospam.invalid> |
| In reply to | #56865 |
In article <53092c34$0$10563$c3e8da3$33881b6a@news.astraweb.com>, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote: > > the second goto has no if statement preceding it, and because of that, > > it will always be executed. that's the bug. > > Assuming no compiler optimization, the second goto will not ALWAYS > execute because the execution may not got to it if any of the 2 > preceding conditions are met and their gotos are executed instead of > that second goto. there could be a lot of reasons it would not get to that particular point. that's not the problem. the bug is that anything past the first goto of the pair won't be seen because the second goto will always execute. code completion would have caught it. > When you factor in optimization, this whole block is likely replaced by > a single goto fail statement. no.
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2014-02-22 18:29 -0500 |
| Message-ID | <220220141829536986%nospam@nospam.invalid> |
| In reply to | #56866 |
In article <220220141822159532%nospam@nospam.invalid>, nospam <nospam@nospam.invalid> wrote: > > > the second goto has no if statement preceding it, and because of that, > > > it will always be executed. that's the bug. > > > > Assuming no compiler optimization, the second goto will not ALWAYS > > execute because the execution may not got to it if any of the 2 > > preceding conditions are met and their gotos are executed instead of > > that second goto. > > there could be a lot of reasons it would not get to that particular > point. that's not the problem. > > the bug is that anything past the first goto of the pair won't be seen > because the second goto will always execute. > > code completion would have caught it. code coverage, that is.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-02-22 23:33 +0000 |
| Message-ID | <bmsqdsFnr6sU1@mid.individual.net> |
| In reply to | #56863 |
On 2014-02-22, nospam <nospam@nospam.invalid> wrote: > In article <bmslqmFn3b4U1@mid.individual.net>, Jolly Roger ><jollyroger@pobox.com> wrote: > >> >> <https://www.imperialviolet.org/2014/02/22/applebug.html> >> >> >> >> It would seem that the bug is a single extra "goto" which is not inside >> >> the "if" that precedes it. >> > >> > the problem is that there is no 'if' that precedes it. >> >> LOL! mr.know-it-all always knows better than everyone and has to correct >> you even when you weren't wrong! Of course for him to be right, we must >> re-define the word "precede" to mean "immediately precede" rather than >> what the word actually means: to come before. Anyone with half a brain >> cell knows you meant "to come before" and there most certainly *is* an >> if before the errant goto statement, which is clear to see. >> >> What you said is factually correct, Alan. Because the author chose not >> to use curly braces in the if block, only the very first goto statement >> is included in the if clause, and the second goto statement is >> effectively outside of the if clause. > > what's clear is you're once again wrong (and won't admit it). mr.know-it-all loves to project his own flaws onto others. > there are *clearly* two gotos in a row. anyone can see that, and how > that is the bug. Weasel boy loves straw man arguments. Note how while nobody is debating that there are two goto statements in a row, he tries to make it appear so. Keep on digging, weasel boy! > only one of them can have an if statement preceding it. preceding: come before in order or position if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0) goto fail; goto fail; Clearly the if statement precedes *both* goto statements. mr.know-it-all would love to re-define the word "preceding" to mean "immediately preceding"; but that's clearly not what Alan meant when he said it, nor is it what the word itself means. mr.know-it-all has to stick with this petty argument, because it's literally all he's got. LAME. > the second goto has no if statement preceding it, and because of that, > it will always be executed. that's the bug. Now mr.know-it-all tries to pretend that both Alan and I were saying something we weren't actually saying (because the only way weasel boy's argument can make sense is if the word "preceding" is replaced by the phrase "immediately preceding", which is not what Alan said). Next, he spins it around by restating what Alan actually did say as if it's somehow different than what Alan said. Lame. > and you call yourself a professional developer? laughable. And now mr.know-it-all must resort to an ad hominem attack. I don't just call myself a professional software developer. I'm respected by my peers (something that absolutely must be earned in this field). I wouldn't expect a weasel of a fuck tard like mr.know-it-all to be able to appreciate or even recognize a good software developer though - not that this has anything to do with the discussion at hand. Weasel boy just loves distractions! > the link above agrees with me, not you: > > Note the two goto fail lines in a row. The first one is correctly > bound to the if statement but the second, despite the indentation, > isn't conditional at all. Note how mr.know-it-all conveniently deleted the portion of my reply where I said what he just restated above (I went ahead and restored it above for clarity), and tries to pass off his explanation as his own. You can't make this stuff up, folks! Here's what I said and weasel boy purposefully omitted from the quoted text in his reply: >> What you said is factually correct, Alan. Because the author chose not >> to use curly braces in the if block, only the very first goto statement >> is included in the if clause, and the second goto statement is >> effectively outside of the if clause. Weasel boy just loves being disingenuous and petty! -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2014-02-23 18:23 -0500 |
| Message-ID | <230220141823338141%nospam@nospam.invalid> |
| In reply to | #56868 |
In article <bmsqdsFnr6sU1@mid.individual.net>, Jolly Roger <jollyroger@pobox.com> wrote: > > only one of them can have an if statement preceding it. > > preceding: come before in order or position > > if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0) > goto fail; > goto fail; > > Clearly the if statement precedes *both* goto statements. hundreds of other statements also precede it. so what? precede in this context can only have meant one thing. you are twisting it just to argue.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-02-24 01:08 +0000 |
| Message-ID | <bmvkcjFbp4lU2@mid.individual.net> |
| In reply to | #56925 |
On 2014-02-23, nospam <nospam@nospam.invalid> wrote: > In article <bmsqdsFnr6sU1@mid.individual.net>, Jolly Roger ><jollyroger@pobox.com> wrote: > >> > only one of them can have an if statement preceding it. >> >> preceding: come before in order or position >> >> if ((err = SSLHashSHA1.update(&hashCtx, &signedParams)) != 0) >> goto fail; >> goto fail; >> >> Clearly the if statement precedes *both* goto statements. > > hundreds of other statements also precede it. so what? > > precede in this context can only have meant one thing. you are twisting > it just to argue. mr.know-it-all just *loves* to project his own faults onto others. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | Lewis <g.kreme@gmail.com.dontsendmecopies> |
|---|---|
| Date | 2014-02-22 21:49 +0000 |
| Message-ID | <slrnlgi6qc.22tr.g.kreme@oswin.local> |
| In reply to | #56833 |
In message <lears8$l8d$1@dont-email.me> Ted Lee <tmplee@gmail.com> wrote: > The press and gossip rag reports say the recently discovered security > flaw with SSL is present in both IOS and OS X. The patch for IOS showed > up last night. The reports say the OS X one will be out soon. Has > anyone run across a technically competent (as opposed to sensationalized > fear-mongering amateur drivel) discussion of the flaw *and* a conclusive > statement that it is indeed present in OS X? Given Apple's policy of > not discussing or acknowledging security flaws until a patch is > available, I have to wonder if the flaw is in fact present in OS X -- > for, if it were, wouldn't they wait to release anything (including a > fix) about it until the patch was available for both? I haven't seen a reasonable discussion on what the flaw is. It appears to require a rather esoteric set of circumstances that, I think, almost no actual users would ever encounter, but I can't find real information. -- Women like silent men, they think they're listening.
[toc] | [prev] | [next] | [standalone]
| From | Kevin McMurtrie <mcmurtrie@pixelmemory.us> |
|---|---|
| Date | 2014-02-22 22:57 -0800 |
| Message-ID | <mcmurtrie-BA27FF.22572822022014@c-61-68-245-199.per.connect.net.au> |
| In reply to | #56833 |
In article <lears8$l8d$1@dont-email.me>, Ted Lee <tmplee@gmail.com> wrote: > The press and gossip rag reports say the recently discovered security > flaw with SSL is present in both IOS and OS X. The patch for IOS showed > up last night. The reports say the OS X one will be out soon. Has > anyone run across a technically competent (as opposed to sensationalized > fear-mongering amateur drivel) discussion of the flaw *and* a conclusive > statement that it is indeed present in OS X? Given Apple's policy of > not discussing or acknowledging security flaws until a patch is > available, I have to wonder if the flaw is in fact present in OS X -- > for, if it were, wouldn't they wait to release anything (including a > fix) about it until the patch was available for both? The security hole looks quite severe and easy to exploit, especially since the source code is out for it. (Thanks for the reference, Alan Baker) I can't believe that the source code could exist. Compilers are supposed to flag or reject branching flaws that produce unreachable code.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-02-23 16:36 +0000 |
| Message-ID | <bmumcsF59p1U1@mid.individual.net> |
| In reply to | #56884 |
On 2014-02-23, Kevin McMurtrie <mcmurtrie@pixelmemory.us> wrote: > In article <lears8$l8d$1@dont-email.me>, Ted Lee <tmplee@gmail.com> > wrote: > >> The press and gossip rag reports say the recently discovered security >> flaw with SSL is present in both IOS and OS X. The patch for IOS showed >> up last night. The reports say the OS X one will be out soon. Has >> anyone run across a technically competent (as opposed to sensationalized >> fear-mongering amateur drivel) discussion of the flaw *and* a conclusive >> statement that it is indeed present in OS X? Given Apple's policy of >> not discussing or acknowledging security flaws until a patch is >> available, I have to wonder if the flaw is in fact present in OS X -- >> for, if it were, wouldn't they wait to release anything (including a >> fix) about it until the patch was available for both? > > The security hole looks quite severe and easy to exploit, especially > since the source code is out for it. (Thanks for the reference, Alan > Baker) Shit happens. Apple's patched iOS, and has said an OSX patch is forthcoming. Apparently on OSX, Firefox and Chrome are not affected. > I can't believe that the source code could exist. Compilers are > supposed to flag or reject branching flaws that produce unreachable code. The code isn't really illegal. It's just written using bad practices, IMO. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | Alan Browne <alan.browne@FreelunchVideotron.ca> |
|---|---|
| Date | 2014-02-23 11:58 -0500 |
| Message-ID | <ldqdnVJ6A54GtZfOnZ2dnUVZ_uydnZ2d@giganews.com> |
| In reply to | #56884 |
On 2014.02.23, 01:57 , Kevin McMurtrie wrote:
> In article <lears8$l8d$1@dont-email.me>, Ted Lee <tmplee@gmail.com>
> wrote:
>
>> The press and gossip rag reports say the recently discovered security
>> flaw with SSL is present in both IOS and OS X. The patch for IOS showed
>> up last night. The reports say the OS X one will be out soon. Has
>> anyone run across a technically competent (as opposed to sensationalized
>> fear-mongering amateur drivel) discussion of the flaw *and* a conclusive
>> statement that it is indeed present in OS X? Given Apple's policy of
>> not discussing or acknowledging security flaws until a patch is
>> available, I have to wonder if the flaw is in fact present in OS X --
>> for, if it were, wouldn't they wait to release anything (including a
>> fix) about it until the patch was available for both?
>
> I can't believe that the source code could exist. Compilers are
> supposed to flag or reject branching flaws that produce unreachable code.
Depends on the compiler and what switches/pragmas are set. Would likely
just do dead code removal. The code optimizer could then remove the 2nd
goto JMP as well...
I agree the compiler could raise warnings. They in turn can be
suppressed (pragmas set by human) or ignored (human).
--
Privacy has become an essential personal chore that most
people are not trained to perform.
- Jaron Lanier, Scientific American, 2013.11.
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2014-02-23 14:35 -0500 |
| Message-ID | <230220141435478199%nospam@nospam.invalid> |
| In reply to | #56902 |
In article <ldqdnVJ6A54GtZfOnZ2dnUVZ_uydnZ2d@giganews.com>, Alan Browne <alan.browne@FreelunchVideotron.ca> wrote: > I agree the compiler could raise warnings. They in turn can be > suppressed (pragmas set by human) or ignored (human). it did, and apparently was ignored.
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-02-23 21:03 +0000 |
| Message-ID | <bmv61bF8q46U1@mid.individual.net> |
| In reply to | #56914 |
On 2014-02-23, nospam <nospam@nospam.invalid> wrote: > In article <ldqdnVJ6A54GtZfOnZ2dnUVZ_uydnZ2d@giganews.com>, Alan Browne ><alan.browne@FreelunchVideotron.ca> wrote: > >> I agree the compiler could raise warnings. They in turn can be >> suppressed (pragmas set by human) or ignored (human). > > it did, and apparently was ignored. You seem quite certain. Is the compile log available? -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | nospam <nospam@nospam.invalid> |
|---|---|
| Date | 2014-02-23 18:23 -0500 |
| Message-ID | <230220141823318017%nospam@nospam.invalid> |
| In reply to | #56921 |
In article <bmv61bF8q46U1@mid.individual.net>, Jolly Roger <jollyroger@pobox.com> wrote: > >> I agree the compiler could raise warnings. They in turn can be > >> suppressed (pragmas set by human) or ignored (human). > > > > it did, and apparently was ignored. > > You seem quite certain. Is the compile log available? <http://imgur.com/ihdmFC2>
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-02-24 01:07 +0000 |
| Message-ID | <bmvkb8Fbp4lU1@mid.individual.net> |
| In reply to | #56924 |
On 2014-02-23, nospam <nospam@nospam.invalid> wrote: > In article <bmv61bF8q46U1@mid.individual.net>, Jolly Roger ><jollyroger@pobox.com> wrote: > >> >> I agree the compiler could raise warnings. They in turn can be >> >> suppressed (pragmas set by human) or ignored (human). >> > >> > it did, and apparently was ignored. >> >> You seem quite certain. Is the compile log available? > ><http://imgur.com/ihdmFC2> And is that a screen shot from the system of the actual Apple developer who wrote / debugged / built the code in question? Or are you making assumptions? -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [next] | [standalone]
| From | billy@MIX.COM |
|---|---|
| Date | 2014-02-24 01:53 +0000 |
| Message-ID | <lee8ni$7u8$2@reader2.panix.com> |
| In reply to | #56929 |
Jolly Roger <jollyroger@pobox.com> writes, quoting
nospam <nospam@nospam.invalid>:
> >> You seem quite certain. Is the compile log available?
> >
> ><http://imgur.com/ihdmFC2>
>
> And is that a screen shot from the system of the actual Apple developer
> who wrote / debugged / built the code in question? Or are you making
> assumptions?
Of course not, and of course. As I just mentioned, the only test that
matters is the one you'd run on the actual source module.
Billy Y..
--
sub #'9+1 ,r0 ; convert ascii byte
add #9.+1 ,r0 ; to an integer
bcc 20$ ; not a number
[toc] | [prev] | [next] | [standalone]
| From | Jolly Roger <jollyroger@pobox.com> |
|---|---|
| Date | 2014-03-01 21:53 +0000 |
| Message-ID | <bnf35tFl9faU2@mid.individual.net> |
| In reply to | #57303 |
On 2014-02-24, billy@MIX.COM <billy@MIX.COM> wrote: > Jolly Roger <jollyroger@pobox.com> writes, quoting > nospam <nospam@nospam.invalid>: > >> >> You seem quite certain. Is the compile log available? >> > >> ><http://imgur.com/ihdmFC2> >> >> And is that a screen shot from the system of the actual Apple developer >> who wrote / debugged / built the code in question? Or are you making >> assumptions? > > Of course not, and of course. As I just mentioned, the only test that > matters is the one you'd run on the actual source module. Exactly my point. Thanks. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR
[toc] | [prev] | [standalone]
Page 10 of 10 — ← Prev page 1 … 8 9 [10]
Back to top | Article view | comp.sys.mac.system
csiph-web