There's usually at least two reasons to get into Earth orbit first: - maintaining an abort window, having some time to verify everything is as it's supposed to be. - because it doesn't matter much, delta-v vise. The energy it takes to reach the moon is pretty much the same, regardless of whether you directly go for earth escape velocity, or suspend your acceleration for a while at orbital velocity. The image in your link that says "falling to the moon" I find misleading, because while in orbit, you're exactly still falling to the earth (keeping to miss because your horizontal velocity is big enough). The amount of energy to invest to go from falling around earth to traveling to the moon is not insignificant, and at this distance the moon doesn't noticably "pull" either, so it's anything but "falling". It's "burning another stage of your rocket" and called the trans-lunar injection.
Anyway, the comparison between going to the moon and going to the sun is pretty flawed. What you might be forgetting is that the whole system, Earth, Moon, you, me, and your superheavy (or supermany, again it doesn't really matter, energy-wise) uranium-laden rockets, are orbiting *sun*. We *are* already falling "towards" it (again we're just fast enough to be continuously missing it). If your rockets are to fall "into" the sun, then they need to shed their velocity that keeps them orbiting sun -- and that's a healthy 30 km/sec. I don't know how much fuel it takes for a delta-v of 30 km/sec, but it's probably a lot. So it requires even more fuel to lift that fuel into earth orbit in the first place, and then some more for that, and so on (the usual rocket equation).
Thanks for that link, Einstein. I traveled back in time and included it in my own post.
And in no way do they *need* all that. They *want* it to offer fancy functionality which is the *last* thing I want in an allegedly highly secure system. Just think of all the code that is required for those fancy features, and when it does get compromised, the attacker can pretty much do anything they want because they have all the permissions. Fuck that. They've lost their credibility to me by pulling off that incredibly stupid mode.
When I was going to install signal because of all the good things I heard about it, my phone presented me with a *massive* list of permissions the Signal app wants: - read sensitive log data - find accounts on the device - read your own contact card - modify your own contact card - read calendar events plus confidential information - add or modify calendar events and send email to guests without owners' knowledge - find accounts on the device - read your contacts - modify your contacts - approximate location (network-based) - precise location (GPS and network-based) - read your text messages (SMS or MMS) - receive text messages (MMS) - receive text messages (SMS) - send SMS messages - edit your text messages (SMS or MMS) - directly call phone numbers - directly call any phone numbers - modify phone state - reroute outgoing calls - read call log - read phone status and identity - write call log - read the contents of your USB storage - modify or delete the contents of your USB storage - read the contents of your USB storage - modify or delete the contents of your USB storage - take pictures and videos - record audio - view Wi-Fi connections - read phone status and identity - send WAP-PUSH-received broadcast - receive data from internet - view network connections - create accounts and set passwords - pair with Bluetooth devices - send sticky broadcast - change network connectivity - connect and disconnect from Wi-Fi - disable your screen lock - full network access - change your audio settings - read sync settings - run at startup - set wallpaper - use accounts on the device - control vibration - prevent device from sleeping - toggle sync on and off
That is less of a problem with safety but with energy expense. It's hard enough to get the super-heavy super-dense spent fuel into orbit, but even then what? You cut the invisible leash attached to it so it falls right into the sun? If you think it works like that, I happento own a nice bridge you might want to consider purchasing.
More like throwing away less than a penny to donate a tiny fraction of a penny... How long would someone be on the pirate bay website, maybe 5 seconds to search for something, download the torrent close the browser and allow the torrent program to do the work.
You forgot the part where the luser closes the TPB browser-tab so the javash^Hcript stops executing. I wonder why....
I don't really see how maxing out your CPU (which in turn generates heat and as a consequence, noise, as well as raising your electricity bill) beats crappy ads and pop-ups...
Whoever is "impersonating" you seems to be doing a decent job as their incoherent retarded gibberish is indistinguishable from your incoherent retarded gibberish.
Now that's pretty impressive. However, it says the best possible current resolution is 14.6nm, so it can't currently resolve state of the art dies. Also those pretty pictures? Their scale is in micrometers, as shown on them.
Yes, if you hit enter at the part where it says "Enter passphrase (empty for no passphrase)", you'll get no passphrase. News at 11. Now since this behavior is consistent across all systems that have ssh-keygen, including linux, why are you using this to discredit OpenBSD? And it may have not occured to you, but there are legitimate use cases for unencrypted keys.
*Look, ma!!!* Home directories with.ssh/id_rsa,.ssh/id_dsa
Look ma, even if you're too lazy to enter a passphrase, they're still not world readable. This is, btw, layered security, the very thing you're trying to talk away. Stop spreading nonsense in order to appear to have a point.
I wouldn't be surprised if the/. owners/editors think OpenBSD is yet another linux distro. And no, I'm not joking. This is a mainstream news site for joe sixpack, operated by nontechs who want money. So there's that.
ssh-keygen doesn't generate unencrypted ssh keys by default, that only happens when you skip entering a passphrase (same behavior as ssh-keygen on literally any other platform, because - who knew - it actually originates from OpenBSD). If you do enter a passphrase, it will even refuse to generate a key if the passphrase is too short.
As for layered security, there's plenty of that in OpenBSD, a good deal of which other OSs do not have. Most recent example would be the "pledge" system call (formerly known as "tame").
I particularly enjoy stealing them from CIFS and NFS shares and backups, because even if the OpenBSD box is "secure", people inevitably leave those convenient passphrase keys lying around.
Aha, the "passphrase keys". For the record, as anything else, the private key is created chmod 600. You're not "stealing" shit, you're making things up.
Are you sure about that? I agree that it is theoretically possible, but in practical terms, I believe it is.
People have done it for older chips
Yep, and older chips in comparison are huge and have something like 2-3 interconnect layers. Modern chips have a tiny feature size, and on top of the silicon, a stack of >10 interconnect layers, your microscope will have a hard time looking through those (that is, provided these things could be optically inspected in the first place -- the wavelength of light currently is two orders of magnitude bigger than the feature size).
I for one are not aware of a process that can remove exactly a nm-thick layer of interconnects (in order to expose the next one in the stack) without damaging that next layer. If you are, please enlighten me.
AFAIK these days dies have too small of a feature size for meaningful optical inspection (feature size way smaller than the wavelength of light), and dozens of layers from which, even if you could, you'd only see the topmost one, and simply way too many features to begin with.
Could you rephrase that in a way that doesn't suggest you just had an OCD attack? Preferrably not before cooling down for a few hours. I have honestly no idea what you were even trying to say. You can't verify the design, but that's not a problem because you can't verify other designs either? Maybe?
Slashdot Mirror
There's usually at least two reasons to get into Earth orbit first:
- maintaining an abort window, having some time to verify everything is as it's supposed to be.
- because it doesn't matter much, delta-v vise. The energy it takes to reach the moon is pretty much the same, regardless of whether you directly go for earth escape velocity, or suspend your acceleration for a while at orbital velocity. The image in your link that says "falling to the moon" I find misleading, because while in orbit, you're exactly still falling to the earth (keeping to miss because your horizontal velocity is big enough). The amount of energy to invest to go from falling around earth to traveling to the moon is not insignificant, and at this distance the moon doesn't noticably "pull" either, so it's anything but "falling". It's "burning another stage of your rocket" and called the trans-lunar injection.
Anyway, the comparison between going to the moon and going to the sun is pretty flawed. What you might be forgetting is that the whole system, Earth, Moon, you, me, and your superheavy (or supermany, again it doesn't really matter, energy-wise) uranium-laden rockets, are orbiting *sun*. We *are* already falling "towards" it (again we're just fast enough to be continuously missing it). If your rockets are to fall "into" the sun, then they need to shed their velocity that keeps them orbiting sun -- and that's a healthy 30 km/sec. I don't know how much fuel it takes for a delta-v of 30 km/sec, but it's probably a lot. So it requires even more fuel to lift that fuel into earth orbit in the first place, and then some more for that, and so on (the usual rocket equation).
tl;dr: it sucks...
Thanks for that link, Einstein. I traveled back in time and included it in my own post.
And in no way do they *need* all that. They *want* it to offer fancy functionality which is the *last* thing I want in an allegedly highly secure system. Just think of all the code that is required for those fancy features, and when it does get compromised, the attacker can pretty much do anything they want because they have all the permissions. Fuck that. They've lost their credibility to me by pulling off that incredibly stupid mode.
Cron, is that you?
(should've uniq(1)ed the list first, there are four dupes. So the real list is "only" 45 items long as opposed to the 49 I quoted.)
When I was going to install signal because of all the good things I heard about it, my phone presented me with a *massive* list of permissions the Signal app wants:
- read sensitive log data
- find accounts on the device
- read your own contact card
- modify your own contact card
- read calendar events plus confidential information
- add or modify calendar events and send email to guests without owners' knowledge
- find accounts on the device
- read your contacts
- modify your contacts
- approximate location (network-based)
- precise location (GPS and network-based)
- read your text messages (SMS or MMS)
- receive text messages (MMS)
- receive text messages (SMS)
- send SMS messages
- edit your text messages (SMS or MMS)
- directly call phone numbers
- directly call any phone numbers
- modify phone state
- reroute outgoing calls
- read call log
- read phone status and identity
- write call log
- read the contents of your USB storage
- modify or delete the contents of your USB storage
- read the contents of your USB storage
- modify or delete the contents of your USB storage
- take pictures and videos
- record audio
- view Wi-Fi connections
- read phone status and identity
- send WAP-PUSH-received broadcast
- receive data from internet
- view network connections
- create accounts and set passwords
- pair with Bluetooth devices
- send sticky broadcast
- change network connectivity
- connect and disconnect from Wi-Fi
- disable your screen lock
- full network access
- change your audio settings
- read sync settings
- run at startup
- set wallpaper
- use accounts on the device
- control vibration
- prevent device from sleeping
- toggle sync on and off
Needless to say, I backed out.
I'm still not sure you understand your own proposal.
Assuming you get the stuff into orbit, how do you get it from there to the sun?
At least computers are predictable. [...] At least with computers, you can fix the bugs when you find them.
That holds true for classical software, but not for things like neural nets, or anything approaching A.I.
That is less of a problem with safety but with energy expense. It's hard enough to get the super-heavy super-dense spent fuel into orbit, but even then what? You cut the invisible leash attached to it so it falls right into the sun? If you think it works like that, I happento own a nice bridge you might want to consider purchasing.
Obviously he's a pirate.
More like throwing away less than a penny to donate a tiny fraction of a penny... How long would someone be on the pirate bay website, maybe 5 seconds to search for something, download the torrent close the browser and allow the torrent program to do the work.
You forgot the part where the luser closes the TPB browser-tab so the javash^Hcript stops executing. I wonder why....
I don't really see how maxing out your CPU (which in turn generates heat and as a consequence, noise, as well as raising your electricity bill) beats crappy ads and pop-ups...
Most people i know who just want free stuff use some sort of pirate streaming website instead of downloading torrents
Okay, I see it now. It was just phrased the other way around.
Actually, most are probably Android. But I don't see your point, what you said isn't analogous to what I said...
Whoever is "impersonating" you seems to be doing a decent job as their incoherent retarded gibberish is indistinguishable from your incoherent retarded gibberish.
The feature size size today is in the lower range of the visible wave length spectrum
According to wikipedia, the visible spectrum ends at around 390nm.
Intel is currently doing 10nm and planning to go down to 7nm next year.
Here's an example of what can be done: https://www.bunniestudios.com/...
Now that's pretty impressive. However, it says the best possible current resolution is 14.6nm, so it can't currently resolve state of the art dies.
Also those pretty pictures? Their scale is in micrometers, as shown on them.
Hit "enter" a few times
Yes, if you hit enter at the part where it says "Enter passphrase (empty for no passphrase)", you'll get no passphrase. News at 11. Now since this behavior is consistent across all systems that have ssh-keygen, including linux, why are you using this to discredit OpenBSD? And it may have not occured to you, but there are legitimate use cases for unencrypted keys.
*Look, ma!!!* Home directories with .ssh/id_rsa, .ssh/id_dsa
Look ma, even if you're too lazy to enter a passphrase, they're still not world readable. This is, btw, layered security, the very thing you're trying to talk away.
Stop spreading nonsense in order to appear to have a point.
DesktopBSD, m0n0wall, pfSense, GhostBSD, and TrueOS
As far as I know (admittedly I'm more of a NetBSD person), those are all FreeBSD.
I wouldn't be surprised if the /. owners/editors think OpenBSD is yet another linux distro.
And no, I'm not joking. This is a mainstream news site for joe sixpack, operated by nontechs who want money.
So there's that.
Just for the record, this AC is full of shit.
ssh-keygen doesn't generate unencrypted ssh keys by default, that only happens when you skip entering a passphrase (same behavior as ssh-keygen on literally any other platform, because - who knew - it actually originates from OpenBSD). If you do enter a passphrase, it will even refuse to generate a key if the passphrase is too short.
As for layered security, there's plenty of that in OpenBSD, a good deal of which other OSs do not have. Most recent example would be the "pledge" system call (formerly known as "tame").
I particularly enjoy stealing them from CIFS and NFS shares and backups, because even if the OpenBSD box is "secure", people inevitably leave those convenient passphrase keys lying around.
Aha, the "passphrase keys". For the record, as anything else, the private key is created chmod 600. You're not "stealing" shit, you're making things up.
QuickTime
far from impossible
Are you sure about that? I agree that it is theoretically possible, but in practical terms, I believe it is.
People have done it for older chips
Yep, and older chips in comparison are huge and have something like 2-3 interconnect layers. Modern chips have a tiny feature size, and on top of the silicon, a stack of >10 interconnect layers, your microscope will have a hard time looking through those (that is, provided these things could be optically inspected in the first place -- the wavelength of light currently is two orders of magnitude bigger than the feature size).
I for one are not aware of a process that can remove exactly a nm-thick layer of interconnects (in order to expose the next one in the stack) without damaging that next layer. If you are, please enlighten me.
8k is supposed to be the ultimate, the final form of 2D television.
Son, who are you kidding?
Joe Sixpack knows it, marketing knows it: higher is better
I predict 16k devices in 3...2...1...
Way back in the mists of time
I guess that's the thing.
AFAIK these days dies have too small of a feature size for meaningful optical inspection (feature size way smaller than the wavelength of light), and dozens of layers from which, even if you could, you'd only see the topmost one, and simply way too many features to begin with.
Could you rephrase that in a way that doesn't suggest you just had an OCD attack? Preferrably not before cooling down for a few hours. I have honestly no idea what you were even trying to say. You can't verify the design, but that's not a problem because you can't verify other designs either? Maybe?