davidkclark

4 ms·

1. 1.▲
   by davidkclark 8y ago

   Hence the hard swallowing.
2. 2.▲
   by davidkclark 9y ago

   Disabling the root user again with dsenableroot -d does not re-enable the exploit
3. 3.▲
   by davidkclark 12y ago

   I wonder how many sperm or egg donors will register on 23andme and receive an interesting email... Or how many children conceived in that way will find half brothers and half sisters. I wonder if you could see traces of "prolific"
4. 4.▲
   by davidkclark 13y ago

   I have also had a simple app rejected, then approved once some complexity was added. It was a totally silly app that was pretty much an exercise in what exactly they would accept as the simplest app. ( https://itunes.apple.com&#x2
5. 5.▲
   by davidkclark 13y ago

   This. The tech described is pretty neat... Give you my email creds? Hell no. But _I_ could do all that myself. I think that would be one way that linkedin could save this - release an easy to set up open source version, say one click to a h
6. 6.▲
   by davidkclark 13y ago

   What could they do about it? Not allow you to create a mail account that points to linkedin.com as the server?
7. 7.▲
   by davidkclark 13y ago

   There is really no Apple approval to be given or not given here. It is really just creating a new email account. There is no real way that Apple could stop them from doing this if they wanted to. It is up to you if you tell linkedin your em
8. 8.▲
   by davidkclark 13y ago

   It's pretty easy to convince yourself that "* with the type" is wrong when you see this: int* a, b; // a is int* but b is int