Vlachs

Daca ai 1k E poti sa investesti in ce ai nevoie incat sa iti indeplinesti partea de offsite care dupa parerea mea reprezinta 65-70% din seo. Ai nevoie de tool-uri, servere,etc, 1000E e suma minima incat sa ai succes.

Ar fi pierdere de timp, zilnic cred ca 50 de romani se apuca de 'SEO', nu vad cu ce esti tu mai diferit de ei. Cand ai sa strangi macar 1k E de investit in viitorul tau ca 'seoist', imi spui si vedem atunci, pana atunci...pa pa si o zi buna.

Inveti SEO prin diferite 'experimente' nu citind, inainte de a face 'seo' trebuie sa ai bani de investit(ca in orice domeniu), ai bani de investit atunci o sa reusesti, nu ai...zici ca faci seo si fraieresti lumea.

Lasa ma advertorialele, asta nu e seo, e frectie la piciorul de lemn.

Se poate 'crackui' foarte usor, reflexil + tjd

Mai iesi din casa. Toti penibilii apeleaza la forum. Daca ai avea peste 16 ani nu ai apela pe un forum pentru o chestie din asta, e doar jenant PS: Mutat la penibile.

Nup, s-ar umple de spam, stiu cateva programe care fac spam excelent pe vblogs.

Nu vad ce lagatura are cu respectul si principiile cuiva, motivele date de tine sunt puerile.

Detalii mai multe despre miniduke(analiza bitdefender): Early Version of MiniDuke Ran on Chinese Time | Bitdefender Labs More On MiniDuke and How to Remove It | Bitdefender Labs Bitdefender antimalware researchers have come across samples of a previously-unrecognized version of the MiniDuke virus which, as it turns out, was active as early as May 2012 – and it wants to know what time it is in China. A new sample of the ~20KB MiniDuke backdoor shows (in its header) a compile time of 21st of May 2012. Previously known variants show a compile time of 20th of February, 2013.The sample was first detected and added to the Bitdefender malware database on 26th of May 2012. In conclusion, the file can be confidently dated to May 2012 or earlier. The 2012 sample uses a different installation mode – it is hosted in an executable file as an embedded .dll. The .dll is packed with the same packer as later variants and the code itself is similar. The .exe file drops the .dll, under the name of tempfile.dat and loads it using rundll32. exe Then the virus adds itself to the registry under the key Software\Microsoft\Windows NT\CurrentVersion\Winlogon, shell entry: Unlike the February 2013 samples, it sets an environment variable which contains the path towards the malware. The path where it is stored is identical to the other variants: C:\Documents and Settings\All Users\ and possibly one of the “Application Data” or “Microsoft” subdirectories (picked at random). The environment variable name can be one of the values : APPINIT, DATA, PATHDATA, PROGRAM, USERINIT, SPEC, LOCALAPP, SYSTEMAPP, SYSTEMPATH, APPFOLDER, SESSION, etc. (as shown below). The .dll copied in the temp path has one of the names: ntuser.dat, registry.dat, index.db, profile.dat, sysdata.dat, config.dat, sysini.dat, bootstat.dat … (see above). By contrast, samples from 2013 concatenate several string chunks, picking from: “base, user, reg, index, profile, system, data, config, init, boot, stat, cache, class, setup, network.. etc” and gets run using a .lnk file added to Startup. A very interesting detail: the virus accessesWhat Time is it in China which returns the current time and date in China! If an Internet connection is not present, the system time is used (connection is retried twice every 10 minutes.Although it requests date and time values for China, the malware seems to use only the date(y/m/d), not the time of day. The time user agent for contacting Google is: “User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0)” while other variants used different user agents. Analysis is ongoing but so far it appears that otherwise this sample behaves the same as later ones. The payload files which are downloaded (.gif) are decrypted and saved under one of the names: “winupdt.exe wcsntfy.exe netmngr.exe dumpreport.exe taskhosts.exe wupdmngr.exe winhlp.exe dllhosts.exe dxdiagupd.exe dialers.exe netschd.exe connwiz.exe certupdt.exe repfault.exe wuapreport.exe lanmgr.exe” and is then run with WinExec() if it is an .exe or loaded using LoadLibrary() if it’s a .dll. Multe de aici nu se leaga, ce e atat de sofisticat? 1.daca il pui sa se incarce cu winlogon pe > xp, nu functioneaza, + ai nevoie de uac pentru current_machine(pe current_user nu merge) 2. la bucata asta urla cam toti antivirusii

