|
Once again: How to defence if one has not the knowledge about, and this includes of course how to use it...?
Conceal unfortunately you know from your history 
Bruno
modified 19-Jan-21 21:04pm.
|
|
|
|
|
By your rationale, the police should be trained to catch murderers by murdering. It just happens that the skills needed to get away with murder differ completely from the skills needed to catch murderers.
I agree that coroners must have a knowledge of e.g. the effects of various poisons, but that does not mean that such specialised knowledge should be publically disseminated.
[There was a case in England where an expert on poisons was testifying in court, and started to say that all poisons can be detected, except for... at which point the judge stopped him, saying that airing such knowledge was not in the public interest.]
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Cryptography and Security - OK here - Public domain stuff.
Viruses, Worms, etc. - Not OK here - NSA stuff 
modified 22-Feb-15 10:17am.
|
|
|
|
|
You know, here one point every user about SQL injection  but the reality nobody recognize... *lol* simply stupid...SQL injection that is maybe a Thing which my 10 year old son use.....
Bruno
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Bruno, your use of the term so-called professionals comes across very poorly. Just because they don't agree with you doesn't mean that their opinions are invalid.
The simple reason we close these discussions down is because we don't want to help people write malicious software. Effectively we would be publishing details on how to write malicious software. If you want to find out more details, you can always take one of the numerous courses on the topic. The thing you have to remember is that while you might have reasonable cause to want to read about it, we can't guarantee that anyone reaching it off a search engine will have similar motives. So no. We don't welcome this topic. If you want to find out how well the idea would be received, head on over to StackOverflow and ask the question. Just let us know when you are going to do it so we can bring popcorn.
|
|
|
|
|
Dear Pete O'Hanlon
Thank you for the first constructive answer! Now, I can't agree with your arguments, but I hope that does not affect to proceed the discussion.
I'm still on the Point "the professionals" do not know more than me about this theme and that's why nobody likes to discuss about it.
What is wrong about my thinking "knowing the enemy" is the best way to defense?
Bruno
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Knowing the enemy is fine. Giving them the codes to your house alarm isn't.
|
|
|
|
|
I think the enemies have the code before....
modified 19-Jan-21 21:04pm.
|
|
|
|
|
If you're interested in something that lets you just sit back and listen to, I recommend Steve Gibson's Security Now[^] podcast.
It's not exactly a show that's meant to be accessible for the masses, but at the same time, he won't go so far as to discuss source code. Personally, I find it's an easy-to-digest format to keep up to date with current computer security news.
|
|
|
|
|
Well, you could do a couple of practical things in how you go about doing things on a pc to protect yourself against viruses without knowing how to code it.
1) Don't open any email attachment without absolute certainty about who send the email.
2) Scan the email attachment in any case for viruses... It could be that this person send you a virus without even knowing about it.
3) Don't follow any links via email without knowing who send the email.
4) Use long passwords and keep them in a safe place.
5) Go to safe/recognized websites.
6) Do regular scans with anti-virus software.
7) Keep anti-virus software updated.
8) Monitor your computer's performance, data usage, behaviour and programs running in the background.
9) Search the web and make sure these things running is legit.
10) Change passwords regularly
11) Don't use public pc's to access your internet accounts... These are riddled with viruses.
12) Read articles about security tips on how to prevent yourself from being hacked.
13) If your gut tells you something is fishy, don't do it, or find out more information about it via internet.
14) Pay for the stuff you want... software/games/music/movies... nothing in life is for free... people might make you believe it is but chances are, it comes with a little virus attached. Sure you could download stuff for free off torrent sites but the chance of your pc contracting a virus is good... once again, nothing in life is free. If you download free stuff off torrent sites, be willing to pay for the consequences.
15) Etc.
P.S. If you want to learn how to protect yourself, do not go to hacking websites as this is where you'll get hacked the easiest.
"Program testing can be used to show the presence of bugs, but never to show their absence."
<< please vote!! >>
modified 23-Feb-15 2:32am.
|
|
|
|
|
Born to code...[^]
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Hell yes I'd take the job. I love coding, but I also love having responsibilities and getting paid accordingly 
As a bonus I can make my underlings do whatever I want, ALL SHALL LOVE ME AND DESPAIR!!! MUWHAHAHA!
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
Sander Rossel wrote: As a bonus I can make my underlings do whatever I want
I would like to live the day you discover how that's not! true... 
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
If my underlings were like me I'd be doing stuff for them... 
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
So, after all you not that Lazy<person>?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Not really, actually
I used to be lazy until I started working.
Before that I went to school, which really sucked up all of my energy, creativity, will to learn, lifeforce, everything actually.
It still does that, that's why I hate studying, but I still do it from time to time...
I also really don't like manual labour. Chores, garden, that sort of stuff.
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
Sander Rossel wrote: Chores, garden, that sort of stuff.
I'm with you there: I hate mowing the damn lawn - you end up with a huge pile of cr@p to get rid of, and it just grow back anyway!
But I don't mind manual labour sometimes: fixing motorcycles (even cars sometimes), reupholstering my chair, making a fence. There is a sense of "completion" that you don't get often enough from coding.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Concrete? You can color it too...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I suggested green concrete many years ago.
She did start speaking to me again, after a few weeks... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
So suggest it again! It will not take away the problem of the garden, but at least she will left you alone... 
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
"Speaking" is not the only thing she doesn't do... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: I hate mowing the damn lawn - you end up with a huge pile of cr@p to get rid of
Now that's when I get lazy... Just leave it lying there. It'll be gone in a week
OriginalGriff wrote: fixing motorcycles (even cars sometimes), reupholstering my chair, making a fence
The only thing I complete is chaos. I'm really bad at that sort of stuff... Had to paint a wall. So I sandpapered it (with a name like Sander you'd say no problem!) and it did actually look pretty good. Then I had to clean my whole living room because it was covered in dust. So then I started painting and by the time I was finished I noticed it didn't look as good anymore. So the next week I sandpapered, cleaned and painted again. Didn't look good again, so then I just sandpapered it some more. It looks "okay" now, but screw that $#%@#^$*@) wall. It's only in my kitchen so I'll only have to look at it everytime I'm at home and in the kitchen, which is multiple times a day.
I kind of saw this coming too, so I hired someone to do the rest of the house for me 
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
|
Sander Rossel wrote: Had to paint a wall.
It is much more easier to paint a white wall programmatically - Blank[^]
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
OriginalGriff wrote: I hate mowing the damn lawn - you end up with a huge pile of cr@p to get rid of, and it just grow back anyway!
Just like programming.
|
|
|
|
|
Nope.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
