*cough*
12-01-2017, 02:51 AM,
Post: #626
RE: *cough*
(12-01-2017, 12:24 AM)FuturDreamz Wrote:
(11-18-2017, 12:02 PM)FuturDreamz Wrote:
(11-18-2017, 07:04 AM)Jehannum Wrote:
(11-18-2017, 06:01 AM)FuturDreamz Wrote: It did work. The fact that it died two days later is unrelated.

The fact that you don't understand DevOps is apparent in your post.

I was just picking on you with the broken computer dig.

I may not know DevOps very well, but I can presume that it is reliant on good communication. Although I can't find it at the moment (Continuum has it's limits), I was recent reading a report describing Apple's structure as that of a security company where employees are segregated into smaller units/cells which have very little communication and knowledge of other projects. That kind of organization can make collaborating on resolving bugs a lot more difficult, ESPECIALLY if you keep development and mainteance seperate. 

This does seem to match up with the increasing complaints I hear from Apple users and the decreasing complaints from Microsoft users (complaints from Windows Phone users have almost completely dropped off, but for a different reason)

https://m.slashdot.org/story/334259

hmm...


Every company does this after a blunder.
Its called a post-mortem.

Identify the break down and implement any necessary process and/or engineering fixes needed to safeguard against that class of failure.
12-01-2017, 06:42 AM,
Post: #627
RE: *cough*
(12-01-2017, 12:24 AM)FuturDreamz Wrote:
(11-18-2017, 12:02 PM)FuturDreamz Wrote:
(11-18-2017, 07:04 AM)Jehannum Wrote:
(11-18-2017, 06:01 AM)FuturDreamz Wrote: It did work. The fact that it died two days later is unrelated.

The fact that you don't understand DevOps is apparent in your post.

I was just picking on you with the broken computer dig.

I may not know DevOps very well, but I can presume that it is reliant on good communication. Although I can't find it at the moment (Continuum has it's limits), I was recent reading a report describing Apple's structure as that of a security company where employees are segregated into smaller units/cells which have very little communication and knowledge of other projects. That kind of organization can make collaborating on resolving bugs a lot more difficult, ESPECIALLY if you keep development and mainteance seperate. 

This does seem to match up with the increasing complaints I hear from Apple users and the decreasing complaints from Microsoft users (complaints from Windows Phone users have almost completely dropped off, but for a different reason)

https://m.slashdot.org/story/334259

hmm...

One would certainly hope that they would review their process after a mistake like that.

Still doesn't mean you know jack shit about DevOps.
12-02-2017, 03:12 AM,
Post: #628
RE: *cough*
Oof.
Quote:Once an intruder gains access to the user’s iPhone and knows (or recovers) the passcode, there is no single extra layer of protection left. Everything (and I mean, everything) is now completely exposed. Local backups, the keychain, iCloud lock, Apple account password, cloud backups and photos, passwords from the iCloud Keychain, call logs, location data, browsing history, browser tabs and even the user’s original Apple ID password are quickly exposed. The intruder gains control over the user’s other Apple devices registered on the same Apple account, having the ability to remotely erase or lock those devices. Finally, regaining control over hijacked account is made difficult as even the trusted phone number can be replaced.

https://blog.elcomsoft.com/2017/11/ios-1...-security/
The chaos army seems suspiciously well organized.
flickr | Stupid Blog | Twitter
12-02-2017, 04:25 AM,
Post: #629
RE: *cough*
(12-02-2017, 03:12 AM)Gippy Wrote: Oof.
Quote:Once an intruder gains access to the user’s iPhone and knows (or recovers) the passcode, there is no single extra layer of protection left. Everything (and I mean, everything) is now completely exposed. Local backups, the keychain, iCloud lock, Apple account password, cloud backups and photos, passwords from the iCloud Keychain, call logs, location data, browsing history, browser tabs and even the user’s original Apple ID password are quickly exposed. The intruder gains control over the user’s other Apple devices registered on the same Apple account, having the ability to remotely erase or lock those devices. Finally, regaining control over hijacked account is made difficult as even the trusted phone number can be replaced.

