Nytro

[h=2]Free Web Vulnerability Scanner[/h]Netsparker Community Edition is a SQL Injection Scanner. It's a free edition of our web vulnerability scanner for the community so you can start securing your website now. It's user friendly, fast, smart and as always False-Positive-Free. It shares many features with professional edition. It can detect SQL Injection vulnerabilities better than many other scanners (if not all), and it's completely FREE. Download: https://www.netsparker.com/communityedition/

Nu ca "se merita", e obligatoriu.

Salut, Invata si foloseste select + FD_CLR, FD_ISSET, FD_SET, FD_ZERO. Ce face: iti permite sa verifici daca pe unul sau mai multi socketi ai date de intrare, date de iesire sau erori. Adica daca ai primit date (in cozile din kernel) pe acel socket, daca urmeaza sa fie trimise date pe acel socket sau daca a intervenit o eroare pe acel socket, de exemplu inchiderea conexiunii. Ce e important la acest "select" e ca poti "astepta" pe un socket un anumit interval (sau poti sa nu astepti) sa se intample un astfel de eveniment (primire date de exemplu). Adica poti verifica daca pe socket ai date de intrare. Daca ai, le procesezi, daca nu ai, treci mai departe. Sau poti astepta 3000 ms sa primesti date. Dupa 3000 ms, daca ai primit date, le procesezi, daca nu, faci altceva. Nu e foarte complicat si sunt tutoriale care explica in detaliu acest syscall. PS: Daca vrei Windows, pe langa select, ai o serie completa de functii asincrone (cele cu Async) care au ca parametru o functie callback care e apelata exact cand e declansat un eveniment (ca primirea de date).

Cu alte cuvinte, spre binele vostru, evitati site-urile guvernamentale. Sunteti liberi sa spargeti site-uri ale unor alimentare sau brutarii, dar evitati "tinte" care va pot face probleme.

Am fost 3 persoane din staff la conferinta. Plus cativa membri. Deci ii intereseaza pe cei de pe RST. Si e legata de securitate. Si e o stire. Deci poate fi postata aici.

@B7ackAnge7z Am votat, primul. Se poate afla usor (Google) si la ce firma.

Posted from Lynx.

Salut, e mai mult o curiozitate, dar ar fi frumos sa vedem cam ca ce lucreaza lumea pe aici. Eu vreau sa vad cine lucreaza ca Developer/Security si cam care e procentul. Alegeti domeniul in care lucrati si daca vreti dati mai multe informatii, opinii si sugestii, intr-un post.

Super, unde gasim un sample?

