Search the Community

Asa cum spune si titlul. Caut programator full time cu cunostinte medii spre avansate in limbajele principale de programare: php, mysql, javacript si sa fie capabil sa rezolve si sa invete fiecare obstacol de limbaj nou intalnit. (css, html nici nu se pune problema). Salariu 1000 euro cu posibilitate de crestere + bonusare. Se lucreaza de la sediu, proiectele sunt atractive, iar stresul de la locul de munca 0. Locatie: Bucuresti. Astept PM.

facebook proxy unblock (DVD Strmec) status updates and posts keep you linked to all of your buddies near and far in the same time. It seems everybody is joining Facebook to settle in touch with family and friends.

|=-----------------------------------------------------------------------=| |=--------------------=[ The Fall of Hacker Groups ]=--------------------=| |=-----------------------------------------------------------------------=| |=--------------=[ Strauss <strauss@REMOVEME.phrack.org> ]=--------------=| |=-----------------------------------------------------------------------=| --[ Contents 1 - Introduction 2 - Background 3 - Nowadays 4 - Conclusion 5 - Shouts 6 - Bibliography 7 - Notes --[ 1 - Introduction The earlier, bigger part of hacking history often had congregations as protagonists. From CCC in the early 80s to TESO in the 2000s, through LoD, MoD, cDc, L0pht, and the many other sung and unsung teams of hacker heroes, our culture was created, shaped, and immortalized by their articles, tools, and actions. This article discusses why recently we do not see many hacker groups anymore, and why the ones we do, such as Anonymous and its satellite efforts, do not succeed in having the same cultural impact as their forefathers. --[ 2 - Background Hacking is, in its very essence, an underground movement. Those who take part on it have always been the ones who (ab)used technology in ways beyond the knowledge of the larger userbase. It is tightly linked to intense efforts in unveiling previously unknown information as well as in sharing these discoveries. These premises hold true for as long as we know hackers: since computers had barely no users up until the informatic massification of today. The nature of the hacker interests intrinsically poses difficulties: growing knowledge on anything is hard. It requires heavy research, experimentation, and can turn into an endless journey if objectives are not carefully set. Just like in any field of scientific studies, it calls for a good amount of colaboration, an attitude which, luckily for hackers, was greatly enabled by the advent of computer networks and, most notably, the Internet. Computer networks increasingly made it possible to transmit unlimited and uncensored information across their geographical extent with little effort, with little costs, and in virtually no time. From the communication development standpoint, one would expect that the events that followed the 80s to our days would lead to a geometric progression in the number of hacker communities. In effect, hacking has arguably grown. Hacker communities, definitely not. So what went wrong? --[ 3 - Nowadays We live in days of limited creativity. Moreover, as contraditory as it may seem, it looks particularly rare for creativity to arise from groups or teams. Communities, rather than individuals, should be more intellectually empowered to create, but lately we have been watching the force of the solo, the age of the ego. That, of course, when we do see anything that catches our attention for originality, which is an ever scarcer pleasure. In "Time Wars" [1], Mark Fisher explains that post-fordism has taken us to this catatonic inability to innovate. Our nearly obsessive compulsion for work consumes not only our time, in the literal form of labor hours, but our minds, by distracting us from everything else we could be doing otherwise. These distractions include our unceasing connection to ubiquous media (e.g. the frequent checks for new e-mail, or accesses to social networks on mobile devices) as well as an increased concern with financial stability and provisioning, a concern that grows as welfare is invariably trimmed by both the governments and the private sector. It is important to note that our capitalist worries are more deeply rooted in us than might seem at first, even in the most politically diverse people. Supporting oneself is not easy, it does not come for free. Getting some education, finding a job, staying up-to-date... regardless of what your aspirations are, whatever you feel obliged to do is probably a lot, already. And it likely involves a prevalence of "minding your own business". The unsettlement created in our thoughts affects intellectual solidarity in even more severe ways than it does individual creation. Simply put, if it is already so difficult for one person to focus away from these "distractions" and into inspired productivity, let alone for a group to join in a true collective mind. The ties that bind collective-minded parties together take dedication to build, and our egotistical concerns do not help (see note "A"). Not only is commitment required for the actual work to be accomplished, but also to identify the shared values and goals that enable true human connectivity. Notice this does not concern _collaboration_ as much as it does _collectiveness_. Collaboration typically breaks down the creative process in a way it can be incrementally achieved with very self-sufficient, individualistic contributions. Such is the case in most open-source software projects. Roles are very well segregated so that a minimum of human integration is required, as far as most modern software development processes go, anyway. A true "hive mind" [2] cannot exist without the support from a stronger, more unisonant cognitive bond. Funny enough, the popular variants of LOIC, the DDoS tool used by "Anonymous", contain a "hive mind" feature (i.e. getting a target automatically from a given IRC server and channel and firing your packets against it). You wish it was that easy. The concept of the "conscience collective" was first established by Emile Durkheim who, in his 1893 book "The Division of Labor in Society", expressed 'that the more primitive societies are, the more resemblances (particularly as reflected in primitive religion) there are among the individuals who compose them; inversely, the more civilized a people, the more easily distinguishable its individual members', as put by R. Alun Jones [3]. Well, following (or despite) the prosperous adoption of atheism and agnosticism as professed in the Internet and other popular media, it is understood that religious beliefs are in a low, taking a bit of what socities traditionally saw as a point of unity. In fact, there seems to be an ever growing search for uniqueness in the modern man, especially that from the apparently overpopulated metropolises (see note "B"). In this never-ending crowd of interesting, outstanding personas, we want to shine somehow, to prove ourselves different and original. In the end, it turns into a pointless battle, against God-knows-who, for apparent singularity. Instead of reaching for the fellow man, we want to set ourselves apart, and thus, remarkable. --[ 4 - Conclusion Modern life nearly conspires against the collective. We are tormented by a relentless flow of information as well as the daily worries of an eternally insecure, unwarranted life. Furthermore, we dread the thought of being alike, of sharing multiple views and opinions. As such, we are turning progressively judgemental of who we should be partnering with, on the basis that "they do not understand". In hacking, it yet implicates on the delicate subject of trust, which would require an essay on itself, given the undeniable importance the matter has acquired over the years. If our thoughts on creating hacker groups were to be summarized, this is how they would look: No one ever feels like we do. They are not to be trusted and we do not have the time for them. The only attitude consonant to our search for a comfortable, safe life is to constrain ourselves to our own limitations, ignore the intelligent life out there, and surrender to the mediocracy that our society has condemned our leisure time to. --[ 5 - Shouts My only acknowledgements go to whoever reads this through and puts his/her thoughts to it. I eagerly await for your comments. --[ 6 - Bibliography 1 - "Time Wars", Mark Fisher - (pagina’s niet in het hoofdmenu) | Gonzo (circus) | Muziek.Kunst.Meer. incubate-special-exclusive-essay-time-wars-by-mark-fisher/ 2 - "Collective Consciousness", Wikipedia - Collective consciousness - Wikipedia, the free encyclopedia 3 - Excerpt of "Emile Durkheim: An Introduction to Four Major Works", Robert Alun Jones - The Division of Labor in Society (1893) --[ 7 - Notes A) In respect to social networks, while they are a valid community-building mechanism in nature, selfishness prevails in common usage, by means of the indulgent pleasure that fuels chronic "pluggedness", at times voyeur, at times exhibitionist and needy. It is arguably the case, though, that the globalizing aspect of the Internet has brought the feeling of upsetting commonality to the citizens of even the more unpopulated places. Un articol interesant.

Am dat peste un raspuns destul de elaborat si bine construit / argumentat si m-am gandit sa il shareuiesc pentru ca poate schimba perspectiva multor useri de p-aici. ( asta daca stiu engleza, desigur ) Argh. No. We really need to stop with the current internet-penis-size mentality around algorithm skills. Yes, testing for basic algorithmic knowledge is an excellent interview shit-test to weed out people that have absolutely no business writing code, but other than that has very little to do with the job of being a software developer. You can spend all bloody day churning out bug-free code with perfect linear time complexity at laser-finger speed, but you might still be a totally shitty developer. We are not athletes or musicians that perform on stage - we are engineers. Our job is to build things. More specifically, (1) build the right things, that (2) work as expected, are (3) easily maintainable for a year or two, and (4) built within reasonable time-frames. This is sort of how I spend my time at work: 40% Talking about WHAT to build. Communication about requirements is by far the most complex, important, and time-consuming aspect of software development. This includes negotiating them, measuring success of them, preventing feature creep from entering the backlog, prioritizing work, how to evolve the architecture instead of just welding the feature on top of it, convincing your product owner that you need to deal with technical debt, and another billion things. If you don't get this right, it will fail your project no matter how good you are at the other stuff. 40% Diving through other peoples code. It is absolutely crucial to be able to absorb other peoples code correctly and quickly, so that you'll make changes that fit (1) in the architecture and (2) don't break existing functionality. It's even more important that you are able to GENERATE code that is easy to understand and absorb, or you'll be a sort of "time cancer" for the team that constantly produces more and more code that wastes more and more time for people to read and understand. I don't care if a programmer has 200 in IQ - if she neglects writing unit tests (the best kind of code documentation), he's GOING to be a detriment for the team, not an asset. 15% Hunting down existing bugs and performance bottlenecks. This has very little to do with algorithmic skills, because humans cannot "look" at 500 000 lines of code and see what is wrong. You need the skillset to methodically narrow down your suspects until you've found the offending method, which usually takes a lot of methodical patience. Once you actually find WHERE the bug/bottleneck resides, it's almost always easy to fix and doesn't require algorithmic genius. 4% Writing actual, new functionality. 1% (and I'm being generous here) Thinking about the time complexity of things. In conclusion: When interviewing, by all means, do a little bit of algorithms just to make sure that the candidate can code, but primarily look at if the person has actually gotten shit done, in a team, in the past.

Funding from the Core Infrastructure Initiative has helped the maintainers of OpenSSL, one of the Internet’s most-deployed pieces of open source software, begin to get the crypto implementation on its feet. Despite its ubiquity, OpenSSL has historically been under-funded and under-resourced, though no one outside those close to the project knew how dire the situation was until Heartbleed and other Internet-wide bugs started experts looking closely at the security of open source software. With funding from CII and other corners of the Internet, full time help has been hired to maintain the regular flow of patches and feature upgrades, and since last spring, get the code base ship-shape for a full-fledged security audit. NCC Group Cryptography Services, the security company behind the first phase of the TrueCrypt audit, Monday announced that it, in partnership with the Linux Foundation, will conduct an audit of OpenSSL, looking at key components likely to put installations at risk in the event of a critical vulnerability. “A number of folks who have contributed their free time and professional time, kept OpenSSL growing,” said Tom Ritter, principal security engineer at NCC. “A lot of those contributions were around making OpenSSL more efficient and improving speed—and security improvements. Now, being able to have people work on it fulltime in a maintenance capacity goes long way. Any project that old accumulates technical debt takes that takes time and effort to pay down. Having fulltime focus on bug maintenance is super important.” OpenSSL’s code cleanup paved the way for the audit, Ritter said. Engineers spent significant time re-reading areas of code of most concern—and fixing bugs along the way—in order to make the code more reliable, consistent and secure. Ritter said work on the audit should begin shortly, and the first set of results will be made available mid-Summer after OpenSSL has had time to review the results and patch. Ritter said the audit will be concentrated only in certain critical areas of the OpenSSL codebase, and will not be comprehensive. In scope are the TLS stacks, covering protocol flow, state transitions, and memory management. The BIOS, high-profile crypto algorithms and fuzzing of the ASN.1 and x509 parsers will also happen, Ritter said, adding that input and feedback from the current OpenSSL team also contributed to what ultimately ended up in scope for the audit. “We chose areas around OpenSSL where a flaw here might be of higher severity than other areas,” Ritter said. “The types of things we’ll be looking for are things such as protocol mishandling or state transitions, things like that, even timing attacks in crypto algorithms, or memory corruption that would yield a denial of service condition or remote code execution. Those are the types of bugs looking for. If find one of those, it has the possibility of being fairly critical.” Unlike the TrueCrypt audit where one of the stated goals was to determine whether the popular encryption software had been backdoored, that isn’t necessarily the case with OpenSSL, Ritter said. “You haven’t heard much about [backdoors] in OpenSSL,” Ritter said. “Our real goal is to find any sort of exploitable security concerns. I think that we’re focusing on it from the perspective of a security audit.” Expect Ritter and his team to spend plenty of time in front of large whiteboards for the next few months, tracing out function flows and diagram the code in order to support the manual and automated code review it will take to properly assess OpenSSL. And while the audit may not yield something as dramatic as Heartbleed, you can expect Ritter’s team to be looking in that direction. “Certainly looking at historical bugs in the platform gives us an idea of the types of flaws present still; it will be helpful,” Ritter said. “I’m not going to say we’re doing to go in expecting to find any particular bug in a particular area, but looking at historical bugs does guide us in certain areas as do a lot of the less high-profile bugs. Looking at just about any bug and seeing the underlying causes of it gives us a sense that if something similar is happening elsewhere, there could be a bug there.” Source

There's a story on Hacker News asking what the hell is going on with the Truecrypt audit. I think that's a fair question, since we have been awfully quiet lately. To everyone who donated to the project, first accept my apologies for the slow pace. I want to promise you that we're not spending your money on tropical vacations (as appealing as that would be). In this post I'd like to offer you some news, including an explanation of why this has moved slowly. For those of you who don't know what the Truecrypt audit is: in late 2013 Kenn White, myself, and a group of advisors started a project to undertake a crowdfunded audit of the Truecrypt disk encryption program. To the best of my knowledge, this is the first time anyone's tried this. The motivation for the audit is that lots of people use Truecrypt and depend on it for their security and safety -- yet the authors of the program are anonymous and somewhat mysterious to boot. Being anonymous and mysterious is not a crime, but it still seemed like a nice idea to take a look at their code. We had an amazing response, collecting upwards of $70,000 in donations from a huge and diverse group of donors. We then went ahead and retained iSEC Partners to evaluate the bootloader and other vulnerability-prone areas of Truecrypt. The initial report was published here. That initial effort was Part 1 of a two-part project. The second -- and much more challenging part -- involves a detailed look at the cryptography of Truecrypt, ranging from the symmetric encryption to the random number generator. We had some nice plans for this, and were well on our way to implementing them. (More on those in a second.) Then in late Spring of 2014, something bizarre happened. The Truecrypt developers pulled the plug on the entire product -- in their typical, mysterious way. This threw our plans for a loop. We had been planning a crowdsourced audit to be run by Thomas Ptacek and some others. However in the wake of TC pulling the plug, there were questions. Was this a good use of folks' time and resources? What about applying those resources to the new 'Truecrypt forks' that have sprung up (or are being developed?) There were a few other wrinkles as well, which Thomas talks about here -- although he takes on too much of the blame. It took us a while to recover from this and come up with a plan B that works within our budget and makes sense. We're now implementing this. A few weeks ago we signed a contract with the newly formed NCC Group's Cryptography Services practice (which grew out of iSEC, Matasano and Intrepidus Group). The project will evaluate the original Truecrypt 7.1a which serves as a baseline for the newer forks, and it will begin shortly. However to minimize price -- and make your donations stretch farther -- we allowed the start date to be a bit flexible, which is why we don't have results yet. In our copious spare time we've also been looking manually at some portions of the code, including the Truecrypt RNG and other parts of the cryptographic implementation. This will hopefully complement the NCC/iSEC work and offer a bit more confidence in the implementation. I don't really have much more to say -- except to thank all of the donors for their contributions and their patience. This project has been a bit slower than any of us would like, but results are coming. Personally, my hope is that they'll be completely boring. Sursa: A Few Thoughts on Cryptographic Engineering: Another update on the Truecrypt audit

Product Description TimeBell software of reminders with advanced capabilities, simple and pleasure interfaces and convenient desktop calendar. TimeBell – very easy to use and convenient tool that allows you to create reminders and plan system actions at specific time. There is important event which your would not miss -TimeBell reminds about it. Having created any tasks with the help of TimeBell your can not worry about its performance. Need a reminder? No problem! Set it up easily with TimeBell ! TimeBell – program reminders of events. Is there an important event you don’t want to miss? Use TimeBell to remind you! But TimeBell doesn’t stop there. TimeBell automates reminders and many repetitive computer actions for you. Once created in TimeBell, you will never have to worry about them again! What a time saver, your computer will remember to have that program up and running, even if you can’t be there! TimeBell with its reminders and advanced capabilities, makes it simple! The TimeBell program is easy to understand, even someone new to computers will find it easy to get started. There is even a convenient desktop calendar. New in this version TimeBell: – Function Countdown Timer. At predefined time TimeBell can: – open a reminder window with your text (image can even be added to it) – start up predefined program or open a file – close selected a program – open a predefined website – switch off monitor, shutdown, put it to sleep or put it to standby mode, change PC user. – show window with countdown 1 minute before action with powerPC – change the wallpaper of desktop – send an email using a predefined e-mail address – accompany task by the sound – synchronize time with atomic clock All these tasks can be executed once or periodically (hourly, daily, weekly, monthly, yearly). All tasks can be performed in any combination, together or separately. The number of TimeBell tasks is unlimited. At start up, TimeBell notifies you about any missed tasks. You can view the list of tasks on present day at starting program. If you use multiple computers, you can transfer the data file with all the tasks of TimeBell between them via external storage or through Internet. You can even create TimeBell tasks remotely through Internet. Customized capabilities of TimeBell. – run TimeBell with Windows (is active by default) – minimize TimeBell to system tray on start (is not active by default) – when TimeBell is run, show window with tasks on current day (is not active by default) In order to see tasks in more detail or edit a task, just double-click on the task with left mouse button to display a window with all the details. – speak time every hour (is not active by default) – displaying calendar on the desktop (is not active by default) – automatically download a tasks from website EVVAsoft - Enjoy the life! We will remind you about events. (is active by default). Delete of downloaded tasks from website (is active by default) – windows “stickers” for create your notes – function of the address book – function countdown timer. – check update for new version TimeBell (is active by default). Check updates automatically – when startup TimeBell or manually select in menu “Check for Updates now”. For disable this function please select in menu program “Disable automatically check updates”. – password to protecting access to TimeBell (is not active by default) – countdown 1 minute before action with powerPC (is not active by default) Synchronize time with atomic clock: – automatically synchronize time with atomic clock (is active by default). You can disable this function. – You can select periodically synchronize time with atomic clock: hourly, daily, weekly, monthly (hourly by default) – at start-up TimeBell synchronizes time with atomic clock – you can select SNTP server for synchronize time ( time.windows.com by default) or add your SNTP server Appearance TimeBell is customizable: – skin – color of the fonts The following are displayed in the TimeBell calendar on the desktop : – date and time – a season of year – the year according to oriental calendar – a sign of the zodiac for the current date – indication of the leap year Setting for the calendar on the desktop: – The 24-hours (by default) or the 12- hours AM/PM view by choice – Select the day to start week : Monday (by default) or Sunday – Skins calendar on the desktop – For returning to current date, push button “Today” on calendar – Variable transparency is available on the desktop calendar – Double-click date on desktop calendar to create new task The number of TimeBell tasks is unlimited. At start-up, TimeBell notifies you about any missed tasks. You can view the list of tasks on present day at starting program. If you use multiple computers, you can transfer the data file with all the tasks of TimeBell between them via external storage or through Internet.You can even create TimeBell tasks remotely through Internet. Product Homepage Here -> Download <-Deal Expires in: EXPIRED!

Product Description It is frustrating: Even with the best cameras, one only gets ordinary results. It is obvious: the photos could clearly be better. Dreary colours could be pepped up, image could be sharpened and details could be highlighted. Especially, brightness has to be adjusted, as most of the photos are too dark. You also want to edit scanned photos? Wouldn’t it be great to have a software which deals with picture optimization and repair and which is at the same time easy to handle? Optimize your photos with one single click! Photomizer 2 makes the most out of your photos – with one single mouse click. Thus, you will get perfect results without training period. Even if you want to optimize a large number of photos, this is not a problem due to the batch mode. Thanks to predefined profiles, you will always find the correct settings for your photos. Photos, which otherwise would have landed in Windows recycle bin, can be rescued effortlessly with Photomizer 2. You can optimize your photos with only one mouse click. Thus, fog is automatically removed by the software. Your pictures will appear in a new light, colours will shine again, contrasts will get sharper and more details will be seen. Optimize and repair your photos! With the integrated batch mode, even large numbers of photos can be optimized easily without changing the original. You can choose the amount of the optimization for every photo individually. The preview function allows you to compare the original to the optimized photo at any time. Photomizer 2 even optimizes scans of old dias and paper prints without any problems. It does not matter if a photo is denoised or if there are artefacts or cracks on a photo: The software can fix those bugs automatically. Save time with integrated profiles! Thanks to integrated profiles, you can optimize your photos even faster. Every profile offers various settings, which avoid a tedious and time-consuming training period. The selected profile can be used for a set of images – the so-called batch mode. Thus, you can save a lot of time. The software already contains various profiles, which have been created with the help of experienced photographers. They assist with optimization of digital photos, dias, negatives, web cam pictures, scans and snapshots made with a mobile phone. System requirements Windows XP/Vista/7/8 (32- and 64-Bit) .NET Framework 4.0 (is installed automatically if required) Min. 1 Gigabyte RAM (2 GByte recommended) – the greater the memory capacity, the better! CPU with at least 1 GHz, a fast Dual-Core or even Quad-Core computer recommended Online Internet connection required to activate the software Product Homepage Here -> Download <-Deal Expires in: EXPIRED!

Salut, am 2 functii si vreau sa le fac detour: private void WriteTempRezults(string iD, string test, string points, string time, string memory, string msg) private void InsertListView(string testNumber, string points, string time, string memory, string msg) Problema este ca nu pot sa gasesc adresele la care se afla functiile. Orice indicatie ar bine primita. Aplicatie: Evaluator Virustotal: https://www.virustotal.com/sv/file/8848b.../analysis/

The Social-Engineer Toolkit is an open-source penetration testing framework designed for Social-Engineering. SET has a number of custom attack vectors that allow you to make a believable attack in a fraction of the time. SET is a product of TrustedSec, LLC - An Information Security consulting firm located in Cleveland, Ohio. Download: https://github.com/trustedsec/social-engineer-toolkit