Si eu caut, sunt curios ce e atat de avansat la malware-ul asta, singurul care e cu adevarat notabil este exploit-ul.

Salut baieti si fete(putine da bune ). Topicul se spera a fi unu offtopic dar constructiv, dinainte de a vorbi trebuie sa stiti ca oricine posteaza doar un cuvant/poza si nu incearca sa posteze o propozitie cap coada si sa aiba un inteles...primeste ban 3 zile. 1.Ce credeti despre atacurile la adresa romaniei ? 2.Nu vi se pare ciudat ca institutiile romaniei au acces la 'reteaua mare' in loc sa aiba doar pe retea locala cu reguli privind ip-urile la care sa se conecteze ? 3.Nu vi se pare ca SRI-ul incearca sa isi faca o imagine prea buna cu 'comunicatele' astea de presa, apar aproape zilnic comunicate in care SRI-ul drege cate ceva 4.O alta chestie care nu o inteleg, atacurile asupra celorlalte tari au avut un scop(au furat ceva important) dar in cazul romaniei oare ce au vrut sa fure, la noi cercetare nu se face, nu avem area 51, deci ce credeti ca au vrut sa fure?

Bitdefender isi fac reclama cu cacaturile astea de stiri, dar sa va spun ceva, am ales Avira(inca free) in locul bitdefender cu licenta.

Da, calculatoarele din debara cu 10Mbps, hai sa fim seriosi A da si uitam, nu inteleg 'autoritatile se straduiesc sa limiteze pagubele si sa opreasca fluxul de informatii sensibile din serverele guvernamentale catre ceea ce pare a fi un serviciu de spionaj extern', ce e atat de straduit?

Poti sa cumperi o licenta cu 10-15$ de la baietii care au acces msdn si in plus cam toate pc-urile/notebook-urile vin cu o licenta in ziua de azi...deci nu se aplica, daca ai bani de platit internetul atunci ai bani sa iti procuri si o licenta win, nu te pune nimeni sa o iei din shop.

Mie mi se pare stupida chestia asta, nu toate pc-urile ar trebui sa aiba support linux, e vorba de necesitate. Nu cred ca este indicat ca in daily usage sa tii linux, multi spun ca folosesc linux, pentru ce il folositi ma fratilor, doar sa intrati pe forum si sa ziceti ca folositi linux, ce faceti voi pe linux fac si eu pe win si in unele privinte fac mai bine pe windows. Windows-ul a evoluat enorm de mult incat in momentul asta il consider mult superior linuxului, binenteles ma refer si la .net care a avut un aport enorm in dezvoltarea applicatiilor win si in plus, a stimulat foarte multe persoane sa invete c#/vb.net... Pe alta parte nu e ok sa 'dictezi' ce os sa foloseasca cineva dar pun pariu ca schema macos se poate aplica si altor producatori de pc-uri.

Nu toata lumea poate sa faca seo, topic-urile de genu nu isi au rostul, cauta pe cineva priceput si plateste-l si gata.

Eu ti-am spus pretul de "la baieti", nu merita banii, iti faci ceva mult mai bun cu banii aia

Nup, procesorul ala e din a doua generatie si este foarte ieftin, undeva la 200-300 lei si restul componentelor nu justifica pretul.

Si cu asta am ajuns la final! Va meritati soarta daca asteptati o pula divina-n cur. The Secret Bible - The Rivals of Jesus @ vPlay - Login

