About tech stocks...

Matt Dillon said:
If they never had a backup of the hard drives it could. I could stop ransomware from starting at boot if I had time to search for it. It uses Windows boot, not BIOS boot.

Yes, I did know about Sub7...in fact mobman gave me it 4 days before general release and I mm'd it to 4400 AOL staff members I had collected from hacking an internal.

I had mm'd it 2 days before general release. My icq was one steady ring to where I couldn't possibly check them all for 2 weeks.

The way I got rid of the present-day ransomware was nuking the drive and copying a functional Windows image.

It was faster than spending 1-2 hrs hunting down how the thing (No it's not "The Thing") starts and stopping it from starting and deleting the files.

I say it was all a cover story, because it's weak AF.

I say Biden shutting off drilling caused a fuel crisis, and they ran cover with that weak-ass story.

More to come..believe that. They won't be able to hide it next time.

Any geek worth his salt can stop ransomware from starting with Windows.

There's only so many places to put the startup .inis and files.
Click to expand...
That's all well and good until you consider that you may have 1,000 windows computers connected to your network that all have access to the network. That means you have to take every one of those 1,000 computers off line and reload the last image that may or may not be corrupted because you would need to know when the system was attacked. The virus may have been dormant for 6 months. You have to know that before you reinstall any image or you are simply pissing in the wind. That means you can't get the entire system up in a couple of hours. You would need 100 geeks each getting 10 computers back up to be lucky to get everyone back up in a day. Each of those installs would require a complete scan to confirm you didn't simply reload the virus. And then you would have to test and make sure everything is working because software and files would likely be missing from the image you restored.

Startup and ini files can reference files anywhere. It is highly likely that the network contains computers upgraded from or even still running XP which means you can't rely on Windows10 security features.

But you still haven't got any of your servers up and running yet. That would be the backbone of the network and you have to make sure there are no infections. Then you likely need to replace every password because you have to assume they are all compromised. That means that everyone that needs to log in to the servers needs new passwords or access keys. Every single person will not be able to log in through your domain server until you get them new passwords. Any remote maintenance access to the servers such as RDP or SSH or RSAT has to be reconfigured. But then you also don't know if the intrusion allowed someone to access routers and change the settings there. So all the routers should be wiped and reset. It's starting to be a little more than just putting an image on a single computer if you really want to do this correctly and be safe.

This is about 1/3 of the things you can do:

https://blog.emsisoft.com/en/31002/basics-manual-malware-identification-removal/

I'm a lil more advanced..take regular backups of your stuff.

If a fuel company that supplies the eastern seaboard doesn't take weekly backups of their software to do so, and leaves themselves open to cyber attacks...:dunno:

That's folly.

There's a lot of businesses and infrastructure like that in America. China hacked Miami traffic grid before.

They need to get more secure and take more backups.

The best Chinese hackers couldn't get around a dedicated old-ass linux hardware firewall. Nope.
Click to expand...
A backup does you no good if your backup includes the virus. Restoring the virus to the network would kind of defeat the purpose, don't you think? If you have 1,000 backups for each week, how do you determine which backup is safe to restore and which one would simply restore the virus to your network? How quickly can you do a scan of the backup of a 1G drive? Then your backups have to be ones where they were actually physically removed from the network or the backups may have been encrypted as well.

The majority of viruses don't need to get around a firewall. They only need to have one person out of 900 on your network mistakenly run a program. It's probably attached to an email that one of the 900 employees received and you just loaded all their old emails back on their computer. I hope they don't open it again. ;) Then you have to remind your employees that they can't reuse an old login password when they reset their passwords.
 
Poor Richard Saunders said:
That's all well and good until you consider that you may have 1,000 windows computers connected to your network that all have access to the network. That means you have to take every one of those 1,000 computers off line and reload the last image that may or may not be corrupted because you would need to know when the system was attacked. The virus may have been dormant for 6 months. You have to know that before you reinstall any image or you are simply pissing in the wind. That means you can't get the entire system up in a couple of hours. You would need 100 geeks each getting 10 computers back up to be lucky to get everyone back up in a day. Each of those installs would require a complete scan to confirm you didn't simply reload the virus. And then you would have to test and make sure everything is working because software and files would likely be missing from the image you restored.

Startup and ini files can reference files anywhere. It is highly likely that the network contains computers upgraded from or even still running XP which means you can't rely on Windows10 security features.

But you still haven't got any of your servers up and running yet. That would be the backbone of the network and you have to make sure there are no infections. Then you likely need to replace every password because you have to assume they are all compromised. That means that everyone that needs to log in to the servers needs new passwords or access keys. Every single person will not be able to log in through your domain server until you get them new passwords. Any remote maintenance access to the servers such as RDP or SSH or RSAT has to be reconfigured. But then you also don't know if the intrusion allowed someone to access routers and change the settings there. So all the routers should be wiped and reset. It's starting to be a little more than just putting an image on a single computer if you really want to do this correctly and be safe.


A backup does you no good if your backup includes the virus. Restoring the virus to the network would kind of defeat the purpose, don't you think? If you have 1,000 backups for each week, how do you determine which backup is safe to restore and which one would simply restore the virus to your network? How quickly can you do a scan of the backup of a 1G drive? Then your backups have to be ones where they were actually physically removed from the network or the backups may have been encrypted as well.

The majority of viruses don't need to get around a firewall. They only need to have one person out of 900 on your network mistakenly run a program. It's probably attached to an email that one of the 900 employees received and you just loaded all their old emails back on their computer. I hope they don't open it again. ;) Then you have to remind your employees that they can't reuse an old login password when they reset their passwords.
Click to expand...

You're making it out to be infinitely more complicated than it is.

If there's 1k computers, they probably are running the exact same thing anyway and can be mass done in the same manner they 1st were programmed.

A) You make sure the master backup has no problems and is ready to go for your applications.