https://blog.elcomsoft.com/2017/11/ios-1...-security/

Does that apply to my iPod Nano?  Because that doesn't have any passcode or anything protecting it.

I'm about equal split between apple's and google's ecosystems otherwise.  Nexus phone and tablet, but apple lappy 486.
12-02-2017, 05:07 AM,
Post: #630
RE: *cough*
Shrug
The chaos army seems suspiciously well organized.
flickr | Stupid Blog | Twitter
12-02-2017, 08:00 AM,
Post: #631
RE: *cough*
(12-02-2017, 05:07 AM)Gippy Wrote: Shrug

DOOOOOOOOOM!
12-02-2017, 08:42 AM,
Post: #632
RE: *cough*
(12-02-2017, 04:25 AM)Jehannum Wrote:
(12-02-2017, 03:12 AM)Gippy Wrote: Oof.
Quote:Once an intruder gains access to the user’s iPhone and knows (or recovers) the passcode, there is no single extra layer of protection left. Everything (and I mean, everything) is now completely exposed. Local backups, the keychain, iCloud lock, Apple account password, cloud backups and photos, passwords from the iCloud Keychain, call logs, location data, browsing history, browser tabs and even the user’s original Apple ID password are quickly exposed. The intruder gains control over the user’s other Apple devices registered on the same Apple account, having the ability to remotely erase or lock those devices. Finally, regaining control over hijacked account is made difficult as even the trusted phone number can be replaced.

https://blog.elcomsoft.com/2017/11/ios-1...-security/

Does that apply to my iPod Nano?  Because that doesn't have any passcode or anything protecting it.

I'm about equal split between apple's and google's ecosystems otherwise.  Nexus phone and tablet, but apple lappy 486.

Try it and find out. That article lists step-by-step instructions for each vulnerably.

I'd strongly suspect that you're safer WITHOUT a passcode as it's going to default to the fully secure passwords

and what is a 486? The only references I can find relate to vintage computers - which don't count anyways.
12-05-2017, 02:53 AM,
Post: #633
RE: *cough*
https://arstechnica.com/gadgets/2017/12/...urity-bug/

I gotta be honest though, I don't see what's the big deal about a bug that resolves itself after a single reboot. Granted that reboot should've been made mandatory or the patch should've had a way to enable the fix during the current session, but it's still better than a bug that returns AFTER a reboot.
My logic is infallible. Resistance is futile.
12-05-2017, 06:55 AM, (This post was last modified: 12-05-2017, 06:55 AM by Gippy.)
Post: #634
RE: *cough*
You don’t see the big deal in a root access bug?
Boy, I hope you never write software...
The chaos army seems suspiciously well organized.
flickr | Stupid Blog | Twitter
12-05-2017, 08:44 AM, (This post was last modified: 12-05-2017, 08:45 AM by FuturDreamz.)
Post: #635
RE: *cough*
Literally the entire solution is a reboot. That's the thing tech support demands before they even ask you what the problem is. Yes the problem is significant, but it feels so weird how everyone is getting so upset over it when the fix is this straightforward.


If you want to be fancy, you probably just need to restart a service using the command line.
My logic is infallible. Resistance is futile.
12-06-2017, 03:02 AM,
Post: #636
RE: *cough*
(12-05-2017, 06:55 AM)Gippy Wrote: You don’t see the big deal in a root access bug?
Boy, I hope you never write software...

But he understands how to write software so much better than Apple!
12-06-2017, 10:22 AM,
Post: #637
RE: *cough*
(12-05-2017, 08:44 AM)FuturDreamz Wrote: Literally the entire solution is a reboot. That's the thing tech support demands before they even ask you what the problem is. Yes the problem is significant, but it feels so weird how everyone is getting so upset over it when the fix is this straightforward.