Ma pis pe dumnezeul tau. Credinta in Dumnezeu e un semn de prostie, intr-o era dominata de stiinta si cunoastere tot mai urmezi "Crede si nu cerceta", o sa muriti in prostie.

My dick its GOD.

Nup, nu am mai scris in vb6 de secole:))

Doar pentru niste chestii fara dependinte, restu tot in .net

A few weeks ago I started a new project called TSMBIOS, this is a library which allows access the SMBIOS using the Object Pascal language (Delphi or Free Pascal). [h=2]What is the SMBIOS?[/h] SMBIOS stands for System Management BIOS , this standard is tightly related and developed by the DMTF (Desktop Management Task Force). The SMBIOS contains a description of the system’s hardware components, the information stored in the SMBIOS typically includes system manufacturer, model name, serial numbers, BIOS version, asset tag, processors, ports, device memory installed and so on. Note : The amount and accuracy of the SMBIOS information depends on the computer manufacturer. [h=2]Which are the advantages of use the SMBIOS?[/h] You can retrieve the information without having to probe for the actual hardware. this is a good point in terms of speed and safeness. The SMBIOS information is very well documented. You can avoid the use of undocumented functions to get hardware info (for example the RAM type and manufacturer). Useful for create a Hardware ID (machine fingerprint). [h=2]How it works?[/h] The BIOS typically populates the SMBIOS structures at system boot time, and is not in control when the OS is running. Therefore, dynamically changing data is rarely represented in SMBIOS tables. The SMBIOS Entry Point is located somewhere between the addresses 0xF0000 and 0xFFFFF, in early Windows systems (Win95, Win98) it was possible access this space address directly, but after with the introduction of the NT Systems and the new security changes the BIOS was accessible through section \Device\PhysicalMemory, but this last method was disabled as well in Windows Server 2003 Service Pack 1, and replaced with 2 new WinApi functions the EnumSystemFirmwareTables and GetSystemFirmwareTable, Additionally the WMI supports reading the entire contents of SMBIOS data i using the MSSMBios_RawSMBiosTables class inside of the root\wmi namespace. Note : you can find more information about the SMBIOS Support in Windows on this link. The TSMBIOS can be compiled using a WinApi mode (uses the GetSystemFirmwareTable function) or using the WMI Mode (uses the MSSMBios_RawSMBiosTables class) If you uses the WinApi Mode you don’t need use COM and the final size of the Application will be smaller, but the WinAPI functions was introduced in Windows Vista and Windows XP x64 (So in Windows Xp x86 will fail). Otherwise using the WMI mode you will need use COM (CoInitialize and CoUninitialize), but also you will get two additional advantages 1) The WMI will work even in Windows Xp x86 systems, 2) You can read then SMBIOS data of local and remote computers. In order to use the TSMBIOS in your application only you must add the uSMBIOS unit to your uses clause, then create a instance for the TSMBios class using the proper constructor [TABLE] [TR] [TD=class: number]1[/TD] [TD=class: content]// Default constructor, used for populate the TSMBIOS class using the current mode selected (WMI or WinApi)[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]2[/TD] [TD=class: content]constructor Create; overload;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]3[/TD] [TD=class: content]// Use this constructor to load the SMBIOS data from a previously saved file.[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]4[/TD] [TD=class: content]constructor Create(const FileName : string); overload;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]5[/TD] [TD=class: content]{$IFDEF USEWMI}[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]6[/TD] [TD=class: content]// Use this constructor to read the SMBIOS from a remote machine.[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]7[/TD] [TD=class: content]constructor Create(const RemoteMachine, UserName, Password : string); overload;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]8[/TD] [TD=class: content]{$ENDIF}[/TD] [/TR] [/TABLE] and finally use the property which expose the SMBIOS info which you need. In this case as is show in the sample code the BatteryInformation property is used to get all the info of the batteries installed on the system. [TABLE] [TR] [TD=class: number]01[/TD] [TD=class: content]{$APPTYPE CONSOLE}[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]02[/TD] [TD=class: content] [/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]03[/TD] [TD=class: content]uses[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]04[/TD] [TD=class: content] Classes,[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]05[/TD] [TD=class: content] SysUtils,[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]06[/TD] [TD=class: content] uSMBIOS in '..\..\Common\uSMBIOS.pas';[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]07[/TD] [TD=class: content] [/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]08[/TD] [TD=class: content]procedure GetBatteryInfo;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]09[/TD] [TD=class: content]Var[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]10[/TD] [TD=class: content] SMBios : TSMBios;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]11[/TD] [TD=class: content] LBatteryInfo : TBatteryInformation;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]12[/TD] [TD=class: content]begin[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]13[/TD] [TD=class: content] SMBios:=TSMBios.Create;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]14[/TD] [TD=class: content] try[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]15[/TD] [TD=class: content] WriteLn('Battery Information');[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]16[/TD] [TD=class: content] WriteLn('-------------------');[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]17[/TD] [TD=class: content] if SMBios.HasBatteryInfo then[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]18[/TD] [TD=class: content] for LBatteryInfo in SMBios.BatteryInformation do[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]19[/TD] [TD=class: content] begin[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]20[/TD] [TD=class: content] WriteLn('Location '+LBatteryInfo.GetLocationStr);[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]21[/TD] [TD=class: content] WriteLn('Manufacturer '+LBatteryInfo.GetManufacturerStr);[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]22[/TD] [TD=class: content] WriteLn('Manufacturer Date '+LBatteryInfo.GetManufacturerDateStr);[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]23[/TD] [TD=class: content] WriteLn('Serial Number '+LBatteryInfo.GetSerialNumberStr);[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]24[/TD] [TD=class: content] WriteLn('Device Name '+LBatteryInfo.GetDeviceNameStr);[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]25[/TD] [TD=class: content] WriteLn('Device Chemistry '+LBatteryInfo.GetDeviceChemistry);[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]26[/TD] [TD=class: content] WriteLn(Format('Design Capacity %d mWatt/hours',[LBatteryInfo.RAWBatteryInfo.DesignCapacity*LBatteryInfo.RAWBatteryInfo.DesignCapacityMultiplier]));[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]27[/TD] [TD=class: content] WriteLn(Format('Design Voltage %d mVolts',[LBatteryInfo.RAWBatteryInfo.DesignVoltage]));[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]28[/TD] [TD=class: content] WriteLn('SBDS Version Number '+LBatteryInfo.GetSBDSVersionNumberStr);[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]29[/TD] [TD=class: content] WriteLn(Format('Maximum Error in Battery Data %d%%',[LBatteryInfo.RAWBatteryInfo.MaximumErrorInBatteryData]));[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]30[/TD] [TD=class: content] WriteLn(Format('SBDS Version Number %.4x',[LBatteryInfo.RAWBatteryInfo.SBDSSerialNumber]));[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]31[/TD] [TD=class: content] WriteLn('SBDS Manufacture Date '+LBatteryInfo.GetSBDSManufactureDateStr);[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]32[/TD] [TD=class: content] WriteLn('SBDS Device Chemistry '+LBatteryInfo.GetSBDSDeviceChemistryStr);[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]33[/TD] [TD=class: content] WriteLn(Format('OEM Specific %.8x',[LBatteryInfo.RAWBatteryInfo.OEM_Specific]));[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]34[/TD] [TD=class: content] WriteLn;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]35[/TD] [TD=class: content] end[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]36[/TD] [TD=class: content] else[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]37[/TD] [TD=class: content] Writeln('No Battery Info was found');[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]38[/TD] [TD=class: content] finally[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]39[/TD] [TD=class: content] SMBios.Free;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]40[/TD] [TD=class: content] end;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]41[/TD] [TD=class: content]end;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]42[/TD] [TD=class: content] [/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]43[/TD] [TD=class: content]begin[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]44[/TD] [TD=class: content] try[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]45[/TD] [TD=class: content] GetBatteryInfo;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]46[/TD] [TD=class: content] except[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]47[/TD] [TD=class: content] on E:Exception do[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]48[/TD] [TD=class: content] Writeln(E.Classname, ':', E.Message);[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]49[/TD] [TD=class: content] end;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]50[/TD] [TD=class: content] Writeln('Press Enter to exit');[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]51[/TD] [TD=class: content] Readln;[/TD] [/TR] [/TABLE] [TABLE] [TR] [TD=class: number]52[/TD] [TD=class: content]end.[/TD] [/TR] [/TABLE] [h=2]TSMBIOS Features[/h] Source Full documented compatible with the help insight feature, available since Delphi 2005. Supports SMBIOS Version from 2.1 to 2.7.1 Supports Delphi 2005, BDS/Turbo 2006 and RAD Studio 2007, 2009, 2010, XE, XE2, XE3. Compatible with FPC 2.6.0 (Windows Only) SMBIOS Data can be obtained using WinApi, WMI or loading a saved SMBIOS dump SMBIOS Data can be saved and load to a file SMBIOS Data can be obtained from remote machines [h=3]SMBIOS Tables supported[/h] BIOS Information (Type 0) System Information (Type 1) Baseboard (or Module) Information (Type 2) System Enclosure or Chassis (Type 3) Processor Information (Type 4) Cache Information (Type 7) Port Connector Information (Type 8) System Slots (Type 9) OEM Strings (Type 11) System Configuration Options (Type 12) BIOS Language Information (Type 13) Physical Memory Array (Type 16) Memory Device (Type 17) Memory Array Mapped Address (Type 19) Memory Device Mapped Address (Type 20) Built-in Pointing Device (Type 21) Portable Battery (Type 22) Voltage Probe (Type 26) Cooling Device (Type 27) Temperature Probe (Type 28) Electrical Current Probe (Type 29) [h=3]The TSMBIOS is a Open Source project is hosted in the code google site.[/h]

