security

Setting jsessonid cookie to SameSite=Strict attribute in spring boot?

你说的曾经没有我的故事 提交于 2021-02-16 19:45:16
问题 What is the spring-boot configuration to set jsessionId cookie as SameSite=Strict. JsessionId need to add SameSite=Strict or existing cookie not new cookie generation.Is it support? 回答1: I used Rfc6265CookieProcessor to configure SameSite flag in the spring boot application as a workaround. build.gradle : dependencies { implementation 'org.springframework.boot:spring-boot-starter-tomcat' ... } Config in the main class: @Bean public ServletWebServerFactory servletContainer() { return new

CertPathBuilderException: unable to find valid certification path was 8.5 network deployment

允我心安 提交于 2021-02-16 13:57:52
问题 I have a webservice client in a web application(java) deployed on Websphere 8.5 After I changed the protocol from http to https in the call of the webservice(deployed on was with selfsigned certificate) I have following error: ... javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.j: PKIX path building failed: java.security.cert.CertPathBuilderException: unable to find valid certification path to requested target at it.xxx.LoginManagerClient.LoginManagerClient._autenticate

Any way to guarantee that a git user doesn't use fake account info when commiting and pushing?

假如想象 提交于 2021-02-16 05:17:00
问题 Since git users can config their user.name and user.email freely and do commits, it's possible for John to fake a commit with Bob's name and email, which is not what we want. Is there any way to prevent this? I know in svn we need username and password to commit; is there any equivalent mechanism in Git? 回答1: Some convoluted solutions are possible, I guess: Require an SSH account to access a repository; create one repository per authorized user. Create hooks in every repository that rewrite

Any way to guarantee that a git user doesn't use fake account info when commiting and pushing?

安稳与你 提交于 2021-02-16 05:15:07
问题 Since git users can config their user.name and user.email freely and do commits, it's possible for John to fake a commit with Bob's name and email, which is not what we want. Is there any way to prevent this? I know in svn we need username and password to commit; is there any equivalent mechanism in Git? 回答1: Some convoluted solutions are possible, I guess: Require an SSH account to access a repository; create one repository per authorized user. Create hooks in every repository that rewrite

Does the Android Keystore make use of the Trusted Execution Environment (TEE) and Secure Element (SE) automatically if it is available?

依然范特西╮ 提交于 2021-02-16 03:08:01
问题 Does the Android Keystore make use of the Trusted Execution Environment (TEE) and Secure Element (SE) automatically if it is available? Or are any further steps required? 回答1: Generally yes. There is no requirement for the Keystore to be hardware backed on all device, but if it is hardware backed and if that is by a TEE (the common case) then it will be used whenever Keystore backed keys are used. See the current CDD document for requirements around this. Section 9.11. Keys and Credentials

Apply spring security only to one page

寵の児 提交于 2021-02-11 15:37:29
问题 I have a typical security configuration: @Override protected void configure(HttpSecurity http) throws Exception { http .authorizeRequests() .antMatchers("/", "/index").permitAll() .anyRequest().authenticated() .and() .formLogin() .loginPage("/login") .permitAll() .and() .logout() .permitAll(); //http.authorizeRequests().antMatchers("/resources/**").permitAll().anyRequest().permitAll(); } Now spring is asking for a login for everything except of the login page... But how could I make it the

Using Firebase Auth Custom Claims for custom permissions

早过忘川 提交于 2021-02-11 15:21:56
问题 Initial situation: I am developing an app (iOS, Android, Web App) that primarily uses Firebase Auth Email & Password to authorize my users and manage permissions . There are complex configuration options for the security and access settings that can be individually set for each user . There are also premade roles (e.g. admin, manager, etc.) . However, these are only templates and don't need to be used by the person who manages the user accounts. The permissions can be customized for each user

git: Setting anyone's email address in .gitconfig

一曲冷凌霜 提交于 2021-02-11 15:19:52
问题 I was playing around with git when I realized that it's possible for me to commit something to a repository as another user (explained a scenario below for better understanding) and it is not considered a security vulnerability, understandably so (see this). For example, let's assume I have push access to some repository called AAA, and my email address is abc@xyz.com . I can simply edit ~/.gitconfig on my system and set the email address as some other person's email address: def@pqr.com .

add security headers in NGINX while using fastcgi caching

纵然是瞬间 提交于 2021-02-11 14:11:04
问题 I am using nginx with fastcgi cache. I want to use security headers on my site. I have already added add header field in my virtual host configurations but I can not get any headers unless I disable add_header X-fastcgi cache $upstream cache status in my fastcgi_main.conf file. virualhost file : } include /etc/nginx/bots.d/blockbots.conf; include /etc/nginx/bots.d/ddos.conf; include /etc/nginx/skip_cache.conf ; include /etc/nginx/purge_location.conf ; include /etc/nginx/gzip_location.conf ;

Is there a way in Azure DevOps settings to create a Personal Access Tokens (PAT) equivalent that is not associated with a single user?

别来无恙 提交于 2021-02-11 13:58:16
问题 If I understand correctly, Personal Access Tokens (PAT) are associated with the user identity logged in (they are within User Settings afterall). Question : For functional responsibilities that should not be associated with and reliant upon one individual team member's account (ex. automated systems deployments), is there a way to generate non-user contextual PATs? 回答1: There is no way to create non-user contextual personal access tokens. Personal access tokens are alternate passwords that