New design flaw found in crypto's TLS: Pretend to be a victim online Researchers reveal way to hoodwink encryption protocol – and how to fix it By John Leyden, 5 Mar 2014 Security researchers have developed a new man-in-the-middle attack against the cryptographic protocol TLS – a protocol that is used to encrypt online banking and shopping, and other sensitive connections, to thwart eavesdroppers. The so-called Triple Handshake attack can, in certain conditions, outwit vital checks carried out to verify the identity of a user connecting to a server over a secure connection. In other words, it's possible to for a malicious system to intercept a user's login credential (a client certificate in this case) and masquerade as that victim with any server that also accepts the same credential. The quirky flaw was uncovered by security researchers at the French National Institute for Research in Computer Science and Control (INRIA) and draws from their previous work in the field. The attack also has implications for the security of SSL (Secure Sockets Layer), the still widely used predecessor to TLS (Transport Layer Security), as the researchers explain on their website: We have discovered a new class of attacks against applications that rely on the TLS Internet Standard for securing their communications. Essentially, if a user connects to a malicious website and presents a TLS client certificate, the malicious website can then impersonate the user at any other website that accepts the same TLS client certificate. The attacks work with all TLS and SSL versions, as well as the DTLS variant. As you may have noticed, online websites and similar services typically use usernames and passwords rather than TLS client certificates to log users in. This limits the impact of the attack. In practice the flaw becomes more of a problem when it comes to logging into Wi-Fi access points. "Variants of our attacks apply to specific scenarios of standard authentication protocols that rely on TLS, such as the PEAP Wi?Fi authentication mechanism," the researchers explained, adding that their exploit is similar to a previously uncovered cryptographic flaw – the 2009 Ray and Rex TLS renegotiation attack. The researchers – Karthikeyan Bhargavan, Antoine Delignat-Lavaud, Cédric Fournet, Alfredo Pironti and Pierre-Yves Strub – advocate short?term application-level mitigations as well as long-term changes to the TLS protocol to strengthen the standard and safeguard its users against this latest attack and other assaults along the same lines. "Let me stress that the attacks we found exploit a protocol-level issue, and not specific implementation bugs," Pironti told El Reg. "We also propose short-term application-level mitigation, but we aim at getting the protocol fixed, which would solve the issue at its root." The French team have already notified major vendors of TLS software implementations (at Microsoft, Google and others) as well as the Internet Engineering Task Force (IETF) about their research. The experts publicly disclosed the attack and possible countermeasures at an IETF meeting in London on Tuesday evening. An outline of their research was posted ahead of this meeting on an IETF mailing list on Monday. A draft detailing proposed changes to strengthen the TLS protocol can be found here. 'People shouldn't panic' Infosec professionals and programmers' early reaction to the Triple Handshakes research was cautious. "In short, the TLS handshake hashes in too little information, and always has. Because of that it's possible to synchronise the state of two TLS sessions in a way that breaks assumptions made in the rest of the protocol," senior Google software engineer Adam Langley explained on his personal website. "I'd like to thank the researchers for doing a very good job of disclosing this. [They] even included a draft for fixing the TLS key derivation to include all the needed information to stop this attack. "People shouldn't panic. The impact of this attack is limited to sites that use TLS client-certificate authentication with renegotiation, and protocols that depend on channel binding. The vast majority of users have never used client certificates." Marsh Ray, an authentication expert at Microsoft, noted: "Criticality is difficult to gauge." Chris Eng, another security expert, half joked: "I'm just going to do what I usually do and wait for ?@tqbf? [Thomas H. Ptacek] to tell us if the SSL/TLS vuln(s) matter." Pironti and other researchers at INRIA previously discovered a way to exploit flaws in Google and Microsoft's web email services using a glitch in the TLS technology. ® Sursa: New design flaw found in crypto's TLS: Pretend to be a victim online • The Register

Din partea mea, daca zbori de aici, nu mai dai DDOS, si nu mai vad rspula aici, e ok, sunt de acord sa nu iti fie facute datele publice. Oricum nu e nevoie, totul se gaseste la simple cautari pe Google sau aici pe forum. PS: Nu stiu cine da DDOS site-ului tau, dar asa vezi si tu ca nu e frumos.

Din cate am inteles eu le-a CERUT el 300 de dolari, i-au dat banii, apoi i-a santajat ca daca nu ii dau 3000 de dolari ii fac datele publice. Ce contract bre? Oricum mi se rupe de cazul respectiv. Din partea mea datele trebuiau facute publice pentru ca a dat DDOS, atunci.

In mod normal nu sunt deloc de acord ca unui membru sa i se face datele publice pentru ShowOff, malware (non-banking) etc. dar cum baiatu' este cel care ne dadea DDOS... In plus, daca povestea cu 300 si 3000 de dolari este adevarata... Lipsa de etica. PS: Si-a postat in trecut niste date aici pe forum, public.

Muie, Steaua!

Acum merge. Nu sunt foarte detaliate, dar sunt ok. Materie de facultate, nu poti avea pretentii de la asa ceva. Thanks.

Nu stiu ce s-a intamplat, dar Gecko are dreptate pentru ca e moderator. RST's logic.

Sunteti prea activi aici. Topic inchis.

Cine mai comenteaza de-a-n-pulea are ban.

Va place sa comentati la toate cacaturile...

Sa imi ziceti daca mai patiti asta. Puneti un Wireshark daca se intampla si salvati pcap-ul.

Asa cum au bagat nu stiu cate milioane de euro intr-un portal de cacat, ma astept la asa ceva. Comunistii astia sunt chiar retardati. E spalare de bani, pe fata.

"Valoarea total? a proiectului s-a ridicat la 17.881.980 de lei, dintre care 15.199.683 de lei au fost achita?i din Fondul Social European" Sa-i fut in inima. Sa ii futa cineva, sa le dea deface si sa faca toate datele publice. Sa-si bage programu' prin capu pulii si sa il scoata pe cur. Ce firma a realizat acel program? De catre cine e condusa?

Uber kewl!

Nu va alegeti username-uri drept cuvinte cheie sau nume de functii (@mysql_connect de exemplu)

In sfarsit o informatie utila. Aveti AVG? Aveti Chrome? Toti? De pe Mozilla nu merge?