The WMI Delphi Code Creator (WDCC), allows you to generate Object Pascal, Oxygene (Delphi Prism), C++ and C# code to access the WMI (Windows Management Instrumentation) classes, events and methods. Also includes a set of tools to explore and Query the content of the WMI. [h=2]Code Generation Features[/h] If you are a Delphi developer go to the Delphi Developers wiki page for an detailed list of features about Delphi and the WDCC If you are a Oxygene/Delphi Prism developer go to the Oxygene Developers wiki page for an detailed list of features about Oxygene and the WDCC If you are a Free Pascal (FPC) developer go to the FPC Developers wiki page for an detailed list of features about Free Pascal (FPC) and the WDCC If you are a C#/.Net developer go to the CSharp Developers wiki page for an detailed list of features about C#/.Net and the WDCC If you are a Borland/Embarcadero C++ developer go to the Borland/Embarcadero C++ Developers wiki page for an detailed list of features about Borland/Embarcadero C++ and the WDCC If you are a Microsoft C++ developer go to the Microsoft C++ Developers wiki page for an detailed list of features about Microsoft C++ and the WDCC [h=2]General Features[/h]WMI Explorer : Allow you to navigate over all the WMI namespaces and classes, and display WMI metadata like MOF, Qualifiers and Properties. WMI Class Tree : shows the hierarchy and dependencies of the WMI classes in a namespace WMI Finder: Display all the WMI classes and properties related to a search term. WMI SQL : Allow you to execute WQL sentences in a local or remote machine, also include a option to auto generate of WQL code WMI Properties Links : Display the location and sources from where each wmi property get the information. Support for Skins Customizable Syntax Highlight Colors [h=2]Download Links[/h] Installer Binaries (Portable edition) Microsoft, Visual Studio, and the Visual Studio logo are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. All Embarcadero brand and product names are trademarks or registered trademarks of Embarcadero Technologies in the United States and other countries. All other marks are the property of their respective owners