It can all be done via an ethernet hub. Really.

I seriously doubt there's that many connected in this instance. Probably 1-2 that manage the system. If it even really happened.

Just because 1 employee opens an email with ransomware, doesn't mean everything on the network is going to be infected.

You are messing with the wrong cracker about things like that. I've been trying to tell you.

You won't learn. It's ok. :)
 
Last edited:
Poor Richard Saunders said:
That's all well and good until you consider that you may have 1,000 windows computers connected to your network that all have access to the network. That means you have to take every one of those 1,000 computers off line and reload the last image that may or may not be corrupted because you would need to know when the system was attacked. The virus may have been dormant for 6 months. You have to know that before you reinstall any image or you are simply pissing in the wind. That means you can't get the entire system up in a couple of hours. You would need 100 geeks each getting 10 computers back up to be lucky to get everyone back up in a day. Each of those installs would require a complete scan to confirm you didn't simply reload the virus. And then you would have to test and make sure everything is working because software and files would likely be missing from the image you restored.

Startup and ini files can reference files anywhere. It is highly likely that the network contains computers upgraded from or even still running XP which means you can't rely on Windows10 security features.

But you still haven't got any of your servers up and running yet. That would be the backbone of the network and you have to make sure there are no infections. Then you likely need to replace every password because you have to assume they are all compromised. That means that everyone that needs to log in to the servers needs new passwords or access keys. Every single person will not be able to log in through your domain server until you get them new passwords. Any remote maintenance access to the servers such as RDP or SSH or RSAT has to be reconfigured. But then you also don't know if the intrusion allowed someone to access routers and change the settings there. So all the routers should be wiped and reset. It's starting to be a little more than just putting an image on a single computer if you really want to do this correctly and be safe.


A backup does you no good if your backup includes the virus. Restoring the virus to the network would kind of defeat the purpose, don't you think? If you have 1,000 backups for each week, how do you determine which backup is safe to restore and which one would simply restore the virus to your network? How quickly can you do a scan of the backup of a 1G drive? Then your backups have to be ones where they were actually physically removed from the network or the backups may have been encrypted as well.

The majority of viruses don't need to get around a firewall. They only need to have one person out of 900 on your network mistakenly run a program. It's probably attached to an email that one of the 900 employees received and you just loaded all their old emails back on their computer. I hope they don't open it again. ;) Then you have to remind your employees that they can't reuse an old login password when they reset their passwords.
Click to expand...

TL: DR That's why your backup doesn't include the virus. Natch!

I bet you can't restore, or image hard drives, or anything, and here you are talking all that shit with your poopy lips.
 
Walt said:
Ethernet is not used as much as wifi these days. Ethernet only provides a network connection, not a backup.
Click to expand...

STFU, I'm talking about ethernet/network installing Windows (or a backup OS) to hundreds of hard drives simultaneously.

Yes, it is done, boy. You are not on my level.

I have yet to see an OS install over WiFi, although it probably can be done. :dunno:
 
Matt Dillon said:
You're making it out to be infinitely more complicated than it is.
Click to expand...
You are making it out to be simpler than it is. Restoring a computer to it's original programming means you haven't restored any changes the user has made over time. All the add-ons, all the keyboard shortcuts created, all the scripts written to automate work are gone. Restoring an disk image may be great for the receptionist that answers the phone and does basic word processing but anyone that uses a computer for other work won't be completely back if you simply reload an original image.

If there's 1k computers, they probably are running the exact same thing anyway and can be mass done in the same manner they 1st were programmed.
Click to expand...
One small problem. We are talking about an energy company that probably has multiple locations and has grown over time. I doubt they put all their computers in service at the same time and I also doubt they are being serviced by a single IT department that was diligent about standardizing everything. It's easy to say, this is what you need to do. To have it happen in practice is something else entirely because IT security isn't that important when you have a business to run and you need something now as opposed to next week when IT can get to it.
A) You make sure the master backup has no problems and is ready to go for your applications.
Click to expand...
That gets all the computers up and running again. Now you just have the daily 3 months of calls from users asking "why does this not work like it used to?"