If you want to be fancy, you probably just need to restart a service using the command line.

Then it's an easy patch.  But until a reboot, the machine is leaky like Windows.
12-07-2017, 12:33 AM,
Post: #638
RE: *cough*
http://bgr.com/2017/12/05/instagram-upda...ch-review/
My logic is infallible. Resistance is futile.
12-12-2017, 03:21 AM,
Post: #639
RE: *cough*
http://bgr.com/2017/12/11/iphone-x-wallp...off-notch/
My logic is infallible. Resistance is futile.
12-12-2017, 03:25 AM,
Post: #640
RE: *cough*
https://lifehacker.com/how-to-ditch-appl...1821082984
My logic is infallible. Resistance is futile.
12-12-2017, 05:53 AM,
Post: #641
RE: *cough*
I’ll refrain from commenting on the way that piece of clickbait tends to present opinions as facts, but I will remark that citing macOS recently briefly exposing users to a major security vulnerability as a reason to switch to Windows is varsity level potarded.

For shits and giggles, let’s remember that Apple fixed that issue within twenty-four hours. And then let’s look at the list of unlatched Windows vulnerabilities, shall we?

Three seconds of Googling gets me a list of 490. FOUR HUNDRED AND NINETY.

Yeah. Switch to Windows, hand Google your family photos and let Facebook handle your personal communications. Sounds like a plan. Winning!
ClubbieClubbieClubbieClubbieClubbieClubbieClubbie
ClubbieClubbieClubbieClubbieClubbieClubbieClubbie
ClubbieClubbieClubbieClubbieClubbieClubbie
12-12-2017, 06:10 AM,
Post: #642
RE: *cough*
"varsity level potarded"
Giggle
Clubbie Clubbie Clubbie Clubbie Clubbie Clubbie Clubbie Clubbie ClubbieClubbieClubbieClubbie




12-12-2017, 07:18 PM,
Post: #643
RE: *cough*
https://www.laptopmag.com/articles/macbo...ok-in-2017
My logic is infallible. Resistance is futile.
12-13-2017, 04:09 AM, (This post was last modified: 12-13-2017, 04:09 AM by Gippy.)
Post: #644
RE: *cough*
OMG THIS ONE GUY'S WANTS ARE EVERYBODY'S NEEDS
The chaos army seems suspiciously well organized.
flickr | Stupid Blog | Twitter
12-13-2017, 04:58 AM,
Post: #645
RE: *cough*
EVEN BETTER:

[Image: 380z.gif]
ClubbieClubbieClubbieClubbieClubbieClubbieClubbie
ClubbieClubbieClubbieClubbieClubbieClubbieClubbie
ClubbieClubbieClubbieClubbieClubbieClubbie
12-13-2017, 09:17 AM,
Post: #646
RE: *cough*
NO FIREWIRE FAIL
bedstuy Wrote:mocking a pair of $500 jeans is a form of class warfare... why do you hate my social status?
12-13-2017, 09:18 AM,
Post: #647
RE: *cough*
cough
bedstuy Wrote:mocking a pair of $500 jeans is a form of class warfare... why do you hate my social status?
12-13-2017, 11:43 AM,
Post: #648
RE: *cough*
(12-13-2017, 09:18 AM)roo Wrote: cough

Hot!
12-13-2017, 11:45 AM,
Post: #649
RE: *cough*
Hot Hatch!
bedstuy Wrote:mocking a pair of $500 jeans is a form of class warfare... why do you hate my social status?
12-13-2017, 12:03 PM,
Post: #650
RE: *cough*
*cough*
"The 300ZX Turbo is a dance; it's a song; it's rolling, roaring automotive art. There is no color that doesn't suit it. There is no mood-lifting chemical substance it can't replace." - Automobile Magazine


Forum Jump: