Skip to main content

Windows 8 for tables and viruses

Ieri seara am participant la un eveniment unde s-a prezentat si Windows 8. De data asta eram pe partea cealalta a baricadei (ca si participant), dar am vazut ca lumea spune destul de des:
Abia astept sa apara virusi pentru Windows 8.
Din acest punct de vedere, pentru versiunea normala de Windows 8 mai mult ca sigur o sa existe (din pacate), nu avem ce face. Dar pentru Windows 8 RT, versiunea care este destinata tabletelor, s-ar putea sa nu avem surprize nefericite.
In primul rand fiecare aplicatie ruleaza intr-un sandbox si nu poate sa faca foarte multe schimbari. Fiecare aplicatie inainte sa ajunga in store este supusa la niste teste, unde se testeaza cat de sigura este pentru utilizator.
Daca aceste verificari o sa se faca cum trebuie s-ar putea sa nu avem probleme cu aplicatiile. De exemplu pentru Windows Phone 7 nu am auzit de nici o problema de acest gen.
Deja, foarte multe compani care creaza antivirusi pentru Windows, isi pregatesc si ultimele versiuni de soft pentru Windows 8, iar pentru Windows 8 RT sper sa nu avem probleme sau cel putin asa ma astept eu.

Comments

  1. Unde ai fost? Pregatesc un blogpost ...

    ReplyDelete
    Replies
    1. La o prezentare tinuta de una dim companiile IT din Cluj-Napoca

      Delete
  2. Nu mi-as face mari sperante - cum din cate stiu pe versiunea de Win8 pentru tablets non-ARM se vor putea rula aplicatii normale, non-"metro", malwares vor aparea.
    La fel si pe ARM - daca va exista o posibilitate de side-loading (chiar daca teoretic doar pentru enterprise-stuff), va exista in timp si malware.

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see