It can all be done via an ethernet hub. Really.
Click to expand...
Sure. As long as the computer is turned on, running on an OS, and connected to the network. Do you think it is wise to connect a possibly infected computer to your network while you remotely manage it? Of course they could have all your computers set to boot PXE but how likely is that? Even if that is the case, you still need someone to first connect and then turn on the computers. Otherwise they could be simply attaching an infected computer to the network. Another problem is any laptop that isn't hardwired to the network will probably have a hard time doing PXE over wifi.

I seriously doubt there's that many connected in this instance. Probably 1-2 that manage the system. If it even really happened.
Click to expand...
So either you are simply losing all the files on the individual computers because they are not backed up and you are not restoring them or they are connected with some form of read/write privileges because their system backs up and files are stored on a server.
Just because 1 employee opens an email with ransomware, doesn't mean everything on the network is going to be infected.
Click to expand...
Of course it doesn't. But it does put the network at risk because it allows attacks from within the network. Either through probing the network for weakness or allowing for phishing emails that come from accounts within the company. "Hey Joe, can you open this file on the server and tell me what you think? Frank"

You are messing with the wrong cracker about things like that. I've been trying to tell you.

You won't learn. It's ok. :)
Click to expand...
Good for you but you haven't thought through your security plan.
 
Matt Dillon said:
TL: DR That's why your backup doesn't include the virus. Natch!

I bet you can't restore, or image hard drives, or anything, and here you are talking all that shit with your poopy lips.
Click to expand...

Oh. You must be so smart being able to image a hard drive with software someone gave you. I was "dd"ing drives while you were still a script kiddie.
 
Matt Dillon said:
Sure ya were, cupcake.

What size drives are you talking about? :awesome:
Click to expand...

Back then it was probably a 10gb drive.

Before Linux came along, Norton utilities included a handy little hex editor that allowed for read/write direct to disk. It came in handy more than once to get info from a dying disk. Those were disks that were probably smaller than 1gb. A hard drive that can hold the data of over 300 floppy drives seems plenty big.
 
Poor Richard Saunders said:
Back then it was probably a 10gb drive.

Before Linux came along, Norton utilities included a handy little hex editor that allowed for read/write direct to disk. It came in handy more than once to get info from a dying disk. Those were disks that were probably smaller than 1gb. A hard drive that can hold the data of over 300 floppy drives seems plenty big.
Click to expand...

Ah! Busted in a lie, bitch! There were no 10GB drives in those days. :tongout:

1.44 X 300 = How many Mb?

432 Mb.
 
Poor Richard Saunders said:
Back then it was probably a 10gb drive.

Before Linux came along, Norton utilities included a handy little hex editor that allowed for read/write direct to disk. It came in handy more than once to get info from a dying disk. Those were disks that were probably smaller than 1gb. A hard drive that can hold the data of over 300 floppy drives seems plenty big.
Click to expand...

Linux was around since about 1997.
 
Matt Dillon said:
Ah! Busted in a lie, bitch! There were no 10GB drives in those days. :tongout:

1.44 X 300 = How many Mb?

432 Mb.
Click to expand...

You might want to learn how paragraphs work. There were 2 time periods I was referencing.


No 10gb drives in 1999? Are you sure? You might want to rethink that. 1999 is about the time when you were a script kiddie. Linux was also very available at that time.

About 1995 is when I used Norton Utilities hex editor. There were no affordable 10gb drives in 1995. In 1995 ATA drives would have been about 500mb. I think you already did the math. :)
 
Poor Richard Saunders said:
You might want to learn how paragraphs work. There were 2 time periods I was referencing.


No 10gb drives in 1999? Are you sure? You might want to rethink that. 1999 is about the time when you were a script kiddie. Linux was also very available at that time.

About 1995 is when I used Norton Utilities hex editor. There were no affordable 10gb drives in 1995. In 1995 ATA drives would have been about 500mb. I think you already did the math. :)
Click to expand...

Back then a 10GB drive would have been several if not over 10 thousand dollars.

You said "back then", guy. :rolleyes:

A typical hard drive back then was 250MB or less.

I used all kinds of hex editors, what's your point? I learned VB 3-6.

I know old computer languages, and stuff was getting new real fast then. C+ was coming.

I learned HTML, some javascript.

What brand was this alleged 1999 10GB hard drive? :laugh:

Was it SATA?
 
Last edited:
Sailor said:
Dick cannot google that quickly......
Click to expand...

I had a bigger drive than most, and it was less than 1GB.

128-256k RAM was the max.

People were stepping up from 28K modems to 56K ones..or even dual 56K ones, if fancy.

I had neither. :rolleyes: But I did have a modem.
 
You must log in or register to reply here.
Back
Top